TE
科技回声
首页24小时热榜最新最佳问答展示工作
GitHubTwitter
首页

科技回声

基于 Next.js 构建的科技新闻平台,提供全球科技新闻和讨论内容。

GitHubTwitter

首页

首页最新最佳问答展示工作

资源链接

HackerNews API原版 HackerNewsNext.js

© 2025 科技回声. 版权所有。

Continuous migration to something new in the Infra space

2 点作者 golondon将近 4 年前
Hey folks,<p>I have been working as SWE &#x2F; SRE for last 5 years in FAANG and a big startup, prior to that I was working as normal SWE writing code for the customers.<p>One thing I noticed especially in the infra space is that work itself consistently consists of migrating from one system to another, or to new shiny service you wrote. Migrating all the existing internal teams, sometimes called customers, after some time this becomes quite boring, repetitive and exhaustive as well due to many hats you need to wear (you should keep your team up to date, keep users of the system up to date, keep management up to date, write code, document it, make sure rest of the who didn&#x27;t work on it understands it etc).<p>I wonder how is everyones experience with this? Do you do anything to exit from this endless loop? To me it feels like my only exit is returning back to normal SWE role where you can ship to prod many times a day and don&#x27;t care much about how many % of the users started using the feature. Someone does for sure, but it&#x27;s not your job to follow that, communicate on that.

1 comment

thorin1将近 4 年前
There are some companies where the only way to get promoted is to release a new better improved system. So there is an endless loop of rewrites and migrations all over the company.<p>If you don&#x27;t like it, you will probably have to join a place with a different culture.<p>Edit:<p>If this is the case only for SRE roles then you need to find out why are you rewriting and moving to new, shinier systems. Is there a big improvement? Or is it just for a sake of changing something?
评论 #27448127 未加载