Skip to content

Comment on Encountering some turbulence on Bitbucket’s journey to a new platform

Comments

our engineers implemented a solution where we would proactively
our engineering teams prioritized their efforts to ensure that Bitbucket

It's not a coincidence that company that refers to "our engineers" rather than "we" is having basic engineering problems.

As we planned for this migration
Our focus was primarily on read operations
In contrast, we accepted that there would be increased latency for writes

It didn't sound like they were throwing the engineers under the bus at all to me. They seemed to be highlighting that engineering executed well on the items management wanted them to focus on.

I worked for Atlassian for 3 years. They are a VERY engineering-focused organisation. Both of the CEOs have engineering backgrounds and the whole company is organised around engineering teams. I think you're looking too deeply into some off-handed phrasing there.

Interesting that a company that has two technical CEOs has apparently such problems in their engineering teams (I‘m looking at you, Jira performance).

I don't view this a bad thing; just a sign of recognition for the teams that did the job. Using "we" may come off as if the management is taking credit for the job. Or at least, that's how I see it.

I wrote this post and that's definitely how I meant it! Our engineers are awesome. I think the word "we" appeared more in earlier drafts and I changed it in a few places because frankly I don't deserve any credit for the majority of incredible work they did.

AboutSource Built by g1lg1l

Hackerly is an independent reader for Hacker News, built on the public HN API. Not affiliated with Y Combinator.