# The 11 XALT Steps to Better Code > From Git workflows to automated builds to Jira and XRAY: how XALT puts Joel Spolsky Source: https://www.xalt.de/en/blog/the-11-xalt-steps-to-better-code/ From Git workflows to automated builds to Jira and XRAY: how XALT puts Joel Spolsky's core software development principles into practice. TEAM XALT Atlassian Platinum Partner · 10 August 2022 · 6 min Are you wondering how we code and develop software at XALT? In this blog post, we introduce some of our guiding principles when it comes to software development of any kind. We were inspired by none other than Joel Spolsky (former CEO of Stack Overflow, among other things one of the inventors of Trello), who described the most important steps of programming back in 2000. A lot has changed since then and become easier, but the core principles still apply in 2021 and are a quick and easy way to find out whether your SaaS business model is actually as good as you think, or whether the full potential is being exploited. If you hold a management or team leader position in a company where software is developed, you should ask yourself the following questions and answer them with “Yes”: (From the perspective of job seekers in the software field, it is of course also always good to know whether your potential employer is keeping up with the times) ## **Version control - Do you use it?** Of course we do, after all, we no longer live in the 90s. If you want to track and manage changes to your code and enable more effective collaboration for your programmers, version control is of paramount importance. For us, a Git workflow is essential, but depending on the type of project, we use Feature Branching, Continuous Delivery, and sometimes even Gitflow. We use, among other things, Atlassian's own Bitbucket, as well as GitLab and GitHub Cloud. We place the greatest emphasis on automation. https://www.youtube.com/watch?v=\_w6TwnLCFwA ## **Can you create builds in a single step?** Yes, and we can even go one step further; by using Docker and Bamboo, GitHub Actions, and GitLab Pipelines, this is automatically built for our projects. By using such tools, you can easily automate the integration of code from multiple contributors into individual builds (keywords: Continuous Integration, Continuous Delivery). Further information on our approach can be found here: [https://stackshare.io/xalt/xalt](https://stackshare.io/xalt/xalt) and [https://www.xalt.de/life-at-xalt/](https://www.xalt.de/en/culture/) ## **Do you create daily builds?** Yes, daily builds are your friend when it comes to identifying problems. But why stop there? With CI/CD and automated tests, even multiple builds per day can be deployed! We always create daily builds for our clients and also maintain test servers for them. ## **Do you have a bug database?** Yes! Instead of writing bugs on stone tablets, sticky notes, or simply relying on memory, we have chosen Jira to enable effective, powerful, and versatile bug tracking. We have even gone so far as to be able to [integrate Jira with other bug-tracking solutions](https://www.xalt.de/en/advanced-issue-sync-for-jira/) and thus never lose sight of a bug. Another great thing about Jira is the easy integration with knowledge bases like Confluence, where you can document all bugs and issues in detail. ## **Do you fix bugs before you write new code?** Yes, we always manage our technical debts. What are technical debts? Well, good that you asked! We delve deeper into what technical debts mean for both companies and programmers; you can read all about it [here](https://www.xalt.de/en/blog/technical-debt-in-agile-software-development/). Essentially, it is very useful to fix errors before writing new code. This avoids, among other things, having to go back in time in a software project to find out why the code doesn't work today. The more time passes, the harder it becomes to remember where and when a bug first occurred. Therefore, the methodology of continuous documentation is a great way to achieve this, apart from the fact that errors are fixed as quickly as possible ## **Do you have an up-to-date schedule?** Always. We live agile software development every day, so the concept of an up-to-date schedule naturally applies to everything we do. Our tool of choice on this topic is Jira, which can make project planning and management as simple as possible and as complex as needed. ## **Do you have a specification?** You can bet on it. A product specification is essentially a blueprint that precisely describes what the finished product will do, what its core functions are, who it is intended for, and so on. To make this easily editable and usable by everyone, we use Confluence and a simple integration with JIRA issues, as well as a team of highly qualified and clever cookies who can write technical specifications for a specific issue as if it were your grandmother's cookie recipe. ## **Do your developers have quiet working conditions?** Oh yes, you should provide your programmers (and all other employees in your company) with pleasant and quiet working conditions. Whether in one of our great offices or at home – if you [work with Team XALT](https://www.xalt.de/en/careers/), you have the choice of where to work from. Even after the pandemic, you can enjoy the benefits of home office and remote working. Still too noisy? We can also equip you with noise-cancelling headphones so that you can stay in the "zone" even better. ## **Do you have testers?** It is important to have testers on your team. How else would a bug or a missing feature in your product be noticed? If your customers tell you that there is a problem? Yes, that should be avoided, and testing your software can really help. At XALT, we use unit tests as well as automated tests for our builds, for example with Jira and Bamboo from Atlassian. With XRAY, tests can even be presented in nice frontends. You can read more about it here: [Automated test management with XRAY](https://www.xalt.de/en/automated-testing-with-atlassian/). In addition, Selenium is another tool of choice for testing solutions from the user's perspective. ## **Do you carry out QA tests?** We do, with the help of Jira and XRAY. You can read more about it in this [blog post](https://www.xalt.de/en/blog/quality-assurance-testing-with-xray-and-jira/). ## **Do you use the best tools you can buy for money?** Always. The choice of devices and tools of your choice is the best prerequisite for everyone in your company to feel comfortable. And let's be honest – what is better than bribing programmers by providing them with all the tools, software, and hardware they need to be happy (apart from fair compensation)? So if you work with Team XALT, you just need to tell us what kind of equipment you need, and we will take care of it. Do you agree with our principles and the way we work? Let us know, and if you are interested, find out first-hand how your company can use a few fundamental principles to stand out from competing firms in software development and beyond. If you are a developer looking for a new challenge in a company that makes working with and on software a pleasure. By following a few basic but very important and strong principles such as those mentioned above, please send us your CV and enjoy a smooth and non-binding recruitment process. ## Want to work like this? We're hiring developers for projects across Atlassian, DevOps, and cloud technologies. [Talk to us](https://www.xalt.de/en/contact/) ## More articles ### [XALT Achieves the Atlassian Software Development Specialization: What It Means for Our Customers](https://www.xalt.de/en/blog/xalt-atlassian-software-development-specialization/) XALT has achieved the Atlassian Software Development Specialization – official confirmation that we deliver real value to software development organizations, from prioritization to developer productivity. *XALT News* ### [Agentic AI in the Enterprise: Why Context Matters More Than Prompting](https://www.xalt.de/en/blog/agentic-ai-in-the-enterprise-context-over-prompting/) Why the next AI leap for enterprises won't come from better prompts, but from better context – insights from XALT founder Philipp Göllner at the Atlassian Community Event in Leipzig. *XALT News* ### [Atlassian Cloud Bound Munich: The Future of Teamwork Is Cloud-Native and AI-Powered](https://www.xalt.de/en/blog/atlassian-cloud-bound-munich-2026/) Our recap from Atlassian Connect: Cloud Bound in Munich – featuring a live Rovo demo, the Teamwork Graph, the new Fast Shift migration program, and the key takeaways for XALT customers. *XALT News* --- *This version is for AI agents. Every page of this site is available as Markdown: append `index.md` to its path. Index of all pages: [llms.txt](https://www.xalt.de/llms.txt)*