Regarding deployment, the Nix Package Manager (https://nixos.org/nix/) is a very clean solution. It is a package manager and build system, that can be used for building and deploying libraries and applications, with maximal sharing of the same binaries on disk and RAM, but also great isolation: every user/environment/application can use the version of libraries it needs, without influencing other users/environments/applications.
This approach https://nixos.org/nix/ joins the benefits of dynamic and static libraries. Applications are ELF files directly referencing the version of the library they want to use. Different versions of the same library can coexists on the same system, also of glibc in case. Containers on the same machine can too use the same repository of applications and shared libraries, with minimum overhead.
I don't know how it is usable in production: I only started playing with it, but it is very sound from a theorical point of view.
Software projects with the lowest levels of defects had the shortest development schedules and the highest development productivity... software defect removal is actually the most expensive and time-consuming form of work for software
(Jones 2000)
In "Code Complete 2", McConnell says:
Microsoft's applications division has found that it takes three hours to find and fix a defect by using code inspection, a one-step technique, and 12 hours to find and fix a defect by using testing, a two-step technique (Moore 1992).
So paradoxically code-inspection could reduce development time of good-enough products.
Meyer transmits a strong sense of intellectual excitement and the book is very fascinating. The subject is about the design of the perfect/ideal O-O programming language. He describes every choice balancing pragmatic and academic considerations and the result is one of the best designed programming language.
The book is useful not only for the final result, but also in the rational way used to solve the problem, that can be adopted in many other situation.
When the technology will be more mature/advanced, programmers, data analysts, writers or spreadsheet users can benefit of e-ink based monitors.
For example when I need to study some technical-report in PDF format I must print it on paper, because I am stressed from the LCD screen light bulb and I can not concentrate enough on the content.
Creating a neat C++ framework when what the world really needs a non-Microsoft browser is nothing but a deriliction of duty: a piece of vanity code. What we Brits call pointless "willy waving".
This is correct for a commercial project but for an OSS project a modular well-designed code is an important quality because often programmers work on it for fun.
Now that Firefox has an easy to extend structure (XUL, plugins, ecc..) the OSS development process can show its strengths because many developers can enhance it in a pleasant way.
Slashdot Mirror
Regarding deployment, the Nix Package Manager (https://nixos.org/nix/) is a very clean solution. It is a package manager and build system, that can be used for building and deploying libraries and applications, with maximal sharing of the same binaries on disk and RAM, but also great isolation: every user/environment/application can use the version of libraries it needs, without influencing other users/environments/applications.
This approach https://nixos.org/nix/ joins the benefits of dynamic and static libraries. Applications are ELF files directly referencing the version of the library they want to use. Different versions of the same library can coexists on the same system, also of glibc in case. Containers on the same machine can too use the same repository of applications and shared libraries, with minimum overhead. I don't know how it is usable in production: I only started playing with it, but it is very sound from a theorical point of view.
A study at IBM concludes:
In "Code Complete 2", McConnell says:
So paradoxically code-inspection could reduce development time of good-enough products.
Meyer transmits a strong sense of intellectual excitement and the book is very fascinating. The subject is about the design of the perfect/ideal O-O programming language. He describes every choice balancing pragmatic and academic considerations and the result is one of the best designed programming language.
The book is useful not only for the final result, but also in the rational way used to solve the problem, that can be adopted in many other situation.
When the technology will be more mature/advanced, programmers, data analysts, writers or spreadsheet users can benefit of e-ink based monitors. For example when I need to study some technical-report in PDF format I must print it on paper, because I am stressed from the LCD screen light bulb and I can not concentrate enough on the content.