[prepend]

Flow state is really powerful, but it’s not constant. I don’t want to be in flow for 40 hours per week. And to tell the truth if I get a few hours of flow a week, I’m lucky.

So I don’t want to shut the door on any interactions in the unlikely chance that it interrupts me in my optimal state.

What I like to do is block off “deep work” in my calendar a few times a week. Then people can think about if they want to interrupt.

This has let me look at these “quick call” or “hi” messages as just part of being human and having a pleasant team where people are happy to interact rather than dings to maximum team productivity.

[mewpmewp2]

Unfortunately as of lately my professional life has been terrible for flow state due to various reasons related to working in a corporation. So I might consider switching jobs. Interruptions, blockers, depending on others, etc.

But I love being in flow state, luckily I can still do it with my side projects. With side projects without being interrupted I can easily spend the whole day coding and at the same time building 10x to 100x as much as at a corporation job. Of course it's less realistic in a large company to have it, but I just wish my actual work was like that.

Maybe if I could make one of my side projects to bring in enough, I could just do that. I would say that would be a dream.

> This has let me look at these “quick call” or “hi” messages as just part of being human and having a pleasant team where people are happy to interact rather than dings to maximum team productivity.

It just depends on the human type I guess. Extraversion vs introversion.

[ath3nd]

> But I love being in flow state, luckily I can still do it with my side projects. With side projects without being interrupted I can easily spend the whole day coding and at the same time building 10x to 100x as much as at a corporation job. Of course it's less realistic in a large company to have it, but I just wish my actual work was like that.

Unpopular opinion: a very small team of skilled programmers that have experience working together and are often/continuously in flow (whether alone, or pair programming), can 10x/100x outpeform multiple teams in a large corporate setting.

[mewpmewp2]

I definitely agree with that, and I have been on both sides of the coin, with a little team doing a lot of projects very quickly and also a corporation job where things move very slowly. Also having done so many side projects.

The unfortunate usual thing is though that the jobs that pay a lot usually involve a lot of people. Because when a small group of very productive programmers start out, their business is not proven yet, but when it actually is proven and will start to make a lot of money, there will be a lot of people hired and which breaks what it had initially.

And the more people and teams you put on something the slower the pace will be per developer, for sure.

There are moments in time in a lifecycle for a start up or a business, where there is that golden point, but it always seems temporary.

[ath3nd]

> Because when a small group of very productive programmers start out, their business is not proven yet, but when it actually is proven and will start to make a lot of money

What if we stop at making a lot of money in a proven business, and don't hire more unless absolutely necessary? Keep the team small and lean, retain the talented people who brought you here via profit sharing, and just...relax?

I am surprised that this model is almost non-existent.

[jodrellblank]

It is an unstable model; if it’s only necessary to hire when someone leaves, there’s no slack - what if someone gets long term sick? What if someone feels burnt out holding the thing up but nobody else wants to hire more - by the time that person leaves it’s necessary to hire more but also late to start the hiring process to find the perfect one replacement and who has spare time and redundant knowledge to train them?

When it will start to make a lot of money, it will do that by having lots of customers, therefore more support requests, more payment troubles, more feature requests, more scaling concerns, reliability and maintenance.

When it starts making money, competitors will notice and may start copying it; relaxing will let them catch up and pass you and take your customers.

There is always entropy, things fade, decay, things need continual “growth” just to stay in a steady state - getting that growth perfectly tuned so it doesn’t grow bigger and need more employees, and doesn’t shrink and wreck the company, it precisely counters the decay, is much harder than growing bigger.

Lifestyle business is not unheard of, some people hit on a great idea and execution and it’s a money printer for them, but it seems that more people who try it either can’t get enough money, or struggle to do everything without hiring anyone until they burn out, or have to hire someone and then have to get more income to pay them and are in growth mode, not steady state.

[jrs235]

Because few are able and willing to NOT take outside money (get investors). Investors want to invest in a cancer not somebody's life-style business.

[jakupovic]

This is much better and normal rather than the bs the original author is proposing where they are the main character and everyone caters to them