magic_lobster_party

I mostly use VS Code for notes and configuration files. Sometimes Python scripts. I agree with you, it requires a lot of setup. It has replaced Vim for me either way.

Most of my programming is done in IntelliJ, which works mostly out of the box. I’ve also used Visual Studio (not to be confused with VS Code).

I can’t imagine working without a proper IDE for any serious programming anymore. Working without IDE is like self imposed handicap.

That’s fair enough. The common misconception is that waterfall is great for space missions, when in reality NASA is doing agile.

I agree that not everybody is NASA, so what works for them doesn’t necessarily work for everyone.

NASA also successfully flew a helicopter on Mars first try.

It’s barely waterfall planning either. Often there’s no planning, at least no coordinated one.

Currently at my current workplace we lack coordinated planning between teams. It seems like everybody is working in their own directions and it can take months until we get feedback from other teams. Mostly a product management problem.

The author is also hyping up waterfall too much. Agile was created because waterfall has its shortcomings (the team realizes too late that what they’re building isn’t what the customer wants).

But I also think it also represents how poorly implemented these ideas are. People say they do agile/kanban/scrum, but in reality they do some freak version of these.

I think this is a bit disingenuous. There’s no customer interaction in these panels.

So waterfall would be:

Customer says they want to go to Mars.

You spend years building a rocket capable of going to Mars, draining all the company budget in the process.

Customer then clarifies they actually meant they wanted to go to Mars, Pennsylvania, USA - not the planet!