Dig deeper in my resources, page no 5.

Clean Agile Back to Basics a book by legendary Robert C. Martin.

Why is he legendary? Beside tons of publications, it was him who organised the summit that resulted in creating the Agile Manifesto. His contribution to shaping modern software development can not be overestimated. This book is his view on the Agile after 20 years. Martin explains the reasons why Manifesto was written and why we still should follow its principles. He points out all the nonsense that the corporate world has created out of it. We should keep in mind: Agile is for small groups of people building small things. Whaaat? Yeah, that's true! Read the book!

Contract software vendor or build in-house team?

In my work as a technology consultant this is one of the common questions asked by my clients. When they have this dilemma in mind, it is already a good sign.

Technology Job Market Trends.

Based on my frequent conversations with recruitment agencies, candidates, and my exposure to numerous resumes and offers from software houses, it is evident that significant shifts are occurring in the tech job market. This goes beyond the last year lay-offs by large corporations, which, when compared to the industry's true scale, are relatively minor. I have observed several noteworthy patterns that I would like to share.

Theory of the jobs to be done.

Why do so many intelligent people struggle to address the issues of formerly successful companies? W.E. Demming believed the key was to ask the correct questions at the appropriate time. C.M. Christensen's brilliant theory of 'disruptive innovation' explains that a product must "do the job" in order to be successful. This concept helps us better comprehend what our customers are truly looking for. Book will give you a wow moment on every other page. Not reading it may cause serious damage to your career. No matter what you do.

Is Tauri an Electron killer?

ElectronJS-powered applications are ubiquitous; Slack, Visual Studio Code, Figma, Discord, Postman and countless others. My teams have released several projects using this technology, and it certainly works - albeit with a few minor but irksome bumps along the way. Releasing a project with Electron as opposed to Chromium often required a few days of extra effort just to make it stable. Therefore, when Tauri began gaining traction, I decided to give it a shot.

My thoughts on Github Copilot.

I've been using Copilot in my main editor for several months now, and rarely press Tab to accept its suggestions. This usually only happens when I type descriptions, not code. Anyways, I found it helpful, but risky. Let's take a closer look at why.