Thread

1. dimatura · 1790892256 · focus · HN ↗

   Only tangentially related but many many years ago, I spent a good chunk of a summer internship at synopsys fixing gcc warnings in one of their products. The codebase was huge, with many parts of it more than a decade old at that point. I learned a lot about obscure corners of C. These days a frontier model could do that job in a few days (or maybe just one day if the build and testing process has been sped up - it took several hours on a dedicated cluster back then).

   1. phlipski · 1790906540 · focus · HN ↗

      This is the dirty secret of EDA companies. Their software sucks. It's a function of volume. They don't have the number of customers like Microsoft/Adobe/<insert consumer SW co> does and so the level of testing and bug fixing is just abysmal. It was a rude awakening for me as a young engineer when I would click on tool sub-menu buttons of various EDA software programs find out that they did nothing. I would ask the sales person or FAE why that was and their answer was, "That's a planned feature - we put the button in their to gauge customer interest."

Unofficial Hacker News client; not affiliated with Y Combinator.