The remote work revolution proved to be a triumph. So much so, that when bosses emailed staff with “get back to the office” after Covid restrictions ended, swathes of home workers decided to quit instead. It’s part of what drove the so-called Great Resignation. Remote working has a ton of benefits, but getting it right takes experience and discipline – not to mention tools.
Migrating to the Cloud has been proven to improve productivity, and has enabled even the smallest business to become truly global. And yet, there are still organisations that haven’t gone all-in, relying on legacy hardware and software to get critical work done. The problem is – it won’t be long until in-house server rooms and legacy software are all but dead. Hardware becomes obsolete fast, and maintaining even the simplest server setup is expensive.
Finding the right candidate or contractor for an Atlassian project is a lot harder than just matching a set of skills to a job description. It requires analysing the job description, knowing the hard skills and the soft skills of the job – and picking up on the subtle nuances of what our customer is trying to tell us they really need. ClearHub sources Atlassian contractors for some of the world’s largest organisations, as well as SMBs and startups.
Eficode has acquired Clearvision, a solutions provider for Atlassian, Git, and open-source tooling. The acquisition fortifies Eficode’s presence in the United Kingdom and establishes Eficode in the United States. With Clearvision, Eficode will accelerate the adoption of its Eficode ROOT managed DevOps platform in the UK and the USA and will introduce its Agile and DevOps services to Clearvision’s customers.
Recruitment, especially in tech, is seriously hard work. Even just for one new team member. Listing a job, sifting through applicants, interviewing them, re-interviewing the best, negotiating an offer… It’s a lot. Imagine going through all of that, finally hiring a candidate, and waiting for their start date to arrive – only to discover that they’re totally wrong for the job, and completely at odds with your company values.
Many businesses start working with Jira because it can offer fantastic benefits for quality of work as well as productivity. This is a very powerful tool that can be extremely useful in its ability to be deployed by a wide range of organisations while being adaptable to their individual needs; it is highly flexible. However, for all of its benefits, working in Jira can be intimidating and overwhelming.
It’s a big industry, software. There’s a lot of money to be made, and a lot of fun and satisfaction to be had. With skills in DevOps, you’ll always be in demand – as a freelancer, or as an employee. But DevOps isn’t for everyone, and it’s certainly not an easy ride. Let’s look at what it takes to practise DevOps, and how to become a DevOps engineer.
Atlassian’s deeply integrated ecosystem of tools is now an essential part of thousands of companies. In fact, the company claims to have over 200,000 customers. And it’s no wonder; Jira, Confluence, Trello – and everything else in the full Atlassian suite – offer incredible power and flexibility. These tools are so well connected that using any combination is seamless, once setup is complete.
It’s a big industry, software. There’s a lot of money to be made, and a lot of fun and satisfaction to be had. With skills in DevOps, you’ll always be in demand – as a freelancer, or as an employee. But DevOps isn’t for everyone, and it’s certainly not an easy ride. Let’s look at what it takes to practise DevOps, and how to become a DevOps engineer.
Jira has a massive problem. And it’s not even Jira’s fault. Does any of this sound familiar? This is all because of Jira tickets; not how Atlassian has created the platform – but how we, as users, are writing them. Jira tickets, when written badly, can destroy productivity, cause friction, and lead vocal members of your team to demand a switch to a different platform. To avoid this, it’s important to know how to write Jira tickets effectively from the get-go.
