I periodically laugh from absolutized linear-logical thinking of some CEOs in a way like: "if this worked for X, then it will work for Y". For example: "if regular and strict schedule worked for factory workers, then it should work for software engineering professionals". "If on-site work is necessary for factory and land workers, then it's necessary for all workers (including software engineers)". The thing is that generally you can't predict future events and results based solely on past experience, which is even a classic example of pulling an owl onto a globe (though past experience is a good bias). Software engineering requires different cognitive-energetic load than linear factory working. I notice it for myself and when I mentor junior developers. Software engineering does not need commute to be performed efficiently (commute even contributes negatively to it). And I know that there are another sides of forcing on-site work and time tracking, for example. But they don't benefit in terms longer than several days. And this particularly raises a question on sanity of forcing on-site work. Deciding costs for SWE employs different models and strategies than for linear working. For this reason probably we can't automate even coding to so-called AI. AI helps with boilerplates but this is enough.

#blog #thoughts #thinking #softwareengineering #work