How do you even fix it, when the design is broken. Sure you can make an alternative function, without all the warts, but how do you convince the “seniors” to not use the old functions, because it is in fact problematic for various reasons.
We have a separate C-library that returns all strings by ringbuffer. Why is that a problem? Call into the ringbuffer enough times, and it will wrap around, overwriting earlier strings. This, and other bad code practices such as broken multi-threaded code (not threadsafe), and more.
ISometimesAdmin@the.coolest.zone 8 months ago
Unfortunately if you let Junior play in legacy code once, it'll learn some nasty habits and make more of it from scratch, usually when you're trying to sleep.
Hazzia@discuss.tchncs.de 8 months ago
It’s true, spaghettification sauce stains clothes. Best keep Jr out of it entirely.
MagicShel@programming.dev 8 months ago
I don’t want that shit all over me though. That’s why I hired junior!
MonkderZweite@feddit.ch 8 months ago
That’s what the line represents. So they can pull you if do something nasty.