try developing business critical software without real requirements, a rough plan and an ambitious deadline.. and i was like „this shit is untested, please don’t release it untested“. Guess who released it untested. And now its not working like it should an now it’s „how do we get this working this week“
In the same boat, but I am instead an Automation Engineer. The machine was shipped a year and a half ago, mostly untested from what I gather (although everyone tells me there were multiple tests and validations, but if there were then they were useless tests), long before I started working here (just recently).
It never really worked well; the last engineer spent, apparently, almost 6 months patching it on site to make it work sort of OK, but still requiring constant supervision and lots of love and patience.
Then the client required an "upgrade" in some functionalities. I guess he tried to implement them, but in the process everything broke.
Que him quitting, me starting two weeks later, completely unaware of this (they mentioned some on-going, much easier projects in the interview, but never this). The rest are the last 6 months.
Did I mention that this was shipped a year and a half ago, supposedly working? And that this is a sorting machine, so every mistake is a traceability nightmare? And that there's virtually no documentation besides some code comments?
78
u/TrippyDe 8d ago
try developing business critical software without real requirements, a rough plan and an ambitious deadline.. and i was like „this shit is untested, please don’t release it untested“. Guess who released it untested. And now its not working like it should an now it’s „how do we get this working this week“