nikovirtala.dev

In the picture you can see me doing something completely extraordinary: giving a presentation and a live demo for the unit!

I talked about big numbers (billions) and small numbers (dollars) in the same sentence and how to process multi-tenant data in a single-tenant manner — let the rest of the context remain as a secret, but there is a huge pile of paper and #AWS #serverless event-driven architecture involved 😁

By doing it I surpassed one of my imaginary boundaries — how is that possible? 😮

As a musician myself, Mr. Kelsey Hightower’s words inspired me quite a bit here:

“I approached those live demos like a Jazz musician. I knew what I wanted to show, what it should feel like, wrote the code so I had confidence it should work, went on stage and improvised the whole thing.”

So. Demo, easy? Mastering your crafts through thousands of hours of tireless learning and exercises. The result — unforgettable!

Yesterday, I wrote about how developers use only a few hours weekly to write the code.

It evoked a lot of great comments, like:

– “Coding is a small part of what we do.”
– “Developing is much more than only coding.”
– “Actually coding should be a minor part of great developer time usage.”

That’s all true. The developer’s work is much more than coding, but what these comments missed was that the post was all about *focus* and *productivity*, not coding.

The problem is that distractions are everywhere, and our schedules are so fragmented that we cannot focus on our work — coding, documentation, learning, thinking, problem-solving, or anything that requires our full attention. Fifty-two minutes — it cannot get you even started!

I couldn’t find it in my notes when I first met with Paul Graham’s classic “Maker’s Schedule, Manager’s Schedule”, but it has been an essential resource on understanding my own, as well as any fellow maker’s way of working. I recommend you read it and possibly the Farnam Street excellent blog “Maker vs. Manager: How Your Schedule Can Make or Break You” too, and I promise you will understand my perspective better.

I end this post with Paul Graham’s words:

“All we ask from those on the manager’s schedule is that they understand the cost.” ✌️