I help to achieve better results by creating computer programs and by sharing my knowledge about how to program. I combine an engineering approach with a smile and a business-focused mindset. I am a software engineer and IT trainer focused on front-end, JVM, and integration technologies, with relevant full-stack experience. Since 2013, I have been making a living by programming. I share my knowledge at meetups, job fairs, and conferences. I am skilled in JavaScript, Java, and Arduino and in addition to programming and knowledge sharing, I am truly interested in AI, technology, Dragon Ball, MMA, and the strategies of the big companies (Frightful5).
Architecture was always important, but with coding agents it's even more important to nail it. And how to nail something without visualizing, interacting with it, and validating? C4 is an approach getting more and more popularity thanks to its simplicity, and hierarchical abstractions (https://c4model.com/). LikeC4 is a nice JavaScript-based solution for defining models, and visualizing them, potentially following C4 (https://likec4.dev/). Mermaid is another visualization tool, and its competitive advantage is a native support in GitHub Markdown files (https://mermaid.js.org/). Worth to check, but we'll do this in the context of C4 alone. Overall, this presentation should give you a nice idea on how to approach documenting your architecture. 30% on C4, 50% on LikeC4, 10% Mermaid, 10% freestyle/questions.
In 2023 I finally tried https://adventofcode.com/, motivated by an internal company leaderboard and competition. I finished with 47/50 stars, being 4 in our internal ranking, but there were many ups and downs on my way. Advent tasks are usually algorithmic. I went through them using JavaScript and no external libraries (apart from Jest). I want to share some algorithms I got to know, techniques which helped me and some observations about AoC community.
'New day, new framework' - is this still valid? I follow front-end trends and I want to share my thoughts on them. Both experienced front-end developers and the beginners, expecting a quick summary, should find something valuable for them in my talk. I’m going to start with facts & statistics, then we’ll think about the future of JS & its frameworks, talk through npm problems and we’ll finish up with an open topic: can anyone take over our lovely technologies?
I’m going to share my tips and tricks on how to organize JS code. Not only inside a file, but also at a higher level - how to organize a whole project. I’ll use React examples as React is the most popular solution. But also a problematic one from the “architectural” perspective.
There are 1000000+ npm packages. And we have microservices, where teams should own all the frontend, backend, DevOps... How to mix a backend microservice with a company-wide frontend? How to deal with the programmers' preferences who have so many packages to choose from? Let's check micro-frontends!
Czy nowoczesny front-end to tylko i wyłącznie Angular, React lub Vue? Cóż, jak podaje modulecounts.com, każdego dnia do npm-a wpada ponad 500 nowych paczek. Może więc istnieć kilka alternatyw. Podczas prezentacji skupię się jednak na opcji numer 4, jeśli chodzi o frameworki. OK, React jest biblioteką, ale wiele osób myśli o nim w kategoriach frameworka, co ma swoje plusy. Ale, hej, skąd wiadomo co jest 'opcją numer 4'? To zależy... I nie, nie chodzi tu o Embera ani o Preacta.
Angular jako nowoczesny framework
