They don't even know the fundamentals
4 by kaeruct | 0 comments on Hacker News.
Monday, 1 November 2021
New top story on Hacker News: Is it unprofessional to leave a new job where everything is a mess?
Is it unprofessional to leave a new job where everything is a mess?
6 by itistricky | 13 comments on Hacker News.
Hi, after a long job hunting period I joined a small remote first company 5 months ago. Problems showed up immediately in the form of chaos and dysfunctions in the microservices cloud project I was hired in. Let's put it this way: say you get the seminal book on microservices and the seminal book on CICD. Now imagine reading along and doing almost everything from code up to project management the wrong way (essentially keeping on-prem 2000's philosophy and revamp it as microservices). On top of that add vendeta-developers in Asia (I'm in a small offshoot team in Europe) handing down half-baked frameworks (not-invented-here and reinventing the wheel are strong) with minimal documentation and a culture based on meetings instead of documenting things. Developer sandboxes that just don't work and unrealistic deadlines. In short a huge draining mess where I felt burnt out just a few months after I joined and where I honestly don't want to spent another minute. Almost every attempt of mine to change anything was met with either "yeah we know but we have to live with it for now" or a straight denial to hear me out - brushed aside as a newcomer (I'm senior and was hired as such). So, the question is, is it unprofessional to abandon ship just 6 months in or given the circumstances is exactly what I should do in order to protect my well being and my career prospects (the project is a slow motion train wreck IMO).
6 by itistricky | 13 comments on Hacker News.
Hi, after a long job hunting period I joined a small remote first company 5 months ago. Problems showed up immediately in the form of chaos and dysfunctions in the microservices cloud project I was hired in. Let's put it this way: say you get the seminal book on microservices and the seminal book on CICD. Now imagine reading along and doing almost everything from code up to project management the wrong way (essentially keeping on-prem 2000's philosophy and revamp it as microservices). On top of that add vendeta-developers in Asia (I'm in a small offshoot team in Europe) handing down half-baked frameworks (not-invented-here and reinventing the wheel are strong) with minimal documentation and a culture based on meetings instead of documenting things. Developer sandboxes that just don't work and unrealistic deadlines. In short a huge draining mess where I felt burnt out just a few months after I joined and where I honestly don't want to spent another minute. Almost every attempt of mine to change anything was met with either "yeah we know but we have to live with it for now" or a straight denial to hear me out - brushed aside as a newcomer (I'm senior and was hired as such). So, the question is, is it unprofessional to abandon ship just 6 months in or given the circumstances is exactly what I should do in order to protect my well being and my career prospects (the project is a slow motion train wreck IMO).
This Is Where the First Climate Wars Will Break Out
from Yahoo News - Latest News & Headlines https://ift.tt/3btalzw
Halloween contest for best dressed dog in Brooklyn
from Yahoo News - Latest News & Headlines https://ift.tt/3my36g5
Subscribe to:
Posts (Atom)