Search
Online Courses
Pocket Guides
Last Update: 28.11.2018. By Jens in Newsletter
The next article is about a new software system for medical clinics and how it changed the work of different kind of users like doctors, assistants and biz administrators. It is a prime example of the unintentional consequences a new software has on people. It is a long read though.
Last Update: 27.11.2018. By Jens in Newsletter
I read some interesting articles over the weekend and I am going to share them with you. Todays’ is about trust or better distrust at work and how projects are set up for distrust, which makes working together towards a single goal difficult.
Last Update: 23.11.2018. By Jens in Newsletter
Let’s see if I can finish my thoughts on this today. I am bit distracted, so bear with me.
Last Update: 22.11.2018. By Jens in Newsletter
Following up on yesterdays email. The difference between the perception of material and immaterial goods is not the only reason why legacy apps are forgotten. Another one is the economic value and the way our modern world thinks about it.
Last Update: 21.11.2018. By Jens in Newsletter
Legacy apps are the bane of developers. Many have to work on one, nobody loves them. But why do they grow to such a pain?
Last Update: 20.11.2018. By Jens in Newsletter
I know legacy apps cause many issues. Nobody really wants to work on one. The funny thing is, most of them are already the legacy problems roughly a half year after the first release. At least in my experience. Anyways, one of the problems can become a nightmare after a few years.
Last Update: 16.11.2018. By Jens in Newsletter
Keep a list of your assumption during development. After all, we’ll probably never ever answer all of our assumptions before we develop anything.
Last Update: 15.11.2018. By Jens in Newsletter
Assumptions are everywhere.
Last Update: 13.11.2018. By Jens in Newsletter
If you think about going solo - becoming self-employed, read this article first and this comment too. It’s so true.
Last Update: 09.11.2018. By Jens in Newsletter
Besides being consistent with naming, I think readability and easy understanding are also important. I sum that up as use-case-driven.