- cross-posted to:
- programming@programming.dev
- programming@lemmy.ml
- cross-posted to:
- programming@programming.dev
- programming@lemmy.ml
cross-posted from: https://lemmy.ml/post/47402101
You must log in or # to comment.
If be pretty pissed off if I got laid off from a company with twelve rounds of interviews and technical interviews to prove you can invert a b-tree in o(1), and then you finally start the job and it’s just the same lame legacy code and poorly thought-out technical decisions (let’s roll our own event bus!) as everywhere else for a product that your users hate because they’re forced to use it.
Honestly who’d want to copy their tech stack. Products like JIRA and confluence are notoriously bad and slow and hated by developers forced to use it. And all the good products are things they acquired over the years.
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 its a guide on what not to do?
As another former Atlassian engineer I’d say kinda yes and kinda no depending on which bits you’re looking at.
One important thing a person could learn is: use existing platforms. Do not build a proprietary version of something like kubernetes. The weird internal eventing systems and fake janky kubernetes junk gave me headaches.
One time I was at a place where we got a local ISP to build us a cloud virtualisation service at a discount (i.e. we were the guinea pig), but of course it was terrible and took ages to provision anything - so when someone in Platform stood up a Rancher cluster all of the devs immediately switched to using that.
Please god dont copy it, do better. The bar is so low
Skimmed parts of the video. First thought was “Wait, is he showing and discussing Atlassian internal code/architecture?”
If I were him, I would have read my employment contract more carefully to understand what belongs to Atlassian or him, what he can or can not keep, and can or can not disclose.
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.
Yeah, but the sense I got is he’s not talking about the open source or standard, he’s talking about Atlassian’s specific implementation, and other non-standards based work besides the OSB.
In normal employment contracts, that’s a no-no.
If you’re interested in the video, grab a copy, because I’d reckon Atlassian could have it pulled if they want. And sue the guy as well.
Medium post is strange reading.
