It's coming from the job interview domain... but I wonder if it could be more largely useful due to how simple it is (but not easy mind you). I guess I'll experiment with it for my next project postmortem.
Excellent analysis and explanation of the stutter problem people experience with game engines. It's an artifact of the graphics pipeline becoming more asynchronous with no way to know when something is really displayed. Extra graphics APIs will be needed to solve this for real.
A few examples of why yaml is getting out of control. It is very very error prone at this point.
Nice resource to get started with Prolog.
A love letter to Makefiles. A couple of interesting tricks in there.
Nice nugget reminding us the early steps and basic mechanisms of the CPU life at boot.
I'm more and more tempted by this kind of approach. Managing architecture models using code seems fairly neat. That said I wish we'd have better free software tooling for that, I find it still fairly limited. Maybe I should check out the Haskell library which is mentioned.
Interesting little tool. I usually use make for this kind of things, but it seems to bring some benefits for non build tasks.
Interesting approach although you probably don't want to do this systematically. For some applications it is a good idea.
It's comiiing! OK... not quite yet. But if that prevents your sleep here is an easy way to check.
Not very scientific, but indeed thought provoking and taps into safety considerations.
Always a good idea to seek reduction in time spent in meetings. I've seen this being too often a drain. Can get quickly out of control.
A very interesting metaphor. Indeed on social media we're not dealing with gardens.
This is apparently a somewhat common mistake. Something is apparently not easy enough to handle and error prone.
It's clearly a choice in management style. For such choices, always keep in mind the trade offs this create, maybe it'll push you to revise your choice.
Since I'm also a bit of a nerd of nice programming language features, that's an interesting list (mostly) coming from less known languages. Some of that syntactic sugar would be welcome in more main stream languages I think.
Time to look a bit at the maze of WebAssembly runtimes. Good overview on how they currently perform and how well they are documented or easy to use.
This what we should strive for with our tests. I like how he keeps it flexible though, again it's likely a trade-off so you can't have all the properties fully all the time. Still you need to know what you give up, how much of it and why.
Excellent piece, looking back to history to justify why microservices are mostly a fad. Check what your needs really are and depending on them pick the right way to decompose the problem or organize your teams.
A little reminder that those too often forgotten execution policies for C++ algorithms actually exist and can give interesting results nowadays.