A lot of people know sh#$t about software licenses. That includes me. One option is then to fear licenses and be afraid of them. This behavior is driven mostly by persistent myths. Continue reading
I refuse to understand the discussion about ‘point junkies’. In short: software development teams seem to exist that are so focussed on earning story points that supplementary requirements are completely ignored. Performance, code quality, stability, etc are important factors for engineers and if you find yourself or your team in such a situation I think you have an HR problem instead.
Teams need to be rewarded for reducing technical debt, in fact, most teams reward themselves. ‘You build it, you run it’ teams know that reduced technical debt, means more BeerOps. Continue reading
Often a lot of effort is put into the possibility of rolling back changes to a production system. The amount of time and money wasted on rollback scenario’s is enormous. I realize not everybody agrees with calling this ‘waste’, but I still feel there is a better way. Continue reading
This is a quote on a blog from 2006 from Werner Vogels (CTO Amazon):
The best way to completely automate operations is to have to developers be responsible for running the software they develop. It is painful at times, but also means considerable creativity gets applied to a very important aspect of the software stack. It also brings developers into direct contact with customers and a very effective feedback loop starts. There is no separate operations department at Amazon: you build it; you run it. Continue reading
If you are building software, you need requirements. They are input for implementation and test and they can serve as means of acceptation. Requirements can be as explicit, implicit, formal or informal as long as it works in your particular situation.
That said, if you have requirements, they must make sense. I often see the ‘too many requirements syndrome’ in projects. Most often caused by someone that obviously had too much time on her hands. Continue reading
In our series about the interns working at Avisi, we feature Maik Diepenbroek today. Maik is rearchitecting parts of the NXP Temptation application with a focus on testability, code quality and maintainability. Continue reading
In our series about the interns currently working at Avisi the spotlight now turns to Danny Cobussen. Danny is working on a concept we call ‘one click deploy‘. One click deploy is about installing applications to a cloud environment where the cloud is not a vendor SAAS offering, but a cloud environment that is fully under the clients control. Continue reading
Once upon a time when software was delivered to a customer the final phase in the project was acceptance. Today the iterative approach in agile software development incorporates acceptance as a recurring reality. This limits surprises afterwards, but does it guarantee project success? Continue reading
This is the next post in our series about the interns that currently work at Avisi. This time we introduce Mats Stijlaart. The Atlassian plugin framework is used on several projects to enable seamless extensions. Mats’s assignment is all about finding an alternative for, or confirm the choice of, the Atlassian plugin framework.