https://www.ltaake.com/blog/ Recent content in Blogs on ./lt Hugo -- gohugo.io en-us Sun, 27 Nov 2022 03:14:08 +0200 https://www.ltaake.com/blog/2022/11/should-i-document-this/ Sun, 27 Nov 2022 03:14:08 +0200 https://www.ltaake.com/blog/2022/11/should-i-document-this/ If you consider how software documentation is usually created in everyday life, you can certainly understand why some developers keep it rather thin. (It should be mentioned that I’m talking about an agile development process in the broadest sense - extensive up-front documentation, dictated from the ivory tower and written down in stone tablets would not be something I would want to write about here). So now, as an agile developer, when I’ve built a new feature or done a major refactoring, I ask myself the question, “Should I document this change? https://www.ltaake.com/blog/2022/07/a-naive-case-of-ux-design/ Wed, 20 Jul 2022 03:14:08 +0200 https://www.ltaake.com/blog/2022/07/a-naive-case-of-ux-design/ Some time ago, due to a lack of a mobile flat rate, I started to not only pay for the landline connection included in my DSL line, but actually use it as such. Because it was a VoIP connection and I didn’t have any suitable hardware at hand, I decided on a software solution in the form of a Raspberry Pi with an Asterisk server and an app to use my smartphone as a telephone. https://www.ltaake.com/blog/2017/11/applied-functional-refactoring-in-java/ Fri, 17 Nov 2017 03:14:08 +0200 https://www.ltaake.com/blog/2017/11/applied-functional-refactoring-in-java/ Just a little bit of context upfront: the project on which I did the refactoring was Spring Boot based and about two years old. It did already use some functional elements, for example the new streaming-API. More advanced features were just sparely used, so there was a lot of space for introducing more functional elements. Repeated conditional operations For most projects that have domain entities with a large number of fields, there might be some mapping, state checking, or similar operation that involves evaluating structurally identical conditions for each field and executing some functionality, e. https://www.ltaake.com/blog/2017/09/static-code-analysis-for-domain-driven-design-part-1/ Fri, 29 Sep 2017 13:45:08 +0200 https://www.ltaake.com/blog/2017/09/static-code-analysis-for-domain-driven-design-part-1/ Of course, doing a static code-analysis can’t in any way tell you that you are doing DDD correctly. But what it can do, is to help you to meet some basic principles like a clean aggregate structure and keep them intact over time. The implementation details of Domain Driven Design that I have taken a look on for my analysis are mostly based on common literature, in particular “Domain-driven Design” by Eric Evans and “Implementing Domain-driven Design” by Vaughn Vernon. https://www.ltaake.com/blog/2017/09/introducing-an-advanced-latex-toolchain/ Fri, 15 Sep 2017 20:51:00 +0200 https://www.ltaake.com/blog/2017/09/introducing-an-advanced-latex-toolchain/ At some point most, if not all, developers have to write some kind of large text document, be it documentation or a bachelor, master or other thesis. As you’re just reading this right now, I suspect you might be just starting to write one yourself. Choosing the toolchain for such a document wisely makes enormous differences. That is especially important if you’re working on a document with multiple people. I learned this the hard way, while writing a 40 page documentation with 6 people using different versions of Word running on different operating systems.