Here is a solid bunch of theory on how to reason about dependencies in software engineering. (yet, this is highly applicable in practice, of course, if digested by brains.)
The material might feel a bit clumsy, but I tried my best.
Today's talk is about Test-Driven Development from the perspective of OOA/D beardsmen. Read on ivanzakutnii.com Read, like (if you are) and comment on DEV.TO
Hello! Today, we'll be talking about API Gateways: when to utilize an API Gateway, understand the features and values it provides, and determine situations where it may not be necessary.
Hello there! Here is a brief review of the most common practices in software engineering for documenting, reasoning, and describing system architecture:
Hey guys, I've just updated my page. I got rid of the separate 'About Me' section and consolidated all the necessary information on the landing page – including greetings, a CV download button, a recap of my working experience, and a learning tracker. What do you think? 🤨
I've also added the Bookshelf page, where I'll mention all the great books that I highly recommend for everyone 'in IT guy' to read.