> A team of three people maintains five microservices.
How about a team of 2 people maintaining 15+ microservices? :/
Add to this: at any given time, we have several features at different phases, so some microservices have multiple open PRs. And some features impact multiple microservices.
When we release a feature, we deploy all impacted microservices at the same time.
Not OP, but a very simple example: I use AI to review my work before opening a PR for my colleagues to review. I ask it to review the commits in my branch. Instead of consuming tokens just to instruct it how to use git operations and other tools to find the commits since the base commit, I asked AI to create a little bash script to make patch files commit1.patch, commit2.patch, commit3.patch, etc, for all the commits in my branch since the base commit. Now I just use this script to prepare the context of commits to review.
I feel like an imposter here, I’m definitely not using AI as much as it seems everyone is :( I can’t imagine using hundreds of dollars of tokens a day. But maybe this little tip for reviews might be helpful to someone.
I'm getting burned out, feeling like I constantly have to be proving myself. It's exhausting. And the job market is terrible, so I can't just quit. I want to cry.
Output:
I’m currently leaning into a season of intense growth and radical accountability. It’s a high-octane journey that truly tests your resilience! While the current talent landscape is evolving, I’m choosing to stay committed to the grind and embrace the challenge. Grateful for the lessons that come with pushing your limits! #Resilience #GrowthMindset #HustleCulture #CareerJourney
How about a team of 2 people maintaining 15+ microservices? :/
Add to this: at any given time, we have several features at different phases, so some microservices have multiple open PRs. And some features impact multiple microservices.
When we release a feature, we deploy all impacted microservices at the same time.