The Things more important than Code

There are Programmers living in ivory towers built from their own egos ruling over their systems. Technical solutions for the sake of technical solutions are not the things you should be building. Your code has to solve a problem. It is not beneficial to build a solution and start to look for matching problems. There is this saying: “If all you have is a hammer, everything looks like a nail” – Maslow’s Hammer, Abraham Maslow So make sure you work hard at solving a problem and not building a “solution without a problem”. The Software Developer Your part in this,... [Read More]

Git Best Practices

Over the years I learned a lot about git. Most of the parts I learned the hard way by using it on a regular basis. Here I summarize a lot of the things which I would consider Git Best Practices for using git in a team. Use the force Luke – use the CLI At least give it a real try! Like the young Skywalker you at least once should limit yourself to the bare minimals. Use the force Luke – let go! Over the years I got used to the terminal interface of git in a way that all... [Read More]

11 Ways to Kill Your App in the App Stores

1. Make Sure to Build the Wrong Features Users complain a lot about features which don’t work. So what would be better than building things they won’t use at all? Features not getting used are the ones with the lowest number of bugs reported. 2. Don’t Listen to Your Users This goes hand in hand with the advice I just gave. Why should we listen to our user base? Aren’t we experts who get paid for developing good software? Would you give feedback to a chef who wants to cook you a steak? 3. Ship No Matter What Every user... [Read More]
Tags: experience

What nobody tells you when you get your first Job as a Developer

Hi everybody, I just got a friendly reminder – an annual HR talk with my boss – that my graduation is now more than two years in the past. Time again to reflect upon what I learned during the last two years and how that differs from what I expected. What I expected from my first Job Phew, maybe I should have written this two years ago. If my mind is not playing tricks on me, I remember that I was a bit afraid of what I have to learn and all the things I don’t know. I already knew... [Read More]

What Two Years With Microservices Taught Me

When I joined my current employer we were operating a full blown Monolith with around 20k lines of code. The Monolith was serving an Android and iOS Application which both were also developed within the team. We migrated from that Monolith to Microservice architecture. This article is about our Journey. Also: This is my first programming gig after graduating from university (despite having a formal 3 year education to programming before), so maybe it is better if you keep this in mind while reading this article. The Project Speaking about the Team: In case my mind is not playing tricks... [Read More]