Erlang by Example, Accessibility, Good StackOverflow Answers, Testing, Flexbox, HTTP Server in C, Icecream Affecting Cars.

Erlang/OTP by Example

Erlang is one of the languages in my "to learn" list and having a "by example" site really helps -- at least, it helps me a lot with Rust.

The 6 Most Common Accessibility Problems (and How to Fix Them)

Accessibility is always import. And knowing that there is something akin to OWASP (common web application insecurities) that puts a list of common problems is always good. And, on top of that, having a list of easy to fix problems is even better.

Parsing city of origin / destination city from a string

Although the answer is quite long and not "Just use X", this is the kind of answer StackOverflow should aim for: Even if the question seems absurd, there is a long explanation on how to do it, every step and problems on every step, till the point of "it's not that simple".

against testing

Someone took my words about testing and took it waaaay too far.

Sure, testing everything feels wrong, but you can see things are wrong when someone says "Tests are very brittle, breaking due to entirely innocuous changes in the code". Here is the problem: You're a fucking moron if that happens; you're testing the implementation not the behavior. So sure, it will be brittle 'cause you wrote the whole thing wrong.

That is one of the points I really don't like the so called "unit test" -- as in "testing every function". Behaviour is not contained in a function, but it appears when functions interact. That's why integration tests feel more "right" to me: We ignore how things were implemented and focus on how the system should behave.

So yeah, testing is wrong and you may dislike it, specially when you writing it wrong in the first place.

Coping with flexbox

Flexbox is in all rage these days in web development, mostly 'cause it fix the damn "Center this vertically and horizontally". And this kind of explanation, going through the basics, is always welcome.

httpserver.h: Single header library for writing non-blocking HTTP servers in C

One of the weird things about C is that there is a lot you can do with it, including a single file for building a whole HTTP server.

"My Car does not start when I buy Vanilla Ice Cream", said a Man to General Motors.

I'm a sucked for this kind of story: Things don't work because some weird random, seemingly unrelated event.

It reminds me of the story "My password doesn't work when I'm standing up".