The Watercooler Squad is an important place for all things unimportant and nonsense at daily.dev. It’s designed to waste your time and distract you, buckle up 😻 🤹🏽‍♀️

Watercooler

Programmers are compared to human pressure cookers due to the high levels of stress and pressure they experience in their work.

Programmers = human pressure cookers

Pressure is really bad for programmers (at least me). The end product will be much better, when I have time.

I work great under pressure (thanks to ADHD)… as long as it’s a TEMPORARY state. It’s all in finding the sweet spot where there’s just enough “pressure” to get those good hormones going, but not enough that it’s becoming the norm. Stress isn’t a bad thing as long as you get plenty of time to recharge.

I think that “working under pressure” isn’t necessarily a bad thing. Personally, I sometimes have very good ideas when I have to work under pressure (but please don’t ask me why my brain works like that 🙈). Of course, I don’t want to work under constant pressure either. But every now and then it can be good for something … at least for me 🙂

My answer is usually, “Well, can you?”

This point of view is pretty fun. Let say this is our cooker specs
<ul>
<li>Capacity: 8h (can use 1 time per day)</li>
<li>Recharge time: 16h</li>
</ul>
But unfortunately, the user tend to use us with more capacity (or reduce recharge time). The way they used us somehow similar to expect 9 women can give a baby birth in 1 month. Days after days, months after months, the cooker is broken. For years facing with that problem from user and now we have smart-cooker, AI-cooker, but the user behavior stay the same.