Before you upload it all to Github etc, for folks recommending that...
Keep in mind that there may be passwords / keys in the spaghetti etc...
iykyk...
Ask HN: Inherited the worst code and tech team I have ever seen. How to fix it?
701–704 of 704 posts
Re: Ask HN: Inherited the worst code and tech team I have ever seen. How to fix it?
#702Instead of a full rewrite, have you considered just continuing the shitfest?
Re: Ask HN: Inherited the worst code and tech team I have ever seen. How to fix it?
#703Earlier quoted context omitted.
"Have everything in writing, complete with date and signatures" It is possible that the executives won't take it well to all of the formality here (writing and signatures). How would you convince them that this is necessary?
"Have everything in writing" is a bad mindset and is not going to save you. Exeutives are looking at you as the expert to deliver a good outcome. Which means making good decisions, managing expectations and keeping everyone in the loop. Generally, if it gets to the point of having to dig up who signed off on what, you've already failed. Often you won't even get the chance to dig up those emails, because delivering a…
Sounds like you haven't worked in an environment where this happens. You get regarded as 'the expert to deliver a good outcome' sure. But you're ALSO expected to deliver an aggressive roadmap of a while load of other stuff that people already committed to. Someone's something's got to give
Re: Ask HN: Inherited the worst code and tech team I have ever seen. How to fix it?
#704As others have said, a full rewrite isn't needed. Go bit by bit.
Secondly the worst code you've ever seen is capable of pulling in 20 mil per year. Was the best? There is something to be said for success and it really makes me wonder about what 'good code' really is suppose to look like.
Granted a lot of what you're describing sounds terrifying.
If you want to deal with it first thing you should do is stand up a testing server and backup the code. Get some E2E tests in place to keep track of expected behavior. All of this can be done without removing a line of code and you can do it yourself while the team goes about their merry business. This is where I would start.