- larpers and students and shit who don’t even have a job where they write code but comment like they do
- people who don’t do shit for 3/4 of the day and don’t want to be accountable for that
- people who work with too many idiots
Probably lots of other reasons. Personally I think it’s fun and useful, but I wouldn’t want to do it exclusively. Maybe scheduled hours a couple times a week. LLM aided development can be very similar experience.
Also a great teaching tool.
Big part of my job currently is taking slop level Pinocchio prototypes and turning them into a real boy. I’ve decided that I’d much rather have all of the conversations these people have had with Claude when creating the project than the final code artifacts. Hopefully we get more tooling in that direction.
God forbid a well-meaning person need privacy and solitude to get work done in a meaningful way, just as other inventors and geniuses did in their private homes throughout history, and later came together with others to share their findings.
This idea that we need to be married to other co-workers throughout each day has all the same dysfunctional attributes as a nanny state or a daycare, where employees are treated as untrustworthy and needing to be monitored at all times.
The fact that talented engineers are able to contribute meaningfully, with few errors, and with brilliant solutions, all on their own, is proof enough that coding in solitude is a completely reasonable preference, that's shared among most of the engineers I've met in my career.
NO TOM I DONT WANT TO FUCKING MARRY YOU GOD FORBID, ME, A TRULY TALENTED ENGINEER AND GENIUS, TRY TO GET ANYTHING DONE FUCK THIS FUCKING NANNY STATE BULLSHIT as you return to clipping your toenails in the office
Truthfully, I don't mind pairing on something if someone needs help and doesn't mind doing it asynchronously instead of sitting on a video call all day pointlessly when Slack will work just fine. :)
The reason I went to hyperbole with this one was because a prior startup I worked for required everyone to pair on every ticket, whether they liked it or not. I simply refused, and they were fine with it, because they liked the work I did. If I needed to collab on anything, I'd just talk to the other engineers. And guess what? We survived and did amazing work together as a team!
This was modeled after my former coworker Tom who had to be told not to clip his toenails in the open office, and then told not to do it in the lounge room even if he was alone
- antisocial people
- larpers and students and shit who don’t even have a job where they write code but comment like they do
- people who don’t do shit for 3/4 of the day and don’t want to be accountable for that
- people who work with too many idiots
Probably lots of other reasons. Personally I think it’s fun and useful, but I wouldn’t want to do it exclusively. Maybe scheduled hours a couple times a week. LLM aided development can be very similar experience.
Also a great teaching tool.
Big part of my job currently is taking slop level Pinocchio prototypes and turning them into a real boy. I’ve decided that I’d much rather have all of the conversations these people have had with Claude when creating the project than the final code artifacts. Hopefully we get more tooling in that direction.