Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
-
@AlmondSauce boss said I had to since the hardware is old but the current software was comparably new and according to the client "this has never happened before!!!!"
-
@Synthron Ah fair enough. Still though, hardware issues can lay undetected for decades before coming to light - decoupling caps can often be omitted entirely for instance, and no-one will notice for years until a slight power spike causes random brownouts 😁
-
@AlmondSauce i know, but if boss says I should work on it, then I'll work on it ...
-
@Synthron aha! There you could have caught him.
Software always behaves the same, right? New behavior would then suggest hardware problems?
Update: nevermind. Software was updated too? In any case. I feel for you, I write software for machines too. Fixing hardware issues with software 😆
when your code is a mess but everything work out in the end
When you keep getting +1s on a rant you posted a month ago.
Go big or go home.
Ok, a customer came to us saying he had a product that is just randomly rebooting. It sure must be a software issue.
I got the task and worked my way through ~10k lines of assembly code (8085 processor on board) Weeks go by, i tested every single god damn funktion they had, analyzed every vector they put in, finding NOTHING...
Meanwhile the hardware department analyzed and tested some possible culprits on the product for me. I had NO idea what the problem could be...
Then hardware department said: oh, they forgot a resistor on the FUCKIN RESET PIN OF THE PROCESSOR!!!!!
fml...
rant
debug