I was curious about the NDA bit as well, but I guess it's the sort of stuff you'd talk about in a tech interview as well. He's not revealing any deep secrets there. And while none of this stuff is necessarily rocket science, it is always interesting to see how big companies structure stuff that needs to run at scale. A lot of this stuff gets figured out through trial and error, and you can save some time by learning what worked for others.

Jira is just part of Atlassian's offerings. You've got the second-rate Wikipedia knock-off that is Confluence, the will-it-won't-it play video hosting of Loom, and BitBucket with its bizarrely awful API performance and rate limits for a Git host. Admittedly, I used to think that BB presented pull requests in a more reviewable way than eg. GitHub, but they're abandoned the things that made it distinctive in exchange for the follow-the-leader approach, so now it's just a less-good GH. And I don't say that lightly, it's a low bar to limbo under.

In fact, I kind of prefer managing tickets via post-its on a whiteboard then using Jira, as it actually allows you to see everything important at a glance, and micromanaging middle management don't get to set up bizarre and wonky workflows and rules, and a thousand bullshit fields to fill in on every ticket.

Alternatively, it's basically an advertisement for any company that wants to spin up this sort of infrastructure fast.

Atlassin is such a weird company to me. Used bitbucket a decade ago and everything just kept changing, things bought, what I used didn't feel like it got better. Is it a good place to work?

I would fire myself if I had to work there

I think that is the rub though. If your interview pipeline has system design questions all based around your arch that someone just released a youtube vid dissecting, you're going to struggle to get signal out those interviews. False positive hires are arguably worse than false negatives.

It... It can get worse?

we (team of 15) use salesforce and a promise to include issue numbers in our (svn) commit msgs all on one dev branch so when we cherry pick merge later to qa we can “safely” assume we got it all. 30% of the time it works 10% of the time.

i can’t convince these guys code is not “self documenting” let alone use git or a tool for proper bug reporting.

kinda depends how you set it up and run it, no?

i have some simple new projects that are clean and easy, and some 10+ year old monstrosities that are the spawn of satan.

need to use ublock to stop the insane 'pls bro buy our ai' pop-up though.

considering the human summaries here the slop isn't even close to correct, it based it all off the title

The world needs to see how it works to learn from our past errors and move forward as a society

It’s not revenge. It’s a CV

Trello was excellent before Atlassian started “improving” it. You’d always have to fight tooth-and-nail to keep your Trello board against managers who said it lacked features, even though precisely all the features a fucking kanban board needs is showing some tickets and columns.

Perhaps its a guide on what not to do?

I think everything he shows is open source. He mentions where repos can be found.

The post title, which I didn't change when crossposting, and the medium post are garbage. I'm pretty sure the medium post misquotes him as I read it again after watching the video. It's also weirdly written, like slop weird.

The video is interesting though.