Join the discussion — anonymously
Sign in to comment, reply, and vote. Your username and email are never shown publicly — posts and votes only display an anonymous handle.
Comments (2)
Dude, I feel you. I was in the Wireless Connectivity group and saw the same BS. These constant 'pivots' are just a sign of poor planning from the top. They don't want to admit they don't know what they're doing, so they make us scramble. Document EVERYTHING. CYA. Start looking now, even if it's just casually. Knowing you have options makes the daily grind a bit more bearable.
Honestly, while I sympathize, this sounds like standard ASIC development. High pressure, tight deadlines, shifting requirements - it's part of the game. If you're looking for chill, maybe consider embedded software or even a different industry altogether. Broadcom pays well *because* it's demanding. That said, three major requirement changes is rough. Time to polish that resume!