Don’t you just love getting last-minute feedback from your boss right before your deadline? What about combing through a deluge of irrelevant-but-weighty comments from coworkers who aren’t even working on your project?
At Atlassian, we want to give our customers choice in how they deploy Atlassian products: in the cloud, managed by Atlassian, or on the infrastructure of your choice with Server or Data Center. Many of our on-premise customers begin their Atlassian journey with our server products, with the ability to download our software and install it on a single server that you control. This gets you up and running quickly.
Picture boring a new subway tunnel while the city above you goes on about its business, oblivious to the machinations under the surface. That’s pretty much the project we completed earlier this year. Only we were working in the cloud.
Just when you think you’ve got this whole “knowledge economy” thing figured out, here comes the “creative economy” – the world in which your ability to succeed and add value is limited only by your imagination. Of course, that creativity needs to be informed by a deep understanding of your customers.
Major incidents are inevitable, and fixing them is the top priority for any ops or DevOps team. But what happens after service is restored? Do teams take the time to fully understand what went wrong, then follow up to prevent it happening again?
In the ‘90s, we used to think of blogs as online diaries, filled with oversharing and bad graphic animations. But since then, they’ve grown into a full-blown industry. Influencers are now able to make whole careers out of successful blogs and it’s difficult to find a company that’s not using a blog as part of its marketing strategy.
