My previous blog post on integration best practices gave some general thoughts on service development. When designing services one of the most important parts is resilience of your services and make sure that failure of one services doesn’t collapse your entire world.
There are several key features of a service which combined determine the fault tolerance of your service. In this blogpost I will explain which features contribute to creating better services. Continue reading
We are in Amsterdam for Atlassian connect week. The goal for us this week is to port an existing add-on to the Atlassian cloud. It is still JIRA and Confluence in the cloud, but traditional add-ons can’t be installed. So what exactly is different about writing an add-on for the cloud? 3 things: Continue reading
Atlassian Connect week is in full swing and we are there with a team! We are meeting people from all over the world, from Portugal to Mexico and Australia. Curious about what we are doing and why we are there? Continue reading
My team is using Kanban. A key tenet of kanban is to limit the amount of work in progress (WIP). Work-in-progress limits highlight bottlenecks in the team’s process due to lack of focus, people, or skill sets. For us this is always about testing. To resolve this bottleneck we have found boiler room testing to be a great solution. The name is based on the ‘high pressure’ boiler rooms in submarines. You need to be in there sometimes, but you want to get out as quick as you can. So, how does it work? Continue reading
Because I feel there is a shortage on blogs, long opiniated comparisons and hateful flamewars on Emacs versus vi, I thought I’d write something about it myself. I am kidding of course (just in case you missed that joke). Some people, I know of 3 at least, including me, are free of all the anger and seem to use both editors. Both have their own strength and weaknesses and if you find yourself able to look rationally at both editors you will be able to double the joy of editing in using both. Continue reading
Since all the reall fuss started about pairing and code reviews I’ve only seen one approach in code reviews work really well and that’s pull requests. Pull requests force a peer review and if you implement them well, they rarely get merged without the opinion of an extra pair of eyes. So, I’m really going to write about code reviews in the form of pull requests. This is what I learned. Continue reading
Barri Jansen and I went back into the school banks last year. Mid-2016 we decided to affirm our security related knowledge by getting the CISSP-title. CISSP stands for Certified Information System Security Professional (Lord, how I hate those unpronounceable titles) and is the leading international title in information security. When someone is CISSP, you know two things for sure: (1) he or she has gone through a lot of pain in studying the Common Body of Knowledge (CBK), which CISSP prescribes, and (2) he or she has been challenged for hours in a tough exam to test the gained knowledge. Ok, I’m exaggerating, though there’s some truth in it.
I have a not so guilty pleasure. It’s playing computer games. At the moment, my go to game is Tom Clancy’s The Division from Massive Entertainment. The game is beautifully made and really immersive. I really get the feeling I am walking around in a post-pandemic New York City. From a software development point of view, there is something I want to point out which makes this game even better for me. Or, I must say, that makes my regard for Massive even higher.
We, Avisi, have started an agile journey. A journey with one destination: a fancy ISMS for Avisi. I gladly take you along on our trip, by blogging about the adventures we’ve been through. So fasten your seatbelt, we will travel through a roadmap to remember.