About events and component orchestration
Breaking architecture into components and using events to orchestrate high-level functionality helps build large, maintainable, testable, and scalable software systems.
Read articleArticles on software engineering, research, best practices, clean code, systems architecture, and more.
129 articles · 11 pages
Breaking architecture into components and using events to orchestrate high-level functionality helps build large, maintainable, testable, and scalable software systems.
Read articleProgramming is more than writing code: it means solving problems, serving others, abstracting, designing for the future, and creating software with criteria.
Read articleWriting is a powerful tool for self-knowledge, creativity, and emotional release; it helps organize thoughts and turn ideas into something tangible.
Read articleA guide to writing, publishing, and distributing a book in the 21st century without relying on traditional publishers or external permission.
Read articleA practical book on digital entrepreneurship, personal focus, work management, and lean project development in technology.
Read articleThe three technical books by the author are brought together in a single ebook to offer a complete view of professional software development.
Read articleBook Hub is an open editorial platform for authors who want to publish their works without depending on traditional publishers and with greater autonomy.
Read articleRemote work requires self-discipline, trust, and a different way of organizing work; it can be a great opportunity when done well.
Read articleKaizen applies the logic of small changes to gradually improve software, productivity, and the quality of professional work.
Read articleTechnical pauses help improve the design and architecture of the system, preventing chaos and preparing the project to grow in an orderly way.
Read articleProfessional security does not come from hoarding knowledge; it comes from sharing it, delegating, and growing together with the team.
Read articleA software project is never truly finished; it reaches a useful level of maturity, but there is always room to improve through review, refactoring, and continuous learning.
Read articleNo results for this search.