Markus Tacker · Software Crafter

Sat 9 – Sat 16 January 2027, in Kiilopää, Inari, Finland.

tl;dr npm 12 makes dependency lifecycle scripts, Git dependencies, and remote tarballs opt-in.

We are at an inflection point that will have a huge impact on how we write software: Meta is investing billions of dollars into building an LLM that is capable of writing software.

I have been iterating on Event Sourcing and CQRS architectures for nearly a decade.

tl;dr LLMs are excellent at scaffolding code that follows an existing pattern.

Error messages are the only piece of documentation you can be sure people will read when it is relevant.

Build scalable systems by separating concerns.

You should rebase a branch against the main branch before "merging" it, so that there is no merge commit.

This long wrapping in a if / else clause makes the code hard to read.

A Pull Request should only address one change at a time.

At work I don't like when people say sorry about something they can't control.

Bad myMethod(arg1, arg2, arg3); Good myMethod({ arg1, arg2, arg3 }); Reasons this removes the Connascence of Position (CoP) because the order of arguments becomes irrelevant arguments to methods can easier be created programmatically Watch out for remov…

I prefer saga branch over master because I think that this name (which means a long continuous recollection of histories) better reflects how development happens.

It's important to have an automated way of formatting source code to eliminate discussions around style and remove noise from diffs.

Don't use global state like env variables in modules, only on the very top-level or in one central location.

A .gitignore in a project should only cover artifacts caused by the contained source code, not those caused by the personal choice of editor and/or environment of a developer.

I've been building serverless applications on AWS for over ten years.

https://www.youtube.com/embed/2KeBxWAdndo I was first paid to write software in 1997, now 27 years ago, and if there is one skill that had the biggest impact on my career then it’s the ability to deliver working software that doesn’t break.

I can fully recommend the book for developers who are starting to work more with serverless but as well for technical managers who want a better understanding of the potential of the serverless paradigm and the mindset shift needed to tap its full potenti…

This is a small lecture I gave to a team of students on how to approach designing the software architecture for a cellular IoT project.