Sometimes navigating real world situations is more important than being technologically correct. My honest opinion.

Love this real world guidance ♥️

Thanks my brother.

You're wise o. I wish many engineers would do what you do and not just leave at the slightest inconvenience/disagreement. Also, there are some issues that would require you to leave, but this is not one of them.

Thanks 🙏🏾

Facts. Engineering perfection doesn’t mean much when you’re failing the actual humans you’re trying to build for. Seen this play out way too much.

real world: why am i arguing with TL on something that has already been determined by the architecture. they might be wrong but one day, they’ll get to it.

I bet they still version, they just don't separate it. Changing an endpoint without deleting the old one is still versioning and he just needs to have a better understanding that they can still have the latest code with versioning

apt

Spot on. I mean, in your free time, you could start versioning the APIs on a new branch and do a demo when you're done highlighting the benefits of versioning (which they know). The team lead probably doesn't want anything to break, hence the push back.

Nice thoughts bro. It's not about been right or wrong. Client management is a rare skill on its own, especially in this era of AI

🔥🔥🔥🔥

sometimes peace is worth more than being right i'd rather keep the team calm than win an argument

Fact!

1/2 First of all because you are a lead doesn't mean you know everything. Then as a teammate always communicate your own thoughts and solutions even if it is not accepted by the lead. This will show that you actually have deep knowledge of what ever your team is building and

the subtle detail that nobody noticed changes everything

If you had to pause an agent bc of real life vibes, which ones would make it say nah fam?

Trying to prove something will always backfire Just find a way to make the discussion smooth with the team lead

True

It's really all about the money, which decision pays the most?

In theory, maybe. In production, that's a risky approach.

2/2 Will put your team lead of researching part to find out if your contributions is the way to go eventually