Iteration 4 - fixes only
Nov 2, 2018
WebCalc's fourth iteration is mostly about fixing issues, big and small. First, I'm making my Calculator stateless. Then I'm fixing all issues related to number formatting, especially input parsing.
Testing is storytelling
Oct 25, 2018
Tests do not only exist to verify the absence of known bugs. They're also documenting the expected behaviour of a system. Moreover, they're showing developers how to use code.
Iteration 3 - formatting and cleanup in calculator module
Oct 10, 2018
WebCalc third iteration. I'm adding multiplication and division. During that I need to deal with formatting and limiting number of digits.
Iteration 2 - actual calculations and modules separation
Sep 21, 2018
WebCalc second iteration. I now have two Gradle subprojects and clearly separated calculator module. It now can actually add and subtract.
Iteration 1 - setting up with one test
Sep 5, 2018
WebCalc first iteration. It includes setting up Gradle project with JUnit 5 and Spring Boot and then writing a controller driven by an integration test.
Motivation and plan
Sep 4, 2018
Motivation behind creating a not-so-small example project that shows how to develop a Spring project using TDD.
Jun 22, 2018
I think we can all agree that having our codebases more readable and understandable would make our lives much easier. In this post, I'm trying to point out at least a few ideas that influence understanding.
Supporting understanding with simplicity
Jun 15, 2018
Some time ago, my colleague Joy Clark wrote about simplicity. I’ve also approached this topic once before. I’d like to follow up on both articles and show how simplicity can boost our understanding of software. I will also propose that we look at other disciplines to see if and how simplicity affects them. Maybe we can benefit from their experience.
What’s all the fuss about? Why do we even talk about simplicity?
What do I believe in
Nov 2, 2016
Below are my guiding principles, that are the basis of what, how and why am I doing with regards to software development.
Long term development speed First and foremost I understand my main responsibility as delivering value as fast as possible in the long term. By delivering value I mean adding, changing or removing features, that “business” requested, but also things like:
improving processes around me, both technical, like application deployment, and business, like simplifying stock management, proposing and introducing new techniques and technologies whenever I feel that they will improve things, sharing knowledge within and outside of the team (blog, mentoring, pair/crowd programming, etc.
Code quality as a winning factor
Oct 21, 2016
Software development seems to me like the only discipline where practitioners can get away with producing crap. If you’re a doctor and you screw up surgery or treatment, in the worst case you will kill your patient, in the best you will not make his/her situation worse. If you’re a bridge builder and you’ll make a mistake during construction, in the worst case the bridge will collapse killing people, in the best case, the bridge will be usable only after adding some additional support to it.