Wow, don't know where to begin...
1. this article seems to be aimed at startups, but the author then goes on to complain about having to work 8-5 ( good hours for a startup).
2. "Let the bad actors fail" I've met very few people who are actually trying to game the system, the vast majority of people perceived as "Bad actors" need managements help to align their goals and values with that of the business.
3. The title implies this is an issue of trust, where as it seems that it's more about preference and fit. Some software engineering problems lend themselves more to an in-person environment than not. For instance, when I was working on an oil sensing project, All I did was write software but I had to have the hardware close for testing my software. They sure aren't going to let me drag 20k worth of equipment home in my honda.
4. ROWE, how do you measure the output of knowledge workers especially programmers? If anyone figures it out write a book you will make a bajillion dollars.
Experienced developers can work as well as, or better at home. Even in a startup; especially in a startup where time is important and commute can be expensive that way.
I work on embedded frequently; I have way more than $20K of equipment on my desk right now. Not to mention old projects in boxes and on shelves. That's absolutely not an issue. If I need it and need exclusive access to it, in the office or on my desk is all the same.
And measuring output? Why, by performance of course. And by the value of the work done. So I can earn well on embedded work whenever that comes my way, because its not a common skill and I can do it quickly. The market sets the value; there's no mystery to this.
Hey Joe, I also work from home full time but as a backend systems developer. I was not trying to highlight that it would be impossible for someone with hardware to work from home, simply that in some cases it's not feasible or doesn't make sense ofr the business.
So, when a team of 12 delivers a product that makes X amount of money, we say to ourselves, "Each individual on this team has an output of X/12 ? That's silly.
Also, your comment, "Why, by performance of course." What does that even mean?
Would love to hear more detail about how you would measure productivity and output of a programmer. Because there are millions of managers around the world who have yet to figure it out.
