Experienced Devs

3978 readers

1 users here now

A community for discussion amongst professional software developers.

Posts should be relevant to those well into their careers.

For those looking to break into the industry, are hustling for their first job, or have just started their career and are looking for advice, check out:

Logo base by Delapouite under CC BY 3.0 with modifications to add a gradient

founded 1 year ago

MODERATORS

[email protected]

How screwed am I? (programming.dev)

submitted 1 year ago by [email protected] to c/[email protected]

16 comments fedilink hide all child comments

I started working for a big corporation about six months ago. Turns out a few months before I started there was a new CTO hired from a startup. This CTO has been on a hiring spree and basically hired all of the technical staff of the startup he came from (to the point that they're suing the company I work for).

All these people from the startup have their own office, away from all the corporate offices. And they're writing something (that they won't reveal) in what they refer to as their bunker. The best we can gather is that they're coming up with modern equivalents of all the backend services. This would mean that everything the devs do in the office I work in will be redundant.

I have the feeling that within a year or so (maybe less) there'll be mass layoffs of all the existing devs. Am I being paranoid?

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 3 points 1 year ago (3 children)

There there. Rewriting from scratch never go smooth. You at least have 3 years I'd say.

[–] [email protected] 2 points 1 year ago (1 children)

Yeah. Everything depends on the complexity of the product, but it's just as likely that it's the new CTO and his team that gets canned when they get bogged down in the details and the costs start racking up.

[–] [email protected] 1 points 1 year ago

Startups inside companies usually get shut down once the bill gets too high. I've experienced this first hand

[–] [email protected] 1 points 1 year ago (1 children)

This may be the case. They've gone from "this should be easy" to "oh, we never thought about that" pretty quickly.

[–] [email protected] 2 points 1 year ago

That screams inexperience in their end, to me. 20 years in the field, I learned to respect legacy. Can't move away from it without getting it under control first and then weeding out the smelly parts.

[–] [email protected] 1 points 1 year ago

The biggest problem with that approach is your team loses their roadmap, funding for new initiatives, and ambition while that's happening. Your sprint backlog has nothing but minor tech deficit tickets in it, and overall it becomes a chore to get anything done.