Work in progress: 181,232 of 181,233 sites checked so far, more every week · updated 2 Nov 2026Missing a blog? Tell us

Top all-time · #4656

I

Inside Atlassian

Company blog · blog.developer.atlassian.comprogrammingweb

Inside Atlassian is the company blog at blog.developer.atlassian.com, writing about programming and web. Since 2019, 17 different Hacker News readers have linked it 18 times, most often “Why Atlassian uses an internal PaaS to regulate AWS access”. It is still writing: the last post was on 2026-11-02, and you can follow it by feed.

Visit the blog
18mentions?
17HN people?
2019–2024first – last linked?
Links on Hacker News per year · peak 10 in 2019

Too few sampled comments (4) to say how often HN recommends it.?

Why HN links it

HN readers link Atlassian's developer blog for posts on Git and JavaScript, such as the force-with-lease post. Comments mostly cite or link posts as sources without judging them.

Summarised by Claude from a sample of 4 HN comments that link here. Each comment is marked recommending, critical or neutral (citing without judging); how this works.

Research, expert perspectives, and product announcements from Atlassian on how teams can work smarter with AI. Subscribe for monthly insights on the future of teamwork.

Most-linked posts?

  1. Why Atlassian uses an internal PaaS to regulate AWS access
    2 people · 2 mentions · first linked 2019-08-16
  2. Retiring IE11 Support for Atlassian Cloud, Server, and Data Center Products
    2 people · 2 mentions · first linked 2019-09-24
  3. Protect Our Git Repos, Stop Foxtrots Now (2016)
    2 people · 2 mentions · first linked 2022-06-25
  4. Avoid Git merge in a topic branch if you want to keep your history linear
    2 people · 2 mentions · first linked 2019-06-03

What Hacker News says?

  1. I'm trying to respond in good faith, even though I feel you unnecessarily resorted to trying to condescend me. You wrote: > there is a difference between two APIs > that both still work and having one > stable API. As I explained, "this is the direct effect of high levels of backwards compatability. You can't change APIs; you have to create new APIs and then deprecate previous APIs." I thought my point was obvious,…

    Comment linking /retiring-ie11-support-for-atlassian-cloud-server-and-data-center-products/

    on “Modern Javascript: Everything you missed over the last 10 years (2020)”
  2. Submitted Why Atlassian uses an internal PaaS to regulate AWS access as a story · 23 points

    HN discussion
  3. I had to look it up as well. https://blog.developer.atlassian.com/stop-foxtrots-now/

    Comment linking /stop-foxtrots-now/

    on “Oh Shit, Git”
  4. Submitted End of Jira Server support in 2024 as a story · 16 points

    HN discussion
  5. I really do not like `push -f` because in the past git default configuration was to push all branches; things have improved now that the default is to push to the current branch. Recently got turned onto `git push --force-with-lease` which is great. http://blog.developer.atlassian.com/force-with-lease/

    Comment linking /force-with-lease/

    on “More Productive Git”
  6. Submitted Protect Our Git Repos, Stop Foxtrots Now (2016) as a story · 8 points

    HN discussion
  7. Thanks for the clarification on the final NRT behaviour. Just to say, my point about "didn't align with good taste" was itself lacking taste. I'm sure each of those features I critiqued made sense as they were proposed at the time and were just considering different use cases and tradeoffs. Did it drop the idea of assembly-wide opt-ins to stricter behaviour, meaning all NRTs can be reasoned about in the same way wit…

    Comment linking /optional-broken/

    on “The Road to Valhalla”
  8. Submitted Atlassian stopped XML vulnerabilities from landing in production as a story · 6 points

    HN discussion
  9. Submitted Retiring IE11 Support for Atlassian Cloud, Server, and Data Center Products as a story · 3 points

    HN discussion
  10. Submitted We Built the Jenkins to Jira Cloud Integration as a story · 2 points

    HN discussion
  11. Submitted Avoid Git merge in a topic branch if you want to keep your history linear as a story · 2 points

    HN discussion
  12. Submitted Git wisdom – stop “Foxtrot” merge commits as a story · 2 points

    HN discussion
  13. Submitted Configuration management for a consistent and resilient dev environment as a story · 1 points

    HN discussion
  14. Submitted Preventing cross-site scripting (XSS) attacks as a story · 1 points

    HN discussion
  15. Submitted Atlassian Ventures Celebrates 1 Year of Investment in the Cloud Ecosystem as a story · 1 points

    HN discussion
  16. Submitted Why Atlassian uses an internal PaaS to regulate AWS access (2019) as a story · 1 points

    HN discussion
  17. Submitted What Bitbucket learned from migrating its unit testing tool as a story · 1 points

    HN discussion
  18. Submitted Java debugging at scale: when rare events become commonplace as a story · 1 points

    HN discussion

Search all of HN for blog.developer.atlassian.com

Linked by the same people?