Eines der agilen Prinzipien lautet: “Funktionierende Software mehr als umfassende Dokumentation”. Viele Entwickler sind daher der Meinung, dass sie überhaupt nichts mehr dokumentieren bzw. im Code kommentieren müssen. Wer im Manifest jedoch weiterliest, erfährt “obwohl wir die Werte auf der rechten Seite wichtig finden, schätzen wir die Werte auf der linken Seite höher ein”. Dokumentation spielt auch in der agilen Softwareentwicklung sehr wohl eine wichtige Rolle…
I’ve updated my Goodreads account recently and I saw, that there are already 100+ tech books listed that I read. Celebrating this milestone, I’ve decided to create my first TOP 50 list of “books without version numbers”. These are books that aren’t specific to any programming language or framework. There is much value in these kinds of books because they won’t get outdated that fast. From the list, I can see that my preferences are: Agile, Refactoring and Patterns. Have fun browsing!
I regularly come across some weird classes that smell already purely on their poor naming. A few of them end with “Manager” (e. g. BankAccountManager, ReservationManager or ServiceManager, urgs). Why is that bad? Imagine a manager as a real person
Lately, I came across an old presentation of Adam Bien about Vernunft-Driven-Design (in English: Rationality- or Reason-Driven-Design). I generally like the mindset of Adam Bien and I found it particularly interesting that he talks about non-technical stuff in this video.
My notes of an amusing talk about Do’s and Don’ts in software development. Here are the main points I took away: 1. Conference-Driven Delivery Prepare your talk last minute. Remember: Communicating is probably more important than coding. Do Test Driven