todo, read source.

Waste in Web Development

The TPS identifies seven types of manufacturing waste:

Overproduction
Waiting
Transportation
Extra processes
Overstock
Motion
Defects
In relation to software development, however, it’s clear that not all these types of waste translate. Lean Software Development identifies the following types of waste which translate perfectly between software and web development:

Partially complete work
Extra processes
Extra features
Task switching
Waiting
Motion
Defects
Since some of those are not immediately clear as waste, let’s examine them in more detail…

Accurate enough?

Honestly, even with all of the issues listed above, we've only scratched the surface of accurate emulation. Take the case of DICE, the digital integrated circuit emulator. Here is an emulator that works at the transistor level for absolutely perfect recreation of the very first video games ever created. To run Pong at about 5-10fps, DICE requires a 3GHz processor. Yes, you read that right: no computer processor at this time that can run Pong at the circuit level at full speed. It's not that DICE is a slow program; indeed, it is very well optimized. It's that there is enormous overhead to simulating every last transitor propagation delay.

So as my information-less friend said - Node will scale. But that is, indeed information-less. So can Ruby, Rails, Java, C++, and COBOL - architectures scale - languages and servers don't. Just like most web apps, a Node application will probably be bottle-necked at its database. You can fool yourself that Node itself is "insanely fast" but you'd be fooling yourself (Java/Vert.x vs. Node, Java/Jetty vs. Node, Node vs. lots) and rest assured that despite scaling, some portion of your latency is baked into your language/framework performance. Your users are paying milliseconds for your choice of an interpreted and/or dynamic language.

the forum for the "D" language. seems really fucking fast for a forum ... find out why.

an API is just a combination of a protocol and an endpoint.

c++ style guide for the jsf

It’s true. We occasionally take a break from drinking moonshine and shooting beer bottles to do real engineering.

timezone picker.
TODO: redo with static images, w/o using the slippy map.

reccd to read after real world haskell in http://news.ycombinator.com/item?id=3824732

render screenshots of web pages with a headless browser.

load testing tool

apache, linux, mysql, vitess, zookeeper

... todo: look into computing efficiency, esp. max theoretical efficiency.

includes how to set up vagrant so do shared folder with NFS.

For typical projects I feel like I'm building more tools into my REPL workbench. I don't write scripts that I call from the command line, I write functions that I call from the REPL, and use the slime and Emacs environment to create and interact with data, whether it's data from a file, from a computation, from the web, a database, etc.

I find it really helps to have small, focused functions that are easy to follow and that do one thing and do it well. The fine granularity of testing, tracing, intermediate values, etc. can help wire together a very useful set of behaviors from a small core of simple functions.

... they have SOA ... the high level request handler will be running in application container. Communication with the services is managed on a per-process basis with a thread pool for each service. strat for failure: look for usable stale data in cache, queue writes, use generic data instead of user specific data, empty response and deal with the missing data at the high level.

network timeouts are set carefully

Snappy framing format description

uses pep8 tool and fixes problems.

some points on load testing, and instrumentation. nice plots.

"When you have all this data, use a real data analysis tool to look at it. Learn some R or NumPy/SciPy. Instead of using Excel or a clone for data analysis, consider learning a numerical computing language such as R. For example, in R or NumPy you can write a script that takes all of your raw resource consumption data (CPU, RAM, IOPS, etc) and runs correlation tests against the latency data. Try to do that in Excel! Oh, you can then use that script in your monitoring."

excellent explanation of levelDB

list looks good

domain-profiler is a tool that uses information from various sources (Whois, DNS, SSL, ASN) to determine what decisions have been made regarding a domain or list of domains.

chapter resources
Front matter (incl. table of notations) pdf
01 Boolean retrieval pdf html
02 The term vocabulary & postings lists pdf html
03 Dictionaries and tolerant retrieval pdf html
04 Index construction pdf html
05 Index compression pdf html
06 Scoring, term weighting & the vector space model pdf html
07 Computing scores in a complete search system pdf html
08 Evaluation in information retrieval pdf html
09 Relevance feedback & query expansion pdf html
10 XML retrieval pdf html
11 Probabilistic information retrieval pdf html
12 Language models for information retrieval pdf html
13 Text classification & Naive Bayes pdf html
14 Vector space classification pdf html
15 Support vector machines & machine learning on documents pdf html
16 Flat clustering pdf html html
17 Hierarchical clustering pdf html
18 Matrix decompositions & latent semantic indexing pdf html
19 Web search basics pdf html
20 Web crawling and indexes pdf html
21 Link analysis pdf html
Bibliography & Index pdf
bibtex file bib

auth writing abt. db testing on HN, check source.

omg omg omg

If then I use a pre-generated fast array and the specialized areduce function (to match his specialized idx-sum function), I get 16ms for 300k, 22ms for 3m and 230ms for 30m.

guide to securing web apps.

todo

scaling (vert) w/ Varnish etc.