The availability of detailed technical posts suggests that the work is well-documented and transparent. This is a positive sign for clients who want to understand the engineering decisions behind the code. The blog format allows for a clear view of the methodology, particularly around monorepo structures and tooling. However, the critical note is that this level of detail might not be available for all custom projects, or might vary in depth. It seems the availability of information is high, but the availability of specific, tailored service packages is less clear. For teams who value open engineering practices, this transparency is a significant advantage, though the lack of a clear service menu remains a minor drawback in the overall assessment.
Questions about software, systems and decisions
What is software, systems and decisions?
It is a personal blog by Fabio Menchicchi, a full stack engineer based in Cusco, Peru, covering software architecture, tooling, and developer experience. The author works on applications and backends, writing about technologies such as TypeScript, React, React Native, Node, Nest, Go, Java, and Nx. Posts include technical discussions on monorepo package imports and UI bugs in website development.
Who is the author and what is his background?
The blog is maintained alongside the author's professional software engineering work and serves as a notebook where he writes things down to find out whether he actually understood them. If a post helps readers understand something too, that makes him happy.
What are Fabio Menchicchi's qualifications and history?
Fabio grew up in Arezzo, studied computer engineering in Bologna, and now writes code from Cusco, in the Peruvian Andes. He has thirteen years of experience, with ten years spent on an enterprise supply-chain platform where he built the frontend department from nothing.
What specific technical topics are covered in the blog posts?
The site mentions that the next post is building on Nx and TypeScript project references, specifically discussing importing a package in a monorepo behind the scenes. It also covers four UI bugs that never failed, noting that a UI bug does not have to fail to be a bug.
What core principles guide the author's approach to software development?
The author believes that types and tests are what let you change your mind a year later, and that a release should be fast and automatic. He also notes that the only thing that really matters is the direction, and getting that right allows every change to be a small one.
How can visitors connect with the author or learn more about the site?
The website footer and about page include links to GitHub, LinkedIn, and a mail contact option. The site version is v1.8.8 with commit hash 5820ad6, and it was built with love.
What recent developments or tools are mentioned in the content?
The blog discusses the importance of conventions, stating that a lot of the author's recent work is with AI. He also emphasizes that a release should be fast and automatic, reflecting his experience building a frontend department from scratch.
What specific technical challenges are explored in the blog?
The site provides a detailed look into the mechanics of monorepo package imports, explaining how one import line can be influenced by three things: a rule about package dependencies, a TypeScript resolver, and whatever has to turn that file into something that runs.
What is the official website of software, systems and decisions?
The official website of software, systems and decisions is fabiomenchicchi.com.
How is software, systems and decisions rated on Trustburn?
On Trustburn, software, systems and decisions has a rating of 3.6 out of 5 based on 5 reviews.
AI-generated from reviews on this page. Verify anything important with the company directly.
The variety of technologies listed covers almost every modern web need. It is impressive to see such a broad stack handled with such expertise.
Comparing this offering to traditional software consultancies reveals a distinct difference in focus. While many firms emphasize business strategy and stakeholder management, the available information points to a heavy concentration on the engineering layer itself. The emphasis on Nx monorepos, TypeScript resolvers, and automated release pipelines suggests a tooling-centric methodology. This approach likely yields high-quality, maintainable codebases but may lack the broader business alignment services that enterprise clients often require. The blog posts demonstrate a strong grasp of developer experience and architectural conventions, which is valuable for internal engineering teams. However, for organizations seeking end-to-end product development from concept to market, the specific scope of work beyond the code itself remains unclear. The neutral stance here reflects a recognition of strong technical skills tempered by uncertainty about broader service delivery capabilities.
Wow, the technical depth is absolutely stunning! It is fascinating to see such expertise in monorepos and TypeScript. Yet, I am left wondering what exactly is being sold. The blog highlights impressive engineering skills, but the actual service deliverables remain a bit of a mystery. It is a thrilling read, but I need more clarity on how these skills translate to specific client projects and pricing models.
The information available suggests a highly specialized practice rooted in deep technical expertise rather than broad generalist services. Fabio’s background in full-stack engineering, particularly with TypeScript, React, and Go, indicates a strong capability in modern web architectures. The focus on monorepos, tooling, and developer experience aligns well with teams seeking structural rigor. However, the service offering seems niche; it appears tailored for developers who value architectural clarity over quick fixes. Pricing structures are not clearly defined, leaving potential clients to infer value from the technical complexity demonstrated in the blog posts. For someone considering this company, the emphasis on types, tests, and automated releases suggests a premium, engineering-first approach that may require further clarification on cost and scope before committing.
News
No news yet. This is where the business shares its own updates and press.
Photos
No photos yet. Photos shared by reviewers will show up here.
Widgets
Get the widget for your site →About software, systems and decisions
The site is a personal blog by Fabio Menchicchi, a full stack engineer based in Cusco, Peru, covering topics in software architecture, tooling, and developer experience. The author works on applications and backends, writing about technologies such as TypeScript, React, React Native, Node, Nest, Go, Java, and Nx. Posts include technical discussions on monorepo package imports and UI bugs in website development. The blog is maintained alongside the author's professional software engineering work.
- Website
- fabiomenchicchi.com