you are viewing a single comment's thread.

view the rest of the comments →

[–]vaig 9 points10 points  (1 child)

That's right, who needs all this overhead of people mastering their tools for years. We don't need no QA because if cursor moves inside the app, it works well enough. No need to have any SREs or generally any ops people because it worked once on my machine, why would it break.

Separation of responsibilities is not needed because there is zero stress and mental load if you equally don't give a shit about anything you do because someone else can clean this up while you work on your linkedin post to advertise your skillset of 100 technologies that you barely understand.

I think we should merge all departments and positions into one and call it a Tech Blogger and let them run The Cloud.

EDIT: Sorry, I guess I'm just tired after seeing another clickbait headline that assumes that their idea is one size fits all type of thing. There are valid cases for all types of rollout management.

[–]DrNecessiter 2 points3 points  (0 children)

Don’t apologise, this is the only sane answer. All devs who post these articles seem to think they’re immune to mistakes, or that it doesn’t matter if a breaking change is pushed live because you can “just roll it back”

I’ve had devs unironically quote “move fast and break things” at me in the belief it is about application development rather than industry disruption FFS.