3 ms·
I do embedded work. I experienced this while working for a multinational. - A long build process and linker step that takes ages. 1-2 minutes for a small chan
by wojciii 5y ago
I do embedded work.
I experienced this while working for a multinational.
- A long build process and linker step that takes ages. 1-2 minutes for a small change.
- Trying the change on a real device took perhaps 5 minutes.
- A review process that can take days or even weeks sometimes.
- There was a process that merged my change set which often failed and needs to be rerun several times - often 1-2 days were spent on trying to commit something where everyone was doing the same.
- There are no unit test because some manger decided that they provide no business value.
- There were no simulation tools for software be because some manger decided that they provide no business value.
- Testing would be done overnight.
With the right tools (unittest and pc simulation) I would be effective and could test my changes prior to testing on a real device. This was for me the bottleneck and not how long it took to build the project. I was testing code that was just C on a complex embedded device that I could have tested/debugged easily on a PC in 1/10 of the time.
This was really a management problem where the management didn't understand what to do to make their employees efficient with the right tools.
- dezgeg 5y agoAt least you are lucky enough to be able try changes yourself. I am in the "fun" situation where team of 50+ SW engineers don't have single piece of test equipment needed for operating the hardware, and everything has to be manually tested by some QA engineer, taking 1-2 hours minimum...
- wojciii 5y agoIt can always be worse. :) I feel your pain. This was from an old job. I work a different job now with different challenges.
- jeffrallen 5y agoHello, fellow ex-Cisco employee.