I dislike now that everything seems to be hacking around frameworks and dependencies, people don't want to (or can't) write code anymore. This is of course a ra

I dislike now that everything seems to be hacking around frameworks and dependencies, people don't want to (or can't) write code anymore. This is of course a rant, but you get the point. The following in a contrived example, just mentally replace it with whatever horror you've seen. There's an awful lot of very nice good quality libraries, frameworks and 3rd party code that I'm very grateful for. But there's also a lot of hacky stuff around that people blindly import as dependencies. Then it becomes someones else headache (mine!) to deal with it. I get a task to add a feature which isn't supported by the library that the new dev imported into the system. Turns out this library was someone's introduction to the C language and they decided to publish it. It pipes unhygienic user input straight to system calls and has boundary issues. It's mostly one function with a lot of conditional checks on arguments. There are three copies of the source file, one for each supported platform. I'm left with a insane task, PTSD and a deadline on Friday. Do I just pretend I didn't see that and hack in another feature? No. Do I tell the boss the problem? Yes. Will it delay the release? No, there's a demo on Monday and we have to release on Friday. Why Friday, we shouldn't release on Fridays!