It's really weird, though, that nobody really created a language/tool to bridge these two world. It's always just generating one representation from the other, mostly in a bad way.
I'd argue, that for many problems, a graphical view of the system can help reasoning. But there simply is nothing in that regard.
One of our customers does that. It happened multiple times already that one dev fixed an issue in production, and the next regular deployment overwrote everything.
But fortunately, it's just critical infrastructure and nothing important.
The older generations kept leaking contaminated water (reactor coolant), many harbors simply refused entry because they didn't know the risks involved, and I'm pretty sure the decommissioning isn't clear either. The way current laws are set up, it's quite possible that these things go through a few hands and end up on a beach in some underdeveloped country and get dismantled like any other ship under horrible working conditions - but now with the added benefit of nuclear contamination.
No. Not at all. It's about gradient descent, an optimization technique.
You could use it to auto reply and delete said mails.
No, I'd argue you simply didn't want to invest in the other tools.
Think about it, you probably spent hours on customizing and automating vim, and then say you're faster in that. Well, that's called a habit.
IDE are objectively more powerful and since you can actually see options and navigate quickly, you don't need to memorize every obscure feature.
All the terminal editor enthusiasts are actively holding us back, because they insist everything outside vim is garbage for enterprise and kiddies.
If your tool of choice is actively hostile to new users for no reason other than "that's how it's always been, and thus it's better", well then you're digging a moat to automate your gatekeeping.
I understand it very well. And that's exactly why I'm writing this.
Ok, I can see you have no idea what you're talking about.
Then say, grandmaster delusion, what purpose does vim serve, where it is actually the best tool? Writing code? Hardly, it's way too limited and requires a ton of upfront investment and headspace. Writing config files? Hardly, because if you write these by hand, you're living in the 90s, that's what Ansible, Terraform etc are for.
You just don't want to admit, that vim is nothing more than a habit. Muscle memory.
You're using the terminal, because you're used to it. It is not the better tool, it's simply what you happen to know already.
People who argue with productivity because of some key bindings live in the world of the 80s. You don't just sit there and type code 12h a day, that's not how modern software development works.
And all those blockheads down voting me are caught up in their weird superiority complex. They are the powerful superhackers, and don't understand that we are just highly qualified plumbers.
Most names are essentially just landmarks of some sort.
Hamburg is derived from Hammer Burg, simply meaning hammer castle.
Part of Hamburg is Altona, which is lower German for all too near, because it's really close to Hamburg.
East of Hamburg is Lübeck, which is means "settlement of the lub", whoever the lub were.
Even farther east is Warnemünde, which is located at the mouth (Mund) of the river Warnow.
Said river is getting pretty wide a bit upstream, which gave the city of Rostock its name ("where the river gets wider").
East of that: Stralsund. It's the sound (the water kind) of Strela.
And so on and so on.
To be fair, a lot of roles simply disappeared over the years.
Developers today are much more productive than 30 years ago, mostly because someone automated the boring parts away.
A modern developer can spin up a simple crud app including infrastructure in a day or so. That's much much more productive than 1995. We just cram a lot more of the world into software, so we need 20x the amount of developers we needed back then.