Hi there!

I'm Mickey. I decided that programming full-time is not for me and embarked on the adventure of finding a 20h job instead.

I succeeded and you can too.

Truth be told, I'm a bit of a hippie and I don't vibe very well with the traditional, strictly capitalistic approaches to building software and working. Here's why.

The Why

Why not full-time?

If I got a 100 dollars every time I’ve watched a colleague of mine watch a YouTube video instead of coding, I’d be quitting altogether with all that money. If I got a 100 dollars every time I’ve spent hours trying to fix a problem at the end of a long, 8-hour day that in the morning “resolved itself” in 5 minutes, I’d pay you for reading this just because I couldn’t spend all that money in a lifetime.

 

Humans cannot efficiently code 8 hours a day, 5 days a week. Period. If you can, you are an exception to the rule but I’d still push back on your intuition of how sustainable that is and what it does to your thinking, communication skills, and long-term well-being.

Why 3 days a week?

I experimented extensively with my work hours when I was my own boss at SoilSense and concluded that I can code efficiently for around 20-30 hours a week, depending on the type of tasks I handle and my current mental capacity.

 

Does that mean that you should also work 3 days a week? No. All I want to say is that you don’t have to be stuck in your full-time job if it doesn’t suit your lifestyle, needs, or desires. I hope my story can inspire you to pursue the kind of flexibility that will let you live a happy, fulfilling, and comfortable life.

How do I work now?

After exiting SoilSense I took a 2-month break from programming and decided that I want to keep my work-hour flexibility while removing the stress of being the decision-maker. I started a 3-day a week (22.5h) job at a digital agency, Kvalifik.

Truth be told, I'm a bit of a hippie.

— Mickey —