In summery rivers,
The kids are swimming,
Their naked asses
The moonlight gently kissing.

I've studied the effects of electromagnetic fields on patients with carotid stent implants during my PhD. I've never talked with any patient nor seen such medical devices even to this day, fifteen years later.

Another kind of jailbreak. Painful to write, but I just had to get it out of my system.

Some ideas from my personal style of software development that I've developed over the years. It is based on the ability to change code quickly, to see the effect of those changes instantly, to build and have a live system in front of me, to throw code away and iterate over solutions and adjust expectations and the requirements in the process.

C's lack of power in the automotive industry has lead to a proliferation of special tools and domain-specific languages (DSLs). Engineers here spend a lot of time learning, mastering and often struggling to make these tools work with one another, as they are all built by different vendors or standardized by different committees, a problem each new vendor tries to address with their own "magical" and expensive solution incorporating everything into one new tool, which only makes matters worse.

...then why is not everybody using it? This question makes no sense though an answer is often searched for it. Great for what, for whom, in what circumstances, with what drawbacks and compromises? Life is full of such questions and scenarios. If I were to choose, I would live in the best house, eat the healthiest food, do whatever the heck I want all day long. Reality doesn't work that way.

Or why learning to program without ever touching pointers, recursion, syntax trees or delving deep into OS internals among others, leads to lethargic software teams in the long run, those constantly growing organisms clumsily developing their own peculiar ways of solving problems with the help of legions of tools and processes.

A generic distinction between the style and motivations behind big, corporation-like software teams and small, independent ones.

I've once wondered, are street names dominated by male artists, heroes, scientists and politicians? So I went to openstreetmap, taken each country in turn, parsed and cleaned the relevant tags and made a list of those famous people of the past, pics, wiki links and summaries included. Spoiler alert: everywhere the past is almost always bloody.

How to group all shells, code, web browser and all other Emacs buffers into different tabs and switch easily between them with tab-bar mode.

A peculiar book list for the adventurous and free-spirited on which to build a solid base for their future software adventures.

Ditch the classic keyboard and your back and wrist pain together with it. Try a split, fully-programmable keyboard and discover a new world of possibilities. You'll never go back after.

Some examples of Lisp features which are non-implementable in C, together with an analysis of the different levels of power between languages.

My experience with building my own Emacs, text-based, music player and discovering the build one to throw one away mantra.

Over the years I've learned to use my palm to press the controls keys after some advice I've found online. This is an article encouraging that method to potential users. I've since replaced it with a split keyboard, but it has served me well all this time.

Romanian translation of the famous Lessons In Electronic Circuits. It includes plenty of material related to electric and electronic circuits and it starts at the very beginning with ample explanations and step by step instructions and real-world examples.