4 ms·
> This feels like a rant that comes from someone who doesn't have a lot of experience deploying and maintaining complex systems over long periods of time. Agre
by mavelikara 5y ago
> This feels like a rant that comes from someone who doesn't have a lot of experience deploying and maintaining complex systems over long periods of time.
Agree. Also:
> Finally, after many rounds of arguing about why this needs to be done in the first place (ahem: you told us to migrate to your platform, and it literally does not work for our app)
If migrating the app to the new platform is a priority, why not escalate up the startup's leadership chain to get it prioritized higher in the infrastructure team's roadmap? Looks like the startup was poorly run, with no clear escalation paths, and employees unaware that such mechanisms exist in companies (and find it odd when they notice another engineer do it).
- nightpool 5y agoHonestly, I kind of regret the sentence that you quoted. Whether the OP is correct about the complexity of the change or whether the deploy team is right to be protective over it is is really missing the point—the point is that the OP needs to have more humility and understanding for the perspective of the other team when navigating these processes. EDIT: I felt bad enough that I went and edited that sentence, in case anyone reading this later is confused.
- CRConrad 5y ago> Looks like the startup was poorly run, with no clear escalation paths, and employees unaware that such mechanisms exist in companies (and find it odd when they notice another engineer do it). Might be appropriate for a startup?