Hands down, I think “My vacation starts tomorrow.” is a valid point when considering impactful decisions.
That’s true, never make impactful decisions in a rush. But I feel like the last panel only works in the current context of escalating code changes
Valid, but if it needs to be decided, then there should be something concrete scheduled to do that followup when people are back in.
Why is writing code by hand out of the question?
Because clown
I’m still curious what the reason is, even if its clown logic.
No
Shouldn’t this be the other way round?
I think this is coming from a “plugins enshittify projects” mentality where the assumptions are:
- code bases should be as succinct and stable as possible.
- plugins add large amounts of unused code and obfuscate many granular aspects of program execution, increasing debug and research time.
Seems that the author views that the above devs chose to use plugins instead of writing their own code and shot themselves in the foot by doing so. The final portion seems to suggest that the person pushing all these changes then bobs out before any of the problems caused by these changes actually get solved.
Dump it
Wordpress flashbacks
