I don’t know man. For the past 6 months we went with approach “Fuck scrum, let’s just work”. It didn’t go well. We were really disorganized, everyone going their own direction, things being overlooked, …

When a new colleague joined recently, he suggested taking more structured (scrum-like) approach. Things improved immediately.

Like I don’t know how you want to call it - scrum, kanban, whatever, I don’t care. But you need some structure in your team and you need some meetings where you talk about status, about looking back at things, about plans for next weeks, …

This is fake, no one can code like that

Here we go!!! I was expecting the enshitification of this thing for past couple of years

small tasks that you don’t expect to grow in complexity

On one conference I heard saying: “There is no such thing as temporary solution and there is no such thing as proof of concept”. It’s an overexaguration of course but it has some truth to it - there’s a high chance that your “small change” or PoC will be used for the next 20 years so write it as robust and resilient as possible and document it. In other words everything will be extended, everything will be maintained, everything will change hands.

So to your point - is bash production ready? Well, depends. Do you have it in git? Is it part of some automation pipeline? Is it properly documented? Do you by chance have some tests for it? Then yes, it’s production ready.

If you just “write this quick script and run it in cron” then no. Because in 10 years people will pull their hair screaming “what the hell is hapenning?!”

Edit: or worse, they’ll scream it during the next incident that’ll happen at 2 AM on Sunday

There’s a new trend with immutable distros and they have some pros and cons. OP’s stance apparently is that they’re the future

https://itsfoss.com/immutable-distro/

I don’t know if sarcasm because there are actually maniacs like that in this world

Java … BAAAAD! Ahahahaha never gets old.

Also search your dictionary for ‘sarcasm’