[Article] Rails has won
This is a response to My time with Rails is up. I recommend reading both articles. While Rails is bloated and there are technically superior solutions out there, we have to accept the reality:
People think that because something is “technically superior” everybody else should blindly adopt. But this is not how the market works.
[Article] How To Sound Smart At Your Next Team Meeting
Never attribute to malice what can be adequately explained by stupidity. 80% of the effects stem from 20% of the causes. Any code of your own that you haven’t looked at for six or more months might as well have been written by someone else.
[Article] Do You Take Yourself Seriously?
This is a periodic reminder for myself.
ab telling you wrong things
I was running some benchmarks and I noticed that
ab was reporting few “Failed Requests” on every benchmark. It turns out this is not related to HTTP status codes, but it is because the tool compares the length of subsequent responses with the first one. If they differ, then it considers a failed request. For dynamic contents, they will be always different!
-l option “fixes” that:
-l: Do not report errors if the length of the responses is not constant. This can be useful for dynamic pages. Available in 2.4.7 and later.
ab -c 10 -n 100 -l -r -T 'application/json' -p data.json 'http://example.com'
[Article] Am I really a developer or just a good googler?
[…] programming is now a job like any other, because everything you need to do to satisfy your BizDev team can be learned without reverse-engineering the prototype for Thag’s Move Things Better Octagon.
Thanks for reading! 😬