u/greencursordev

This is one of my pet peeves: the inability to actually deprecate the "old" version of something is always so hard. There are always users who don't want to switch. Or that obscure feature you don't want to support in v2 that keeps users from switching. Or my favorite: a general suspicious attitude against all new software.

I'm currently writing internal software for a high tech Corp. It's an even worse situation than writing paid software for actual customers.

Did you manage to deprecate it? Even to delete the code entirely?

The browser is quite powerful with the tags and it's filtering capabilities. But many plugins don't integrate with that: vital has its own system. And even the native flex has a completely separate system. How do people deal with this: How do they reuse instruments if there's no universal system to even manage favorites? Does everyone just go on a searching trip all the time? Or does everyone just create a new sound from scratch in a synth? I'm so confused.

And how about the other "big" synths like serum and pigments, do they integrate with the FL system or do they come with their own? Do other daws have the same problem?

I find this pretty frustrating.

I'm a dev in a big high-tech company. We have lots of teams, lots of processes and therefore lots of software. We try to control this with polaron and leanix. But it's just performative. These tools don't really do anything? And besides being laughable bad, I think they also cost money?

What's the point of someone who has never worked in software and never worked on the processes we use to write down "requirements"? They end up on our Devs table, we try to decipher what that's supposed to even mean. Eventually we usually just end up talking to the people who'll use our software. And almost always these requirements are wrong and we just code what they tell us. And after working completely outside of the entire re cycle, they pad themselves on the back. It seems like a giant scam to employ unemployable people as "requirements engineers".

Same for leanix. It's some weird website that has a few redundant and wrong Infos about our programs. So then what? What's the goal? Colleagues talk about wanting to get an overview of our software landscape and prevent double development. But we Devs know that full well. We develop these redundant programs with full intention: because that's what gets you promoted. I can tell you *exactly" what programs shouldn't exist, and all other Dev teams can as well.

This might sound frustrated but I'm really struggling to see the point of all this. Feels like a few boomers discovered computers and made up fancy words and titles to make themselves seem valuable to the dinosaurs in the lead. All the struggling Devs pivot to rEqUiReMeNt EnGiNeeRiNg. None of this will ever impact a single line of code.