Moreover there are studies showing that if people socialize and get to know each other a bit before working together, there are more chances to collaborate and to reduce conflicts.
Also, and this is something a lot of the managerial class people don't want to hear:
Your job as a sw engineer/architect is to resist the "just ship it" pressure from the management as much as possible. So unless you own what you're coding and you really need it out of the door for your own benefit, if more time makes your work more professional, then take more time. Anyone telling you otherwise is a 100% hack. You are not an automaton that takes in JIRA tickets and spits out hacky code as soon as possible. Or at least you shouldn't be. Not to mention that not taking time (doing things properly) is incredibly taxing on your psyche and you WILL burn out. There are only so much garbage tasks you can take.
It's worth repeating: Unless you have a stake in the company, it is NOT your job to make sure the company is the most profitable it can be. Your job is to create great software. What's great software? The kind you'd be willing to put on your resume without feeling bad. This is the thing that will ultimately make you feel good about the work you're doing. Hitting that arbitrary deadline for a 1425474th time may feel like a relief but it's short term and a form of negative motivation - and in the workplace, those NEVER work over a long period of time. So RESIST that pressure from the top and do your work properly. If they fire you, then who cares, the only way up these days is job hopping anyways.
Is it a hobby for passing time? For pleasure? For the beauty of the code?
Could be. But most of the time, you develop in order for the software to perfom a task someone needs.
And that should be your first focus: to develop something that brings value for its user, and develop it as efficiently as possible. After all, what's the point of a software if nobody uses it? So no, your job is not to create great software, your job is to bring value to users.
In my career, I've mostly seen the developers pleasuring themselves with overengineering, bloating code with features nobody needs, and writing lines to anticipate future developments that never came. Rather than the opposite.
So I think the challenge is to remain minimalistic, that's hard, and that's what the original post is about.
Imagine lecturing people about saving the planet while defending going out to eat in restaurants or ordering all your meals.
Why would I run a docker container, a webserver, start a browser, navigate webpages... just to do some operations on a pdf locally?
A few KiloBytes native program like PDFtk (https://www.pdflabs.com/tools/pdftk-the-pdf-toolkit/) does the job perfectly.
I don't understand what is the point of bloating softwares like this. Not even speaking of the very bad consequences for the planet.
My friends who learned French had similar struggles in France versus elsewhere.
The tone on this thread has that jaded and defeatest "management sucks" attitude that I find most often in the least productive engineers regardless of how they work.
TL;DW: (if I rember correctly) Bulbs with shorter lifespans are generally more energy efficient. There was good reasons to not making bulb that last forever.