As I am getting back into coding once again —and yes, stay tuned for a build-in-public journey that is soon to start— I am reading more tech blogs. And I love to see pragmatism applied to a field of perfectionists and "well-akchyually" agitators.

Perfect code does not exist. So much is clear.

But good code might also be overrated.

What I try to do in my coding work is to write legibly as if I were to hire a junior dev to take over the work (because that's where I want the business to go.) And that, on so many levels, is good enough. Talking about Levels and good-enough code, even Pieter Levels (yeah, I just made that happen) told me on the podcast recently that he is putting more effort into code quality. But not too much.

It really is like a video game. Achievement hunting, leveling up, min-maxing your gear and work-life balance… it is a striking resemblance.

And you get paid to do it.

I've always been a fan of remote work, and was already doing that back in 2013 when I worked for a Silicon Valley startup from Germany. It was a pretty weird time, quite literally: I was in Germany but worked in San Francisco time — a 9-hour time difference. Let's just say I didn't see the sun much, but that sacrifice was definitely worth it.

Today, remote work has been professionalized quite a bit, and developers can pick employers for their remote work policies. And if I were to start a new SaaS business today, I would make it remote-first for sure. A single glance at my Twitter activity feed shows a global talent pool that I'd be stupid not to tap into.