3 ms·
I'd just like to make sure you've at least considered the hypothesis your words are strongly suggesting, namely that you specialise in producing tech debt and y
by Smaug123 6y ago
I'd just like to make sure you've at least considered the hypothesis your words are strongly suggesting, namely that you specialise in producing tech debt and you quit whenever that debt crosses some critical threshold. If it's not actually like that, then great!
- mkl95 6y agoIn my experience, startups produce enough tech debt very early in their existence, that if candidates knew about it, they would simply opt out of the hiring process and focus on something else. So what they do is lure engineers with greenfield projects or projects that are relatively healthy and have a good architecture, and are currently growing. Once these projects have been developed or expanded to a point where the engineers in charge (new hires among them) can also work on other stuff, the shift to "firefighting tasks" and legacy maintenance can be quite fast. To be fair, for a backend engineer it's not that brutal, our stuff is relatively homogenous (our legacy stuff also sucks, but not that much). When it comes to frontend development though, I have seen coworkers transition from clean Vue codebases to massive jQuery spaghetti balls in just a few days.