morgelgluff

It used to be the norm to mix up the groups every three years, when transitioning between low/mid/high school stadium.

I appreciated that change of social dynamics every time.

Strikingly warm in Sweden as well. Geothermal heat pump does work a few hours per day, anyway. It drops far below 10 degrees celsius at night and my house is not modern enough to manage comfortable temperature with only waste energy as source.

I’m sure they are great fun, but I am not very happy about the increasing popularity of eRacers.

Those motors really do make a difference in how fast and hard people ride. And for which trails get frequented by bikers.

Just over the past few years there has been a big increase on my local trails and there is a negative impact for all the walkers, hikers and runners that used to dominate them.

The soft forest paths get turned into mudpits and conflicts arise when people are surprised by silent speed demons in narrow passages.

A name is just a sound other people make when they want your attention.

You are not just ”a person” when you are a parent. You are a person with a very special role and you spend a lot of time acting in that role. As I see it, the border is fuzzy and the overlap large, but the role and the person are not the same.

Those observations pertain specifically to developers who howl about vague technical debts. Those tend to be juniors.

Seniors point out specific issues with specific consequences and lay out specific actions to resolve/mitigate. The term “technical debt” isn’t usually needed in that case.

Technical debt terminology is a fig leaf for “I dont understand and I wont put in the effort to learn”.

My pet issue with technical debt, is what happens when engineers are allowed to pay it down.

In the best case people embark on well-informed yet insane ”version 2.0” over-engineering binges. This can be nice, but is often a waste of time.

Quite often the ones who cried “muh technical debt” in every meeting simply did not understand the problem being solved by the debty code, and end up making something novel but equally problematic.

In the worst case, you have a combination of ignorance and best-practice-hysteria that gets applied to actually-fit-for-purpose code. Then the 200 lines of performant and correct code that takes two hours to fully understand, gets turned into 2000 lines of deeply nested class hierarchies mixed with immutable FP-wank that takes several days to get a grasp of and both fails to handle real-world data (“not in the specification!”) and tanks system performance (“premature optimizations!”).