Publications from the Jaewa team: articles on uncertainty, ways of working, professional ethics and transparency, technical deep dives and case studies. The articles are in Italian.
Several years ago TDD arrived, Test Driven Development. The underlying idea was simple: the number of errors a compiler, even the best one, can find in a piece of software is tiny compared with the problems that emerge at runtime, when the system is actually used. The TDD proposal seemed trivial: write, alongside the application code, test code as well, that is software that automatically runs other software to check that…
At Jaewa we have been working for years on system integration, legacy software re-engineering, distributed architectures and custom solutions; we work with large organisations, SMEs, in-house products, critical operational platforms and ecosystems where various systems have settled over time: a variety of contexts that makes it necessary to compare similar problems seen from different angles. From the experience gained in this variety…
In the world of custom software many discussions always begin and end the same way: “Turnkey project or Time & Material?” It is an understandable question, but it is also, almost always, the wrong question.
The word analysis has an ambiguous reputation in the software world: it evokes long documents, waterfall approaches, weeks of work without code and the widespread feeling of paying for something that produces no immediate value. Those who commission a project tend to see it as an unproductive cost: you pay for working software, not to read diagrams. Even among developers, analysis is sometimes perceived as an obstacle. The…
“Let's build a prototype” is one of the most common phrases in software projects. The problem is that it often means different things to different people. For some it means building a scaled-down version of the product: fewer features, less polish, but already designed to evolve towards production. For others it is a space for free experimentation: you try out a technology, write code quickly and watch what happens.
In the theory of dynamic systems, effective control is not based on perfect prediction but on feedback. You observe the behaviour of the system, measure the deviation from the target and introduce progressive corrections. The idea is not to anticipate every possible disturbance but to build the capacity to react. Software development in critical contexts follows a similar logic.
In software, saying no is not an act of closure. It is an act of responsibility. We would like to always say yes, naturally: projects are the engine of our business, and accepting them is almost always the easiest path, sometimes also the most profitable in the short term. Yet it is not always the right thing to do.
Let's start from a simple diagram. The horizontal axis (X) represents the complexity of the computing problem to be solved. The vertical axis (Y) represents the cost, that is the effort needed to build a software solution. The scientific community agrees on one point: as the complexity of the problem grows, so does the effort required to solve it. This growth is not linear: in many cases it is more than proportional and in…
In recent years artificial intelligence has become one of the most discussed technology topics. It is not hard to see why: it has the potential to profoundly change the way we live, work and develop software. The spread of AI, however, has also produced a recurring phenomenon: the illusion of certainty. Many organisations look for definitive answers on how to adopt it, as if there were already established and universally…
If one of these topics concerns a project of yours, write to us. It will not be a salesperson who replies, but an engineer. Or fill in the survey first: three minutes to bring your situation into focus.
