4 ms·
I’m sorry but it sounds like you’ve just been really lucky in where you’ve worked at. The majority of engineering organizations are quite terrible at recognizi
by pm90 5y ago
I’m sorry but it sounds like you’ve just been really lucky in where you’ve worked at.
The majority of engineering organizations are quite terrible at recognizing and promoting engineering talent. They’re fine with letting even good engineers leave as the cost of doing business. Looking at just the tenure and making an assumption about the individual sounds ridiculously backward and that’s pretty poor engineering leadership imo.
- colmvp 5y agoCouldn't agree more. At my previous job, I spent some of my evenings and weekends to build internal tools to help members of the organization be more efficient, saving certain people on the team dozens of hours of work per week. I largely did it because I wanted to learn libraries and tools we weren't using on a day-to-day basis. Instead of allocating more time for me to work on these projects or to work on improving our developer workflow, my reward was being assigned some of the most mind-numbing projects imaginable, tasks that quite frankly an entry-level developer fresh out of a bootcamp could accomplish. That wouldn't bug me if inefficiencies in the workflow wasn't such a bottleneck to the entire team. Disheartened, I (and many other senior devs) applied elsewhere. One of the strongest devs sent a scathing email to leadership before getting let go. I managed to land a position with a great company that lets me jam and nerd out on cutting edge technology.
- xwolfi 5y agoWhat a pleasure it must be working with someone who think important work is mind numbing and great company let him "jam" on "cutting edge" stuff (which I always translate as "dead in two years because too boring eventually for the jammers")