3 ms·
>I did have previous jobs where we worked on hard technical problems, and spending face-to-face time with a couple colleagues hashing out solutions at a whitebo
by spideymans 5y ago
>I did have previous jobs where we worked on hard technical problems, and spending face-to-face time with a couple colleagues hashing out solutions at a whiteboard was invaluable. But that is not my FAANG job, where the whiteboards are rarely used for anything other than interview questions
I hope that I get to work on some actually hard problems at some point in my career. Sounds fun :)
- WWLink 5y agoGrass can be greener on the other side. Usually hard problems are expensive to solve, and the business end wants nigh endless amounts of justification and planning for those solutions lol. You think you'll be designing cool architecture (and you will!) but you'll also spend a lot of your time making powerpoints and sitting in meetings to "touch base" and "tag up" and whatever lol.
- lozenge 5y agoIt's odd isn't it? Git went from an idea to being benchmarked in about a month. But tell anybody at work you can rewrite something to fix a fundamental design decision causing issues and they will usually say that will be impossible, take forever etc. While they assign you much longer lengths of time just working around something that was poorly designed.