Outdated Raids

[SuperZay]

Both of you are using the player defined version of the word "content", the dungeons, raids, trials etc. that you run.
The person you're quoting is talking about the developer version of it, which is anything that requires development time. And yes, digging through tons of code (some of likely from 1.0 still) does take development time.

You take a ready code from Trials Roulette and copy it. You replace all trials instance IDs with 6 raids instance IDs. Rename second copy to Raid Roulette. Attach that code as another entry in Duty Roulette menu.
Done.

[BillyKaplan]

You take a ready code from Trials Roulette and copy it. You replace all trials instance IDs with 6 raids instance IDs. Rename second copy to Raid Roulette. Attach that code as another entry in Duty Roulette menu.
Done.

1. "You take a ready code from Trials Roulette and copy it" and hopefully get fired for your horrible practices.
2. That depends heavily on how it was implemented. What you described refers to an ideal implementation of the system (making the relevant code generic, and easily accessible, for starters) which is not guaranteed.
3. That would still require development time and then, more importantly, testing.

Yeah it's not new content that needs to be checked from scratch but it still takes time and we have no idea where it stands in their priority list.

[SuperZay]

1. "You take a ready code from Trials Roulette and copy it" and hopefully get fired for your horrible practices.
2. That depends heavily on how it was implemented. What you described refers to an ideal implementation of the system (making the relevant code generic, and easily accessible, for starters) which is not guaranteed.
3. That would still require development time and then, more importantly, testing.

Yeah it's not new content that needs to be checked from scratch but it still takes time and we have no idea where it stands in their priority list.

Get fired for what? If you are not familiar with programming, you don't need to rewrite all the code from zero if you want to add identical, copypasted feature to something, you copy a part of core code and alter it as needed. Rather, you'll be fired for rewriting all the code because you'll not meet deadlines.
For example, Mentor Roulette already has all 6 raids in it. For Raids roulette you take that ready, tested, working code and delete all entries which are not these 6 raids, adjusting it as needed so everyone can participate and not just mentors. Raid Roulette code ready.

[BillyKaplan]

you don't need to rewrite all the code from zero if you want to add identical, copypasted feature to something, you copy a part of core code and alter it as needed. Rather, you'll be fired for rewriting all the code because you'll not meet deadlines.

Twelve preserve, no! I literally quit a place because the project I was assigned had a bug that existed in half a dozen locations that were effectively the same bits of code which I had to slave to find. How's that for time consuming? Copy-pasting code is not what they mean when they say code should be reusable.

For example, Mentor Roulette already has all 6 raids in it. For Raids roulette you take that ready, tested, working code and delete all entries which are not these 6 raids. Raid Roulette code ready.

Not precisely. Mentor roulette has different ilvl and level restrictions. It's a solo duty. Already if you copy-paste the code as you said, you'd have to make modification.
Hopefully the code used for the roulettes is sitting in a nice little function that receives all these things as parameters (# of people who can queue, party make-up, ilvl, duties in it, etc) and is easily accessible from all places relevant to this discussion. But that doesn't mean it won't have to be tested still.

[aesteval]

You take a ready code from Trials Roulette and copy it. You replace all trials instance IDs with 6 raids instance IDs. Rename second copy to Raid Roulette. Attach that code as another entry in Duty Roulette menu.
Done.

And accidentally queue half the party into Verminion because you didn't bother taking the time to understand what the code does or test it.