Programs vs Products
Formulated my attitude to open source. I do not believe in open source products . I believe in open source libraries, programs, systems, widgets, tools, etc. But not products.
However, symmetrically, I do not believe in commercial tools, widgets, systems, programs, libraries. I believe in commercial products.
How to make a product from the program? If this is a good program, you may not even have to rewrite it from scratch :)
')
0. The software product must have a clear purpose. It should be immediately clear why he is needed and what can be done with his help (and what not).
1. A software product must have a user-oriented user interface designed to perform its tasks. Not an interface for running functions and algorithms, but a user interface.
2. The product must have support, at least through e-mail. Support is not in the spirit of “wait and wait for the bug.” Support that solves the problem the user has.
3. The software product must have user documentation. Instead of the description of functions and not javadoc. The documentation should be clear to this user, not the programmer who wrote it;)
4. The product should be so intuitive to the user that he could not even look through this documentation for years if he doesn’t need anything specific.
5. If the product has a price, it should be as simple and understandable to buyers. Buyers do not like to dig into aspects of commercial licenses, looking for pitfalls, and re-read megabytes, figuring out at what price they can buy it.
UPD: I apologize to those present for the possible kindling of the next holy war. My goal was to discuss rather how to make a product from a (commercial) program, rather than open source strengths and weaknesses.
However, symmetrically, I do not believe in commercial tools, widgets, systems, programs, libraries. I believe in commercial products.
How to make a product from the program? If this is a good program, you may not even have to rewrite it from scratch :)
')
0. The software product must have a clear purpose. It should be immediately clear why he is needed and what can be done with his help (and what not).
1. A software product must have a user-oriented user interface designed to perform its tasks. Not an interface for running functions and algorithms, but a user interface.
2. The product must have support, at least through e-mail. Support is not in the spirit of “wait and wait for the bug.” Support that solves the problem the user has.
3. The software product must have user documentation. Instead of the description of functions and not javadoc. The documentation should be clear to this user, not the programmer who wrote it;)
4. The product should be so intuitive to the user that he could not even look through this documentation for years if he doesn’t need anything specific.
5. If the product has a price, it should be as simple and understandable to buyers. Buyers do not like to dig into aspects of commercial licenses, looking for pitfalls, and re-read megabytes, figuring out at what price they can buy it.
UPD: I apologize to those present for the possible kindling of the next holy war. My goal was to discuss rather how to make a product from a (commercial) program, rather than open source strengths and weaknesses.
Source: https://habr.com/ru/post/9588/
All Articles