> As an industry we're surprisingly very behind in normalizing this.
This is great for people whose own pace is reasonable and matched to their compensation. If you’re paying someone 50th percentile compensation and demanding a 90th percentile work pace and output from them, you’re just going to have endless turnover as you burn people out.
Conversely, if you’re paying 90th percentile compensation and you have an employee moving at half the speed of their peers, eventually you’ll get fed up and replace them with someone better matched to the position.
But this all breaks down when you get into the weirder ends of the market. Self-pacing works great for you because you can put in the work to deliver $500K/year of value and companies appreciate it. It doesn’t work for many people whose idea of a workday is to put in 1-2 hours of focus and then browse the internet all day, which is a larger portion of the developer population than I would have guessed before becoming a manager. Other people can’t help but wander through tasks, get distracted by rewrites or new frameworks, needlessly refactor working code, or otherwise do a lot of activity without producing a lot of work. Both of these fault modes benefit greatly from the pacing and structure of management.
There’s no one size fits all approach. I think solo dev contracting is a great option for some people, but the type of person who can self-manage, sell themselves, network, and retain self-discipline isn’t all that common.
I think this is a great example of how different people thrive in different environments.