

…wat? In what kind of shop are you working?
…wat? In what kind of shop are you working?
UpMiiGos as well.
Even in a sewer something has to be swimming at the top. They individually hope to be that something.
Personally I find the smell of slightly burned vanilla very charming, unfortunately we don’t smell much under the breathing equipment. So, kinda wasted effort.
To be honest, it wasn’t until my late thirties that I finally mastered the crucial skill of identifying my own needs and transforming them into clear, appropriate communication. Before that breakthrough, I constantly defaulted to avoiding conflict—thinking “I shouldn’t bother anyone,” “I’m not entitled to make requests,” or “my primary role is ensuring everyone else’s happiness.” This self-effacing approach actually made me difficult to be around, as the unresolved internal conflict was painfully obvious to anyone with even minimal emotional intelligence. The irony is that in trying so hard not to inconvenience others, I created a more uncomfortable situation for everyone.
Change shop, my man. My work desktop consists of a tiling wm, usually has one or two instances of my favourite IDE running, of course has various shells open and the only time I’ve got LibreOffice Writer open is when I’m crafting a report for a customer. Although a few of our young developers are currently building a tool chain that would make some sort of enhanced markdown the default format for human readable stuff and that would fit a lot better into our “a project is managed in gitlab” workflow.
I am not a developer, mind you, I am just creating architectural concepts and I implement them. How do you even do that without automation, automated testing, redeployability and all of that? Hell, even when a project requires talking to bare metal, the first thing I’ll think about is “how do we get out virtualization layer onto that automatically within the constraints of the customer’s network?”.