Many coincidences brought me to software development, I stayed with it, because the interaction of individual components have something fascinating. I put special emphasis on the development of robust, sustainable and reliable software. That's why it gives me the most pleasure to implement concepts like Clean Architecture, TDD and Clean Code in real software system scenarios.
Experienced with the creation of entire software systems. Enabled to apply appropriate theoretical concepts to practical scenarios.
Expertise with both front- and backend state-of-the-art technologies. Able to design, plan and develop applications from start to finish despite a focus on backend development.
Chief Expert
Expert
Expert
Experienced
Experienced
Experienced
Expert
Expert
Expert
Expert
Expert
Experienced
Experienced
Experienced
Experienced
Experienced
Experienced
Advanced
Advanced
Blog on Computer Science with a major focus on Python. Several articles, videos and tutorials. Continuing education with knowledge share component.
Have you ever captured new software requirements and asked yourself, where you can place them in your system? This may sound arrogant, but I assume that your architecture is the reason. After reading this article, it should be crystal clear where requirements should be placed with a little help from the "magic" of Uncle Bob's Clean Architecture