Pragmatic Brain AB is Petter Wigle's software consulting company.
Petter Wigle is a senior architect, technical leader and developer with 25 years’ experience of software development.
His curiosity and enthusiasm help him to find new solutions to business problems and technical challenges.
Petter cares about quality, productivity and sustainability in solutions and is therefore always engaged in improvements, big or small.
How can I help?
Pragmatic Brain offers consultancy services, from short investigations and assessments to full-time assignments.
Whether your organization is about to build software to support new business capabilities or you are struggling with unmanageable technical debt, I'm there to help.
When you walk in to a room full of developers these days, you get immediately struck by the noise and heat from their development laptops. The computers are really struggling under the load of multiple Docker containers all want to have their fair share of the CPU and memory. Even though everyone is working on a single service at a time, they still need to deploy a handful of other services and a few different data stores a message bus and perhaps a web server. Without all those other things, their service won’t even start. A common solution to this problem is to throw in more hardware. Faster CPUs! More memory! Faster and bigger SSDs! Now your development machine has become a server.
The promise of Agile is that we should be able to develop and modify our software to meet the needs of the quickly changing business. I think we have improved comparing to how it used to be in the waterfall era, but I still think we can do much better that we currently do. We’re still struggling with problems like:
Jason Gorman wrote a great blog post that was inspired by Kent Beck’s post about ageism in software development. I would like to expand on their thoughts and add my own perspective.
It’s very common that developers refer to themselves as being an X Developer or Programmer, where X usually is a specific programming language, such as Java, Ruby or Javascript or an architectural area, such as Frontend, Backend or Database. It can even be specific to a certain vendor or a product. Examples of this is EpiServer, Sharepoint or Salesforce. Some developers like to include their preferred programming paradigm in their professional title. But the only example I’ve seen is Functional Programmer. For some reason Object-Oriented or Procedural Programmer is less common.
I have many times encountered developers that think they can solve problems better than anyone else before them. In many cases they end up with reinventing the wheel. Instead of using off-the-shelf open source or commercial software, they insist on doing their own implementation. This is commonly know as the Not Invented Here syndrome.
