I can’t speak for your managers, but my past managers didn’t need Agile to f things up. They can do that with anything!

You know, I wish it wasn’t. Much of Amazon was on a version of Perl for years (and may still be) for almost all of their front end hosting. Facebook has transformed PHP into Hack (which is better for types, though technically not strongly typed), strongly suggesting they were running PHP until 2014. Let’s not forget what WordPress is still in PHP too.

https://quirksmode.org/css/ has entered the chat.

Ouch! Red flag. Sucks to get rejected, but maybe you dodged a bullet.

The mark of a true master.

Python should not be used for production environments, or anything facing the user directly. You are only inviting pain and suffering.

(That’s the joke!)

Someone hasn’t read https://en.m.wikipedia.org/wiki/No_Silver_Bullet yet.

If abstraction was going to kill it, it would have died a thousand deaths already.

The nuances of Go syntax requirements are stupid at times, but I am shocked at how much it helps readability.

How much of that python is written in a shared codebase with multiple active contributors? When was the last time you refactored a module?

Tabs and spaces are invisible. Semicolons are not.

Load bearing whitespace. Damn, I love that phrase.

Also, if you have to have agreement on the tabs or spaces argument in your codebase in order to get it to compile, you have already lost.

Linux can be just as much of a slow-ass OS. The real issue is all of the crap everyone wants to do in the browser now.

One Note. I have yet to see anything from anyone come close. Works with all of my devices, allows me to use a stylus for designs on an infinite graph paper canvas, and damned good at note taking.

Oh boy, here we go (inhales):

Agile isn’t that bad. People just believe they are more productive if they are “heads down” and not held accountable for what they write/do.

Functional programming isn’t that great and doesn’t solve all of the world’s problems; it just pushes the issues with state to other parts of your design, and doesn’t scale well in deeply nested solutions.

IDEs with proper code support (i.e. automatic structure analysis, autocomplete, etc.) are one of the best ways to deal with a large codebase that needs refactoring. Doing widescale refactors without one is asking for trouble. If you believe you don’t need it, either your codebase is just that small (which is fine) or playing with fire.

Much of the advice out there on architecture and tooling isn’t properly contextualized on the codebase, market, and team situation. If you believe you have the One True Architecture Solution, you are naive. (Ex. Microservices, large complex code pipelines, monorepos, etc.) Be especially wary of anything from FAANG engineering blogs unless you are also in another letter of FAANG.

There. Got it out of my system. Have fun dissecting it.