My second article on Kent Becks rules for simple software design dives right into the 2nd rule (“Reveals intention”) and one of the hardest aspects of software development: Naming.
I am very happy and grateful to announce that I will be speaking at this year’s German Oracle user conference (DOAG 2018). It’s my very first experience as a conference speaker (even my experiences as conference visitor are quite limited) and although there is some tension it’s really a dream come true for me: I’ve always enjoyed teaching and sharing Read more…
Knowledge about SW Design is beneficial for every task related to software development and affects developers of any skill and experience level.
I try to deep-dive into @KentBeck ‘s rules for simple design and how they can be applied to DB development
It was a strange moment when Jacek, co-author and maintainer of utPLSQL, asked me last November if I’d like to be part of the next ODTUG CodeTalk series.
And first, it was a disaster.
Why I didn’t blog for several weeks: Open Source engagement for @utPLSQL.
Introduction to the Dunning-Kruger-effect, how likely we are to overestimate our skills in areas not as visible as we might have thought – and how to defend against it
Databases are different to applications from a development view, therefore a state-based approach to development/deployment doesn’t fit very well. Learn about migration-based database development and how it empowers agility
No software is perfect and we should create meaningful, automated self-tests to give us the confidence in continuously changing and improving our software.
Version Control has been around for over 40 years, but still it’s not used in many database projects. This article is a plea and guide to use Version Control in database projects.
We database people are very strict about redundant data in our database design – why aren’t we as strict about the code we write?