By contrast, I was positively surprised by how people at Simply Business deal with these issues. Let me share a few thoughts:<\/p>\n\n\n\n
Development process that just works<\/h2>\n\n\n\n
One common concern I have seen in several companies is the lack of knowledge when starting to work on a new story. Here, the issue was resolved by introduction of \u201cgrooming sessions\u201d<\/em>, where people meet each other to discuss the story and set acceptance (success)<\/em> criteria. Incredible value is provided by these sessions resulting in lower amounts of time being wasted dealing with changing requirements.<\/p>\n\n\n\n Another thing that surprised me was widespread adoption of Lean Startup methodology, especially given the company\u2019s current size. Every single story must have success criteria assigned and, what\u2019s more, is only considered a success if it yields predicted results (i.e. every story is provided with a quantitative success metric). From a developer\u2019s perspective, it means you really know the reason why you are building a given thing. It also helps to keep motivation high in the team as you can see the result of your work.<\/p>\n\n\n\n One of the initial things I was told on my first day at Simply Business was that they have an unwritten rule to refactor first – in most cases you shouldn\u2019t even start working on a story if you are not satisfied with existing design or implementation. That definitely helps achieve good overall quality of code and makes applications easier to maintain. Even now, in the agile software development era, many companies fail at understanding value of collaborative code ownership. What surprised me here is that code reviews can be done by anyone in the team and most work is done in pairs. Additionally, everyone is welcomed to discuss any code submitted to GitHub, even if they’re not working on that particular project.<\/p>\n\n\n\n The most surprising thing happened on my very last day at Simply Business. When I had been walking around the office saying goodbye to everyone, I encountered two product managers trying to amend rates and coefficients somewhere in the system, using an in-house Domain Specific Language (DSL). When writing my master’s degree on building DSLs for business experts, I learned that one of the major advantages of using them is that in some specific cases, non-technical people can understand or even change the code. Just to clarify, DSLs are basically programming languages built to serve very narrow domain. Think of LaTeX – language to create scientific documents or Rspec – language that\u2019s used to describe test scenarios.<\/p>\n\n\n\n Before working at Simply Business, I thought that I would never meet any non-developers working effectively with any form of code. Here, product managers not only work with the DSLs – they actively change the application\u2019s behaviour using Test Driven Development and push their code to GitHub. Even some of the analysts do production deploys, thanks to their amazing deployment scripts and collaboration culture.<\/p>\n\n\n\n I recently learned of the term “tacit knowledge”. Knowledge that, rather than being acquired by means of reading or listening, requires interaction, personal-contact and trust.<\/p>\n\n\n\n If you spend enough time working with the best, you can become one of them, and that idea really stands out at Simply Business.<\/p>\n\n\n\n Want to know more about what it’s like to work in tech at Simply Business? Read about our approach to tech, then check out our current vacancies.<\/p>\n\n\n\nTechnical mastery<\/h2>\n\n\n\n
![\"sb-tech-site-team-opportunities\"](\"https:\/\/www.simplybusiness.co.uk\/wp-content\/uploads\/sites\/3\/2024\/05\/sb-tech-site-team-opportunities.webp?w=768\")
<\/a><\/figure>\n\n\n\nGreat place to work<\/h2>\n\n\n\n
Ready to start your career at Simply Business?<\/h3>\n\n\n\n