Hi...
Hi, I’m Kuba. As a child, my passion for video games sparked my curiosity for computers and electronics. Becoming a software developer was the only logical career choice for me.
Since 2010, I’ve been developing software professionally, gaining experience with a wide range of programming languages, frameworks, and methodologies. Right after graduation, I had the opportunity to start as a Python developer and program my first modern web application using the Django framework. During my studies, I had some initial exposure to Java and C++, but I was impressed with how much faster development was with Python – especially since it required significantly less code. Around this time, I also discovered jQuery and was excited that JavaScript could be used professionally. #python #django #jquery
Unfortunately, there weren’t many Python projects in my area, so I assumed that Java was the only viable next step. As a Junior Java Consultant, I was primarily assigned to the dreaded frontend tasks, which allowed me to further expand my jQuery skills. #javaEE #applicationServer #boilerplate
At that time, AngularJS was at its peak – and it was love at first sight. The development speed was incredible, and the testability was outstanding. My shock was great when, in October 2014, I was in Paris to witness Google announce the end of AngularJS’s core concepts ($scope, controllers, jqLite). At that time, I was experimenting with Phonegap/Cordova and hybrid apps based on AngularJS, all connected to REST APIs. #angularJS #rest #HATEOAS
This was followed by my time working in large corporations – an experience that had a lasting impact on me. Technology became secondary; the biggest challenge was managing people’s interactions with technology. Previously, I had always worked in small teams of 2-3 specialists (frontend, backend, DevOps), each focused on their niche and tasks. Suddenly, I found myself in cross-functional teams where potentially everyone worked on everything, and the code was merged back into a large, shared code repository. This taught me the critical importance of conventions and quality standards, which should be automated as much as possible. My main principle became to develop for the team – ensuring that if I were unavailable, anyone could continue from where I left off with minimal effort. #100devs #prettierLintTest
I was able to bring these principles to the next companies I worked for, helping to build new teams, tech stacks, and developers. Now, I want to share this knowledge with a broader community – especially with those who aspire to become developers. That’s the motivation behind this website.