4

>start new job, not very professionally experienced dev
>spend couple of months working on a feature that is supposed to be an MVP kind of thing, be rushed to finish and told to cut corners because it's "just an MVP", still lose sleep and have relationship suffer (and ultimately ruined) as I try to not lose deadlines created by the boss with questions like "you can have this done by <very soon>, right?"
>frontend created by fellow developer is a garbled mess of repeated code and questionably implemented subpages, frontend dev apparently copies CSS from Figma and pastes it into new non-reusable React components as envisioned by designer, I am tasked with making sense of the mess and adding in API consumption, when questioning boss what to do with the mess I am often told to discard stuff that the frontend dev has made and just reuse his styling; all of this on top of implementing the backend feature that a previous developer wasn't able to do
>specs change along the way, I had been using a library as a helper in some part of the original feature, now the boss sees that and (without further testing the library) promises CEO that we'll add that as a separate subfeature, but the performance of the library is garbage for larger inputs and causes problems, is basically shit that might not have been shit if we had implemented it ourselves, however at this point CEO has promised new feature to some customers, all the actual sense of responsibility falls upon my hands
>marketing folk see halfway done application and ask for more changes
>everything is rushed to launch, plenty of things aren't implemented or are done halfway
>while I'm waiting for boss to deploy, I'm called up to company office by CEO, and get new task that is pretty cool and will actually involve assessing various algorithms and experiment with them, rather than just stitching API calls and endpoints together, it involves delving into a whole new field of CS that I never had the opportunity to delve into before
>start working on cool task, doing research, making good progress
>boss finally deploys feature I had been originally implementing
>cut corners of original boring insane feature start showing up, now I have to start fixing them instead of working on cool task, however the cool task also has a deadline which is likely expected to be met

I'm not sure if I'm having it bad or not, is this what a whole career in software development will look like?

Comments
  • 1
    You chose to be a web dev. So, probably yes.
  • 2
    @Lensflare I actually have systems programming skills but there's no market for them in my country. Had to learn webdev to get a job.
  • 2
    That’s very close to what I see over most places, specialty if there’s a non-dev managing the software department
  • 1
    I've been there too... not just in 1 company... everyone is rushing to deploy their "great" ideas to the market before someone else does... it's a mess, but not everywhere =]
  • 0
    @eo2875 in my case there's a dev managing software development, but... he's a co-founder of the company, so I guess he has the same incentives the CEO would have. But the CEO (also a co-founder) very likely never wrote software ever.
  • 1
    It depends on your city/Country but I would be gone very quickly in an environment like this. Not worth my time nor any need to subject myself to such torture.
Add Comment