"I must not invite a meeting. Meeting is the time-killer. Meeting is the little-death that brings total obliteration. I will face my calendar. I will permit the invites to pass over me and through me. And when it has gone past I will turn the inner eye to see its path. Where the meeting has gone there will be nothing. Only I will remain."

How to manage software complexity?

"If a design appears complicated, try a different approach and see if that is simpler."

"The first approach is to eliminate complexity by making code simpler and more obvious. The second approach to complexity is to encapsulate it, so that programmers can work on a system without being exposed to all of its complexity at once. Isolating complexity in a place where it will never be seen is almost as good as eliminating the complexity entirely."

I feel odd tingling while watching this new night lamp. Perhaps, I'm half a wolf. 🐺

This is a fun little meme, but at the same time, it's also slightly troubling. Have we developers secretly learned to think that our work-in-progress code is, by default, utter garbage that we must hide in a branch?

Does the code get any better when we polish it for days before integrating? Why would working in isolation be better than rapid and early feedback? Is the lack of self-esteem an issue preventing teams from working in small batches and adopting continuous integration?

Shh, Teams. No they don't. I don't want to open you and try to check the messages after multiple failed logins that always tend to happen.

If you recently upgraded to 4.4, you might have been bit by the error handling within a catch clause. Caught errors are now cast to 'unknown' type by default which is generally narrower and thus safer.

Fortunately, there's an easy fix via a helper function. All we need to do is to check the error type and act responsibly. Alternatively, you could disregard this change and cast the error as 'any', which is an anti-pattern.

Despite this being the undeniable truth, maybe pick the longer version the next time you're selling DevOps to an organization.

Unbearable apartment temperature requires radical actions.

Hammock and Borjomi to rescue. Could live here the rest of the summer.

I came home from the vacation trip and having some alone time since ages.

Enter New Order. 👌

A convenient reminder that my technical musings in a semi-long format are also in LinkedIn, should you use that. Please, consider just following me there, but if you suspect we *know* each other through some strange occurrence I'm happy to connect too.

linkedin.com/in/nikoheikkila/

Treasures from the shopping trip. I've been searching for good versions of The Name of the Rose and Metropolis for some time.

One of life's unexpected but valued joys: bumping into a street food place serving authentic Gai Pad Med Mamuang dishes - among other things. 🔥

A healthy dose of beach wellness today. I remembered sunscreen but forgot the chair and parasol. 🤷‍♂️

It turns out, medieval people knew quite a lot about software development. Scope creep and rushing features to production while sacrificing quality was not unknown to them.

Picture from the Book of Job, ca. 1330.

I noticed this pull request in my inbox today. The author states in the title they are refactoring a feature.

This is the best example of how you can smuggle any change you want into a codebase. All you need is to surround it with a diff of several thousand lines.

Here's an inspirational game for your next password validation logic. Can you complete it?

passwordfromhell.com/

Show older
Mastodon for Tech Folks

This Mastodon instance is for people interested in technology. Discussions aren't limited to technology, because tech folks shouldn't be limited to technology either!