Many years ago, I was trying to sell a house and I was having a very difficult time selling it in the best possible way. At the same time I was trying to sell, I was getting the very best offers on every deal. Then, I realized that I was starting to get the best offers and all I was doing was running off the top of my head.
When I started to build my own website, I realized that the only way I could do my business was to publish in every article about my house. This included the fact that I was doing my own business and I felt like I should write down my own code.
A lot of people say you need to write down your own code to make it stand out. While this might be true, the reality is that in a world of too many blogs, a lot of people are writing about their own code and not about their business. So while this might be true, it is not a bad thing at all. When you take your time writing a code down, you actually take time to think about your business and see what you can do to enhance it.
And while I don’t have any hard numbers to back this up, all of these articles and posts I’ve read about how ampere doesn’t want to write anything new are just talking about this one thing. But you should write down your code.
If you dont, you are not really building anything new. The most innovative companies in the world are those whose code is written by the people who are most innovative. There are plenty of people who feel the same way. A programmer who writes some code to build a new product is not really creating anything new. He is merely re-writing the old code that everyone else already knows how to use.
In a recent article, Ampere, an entrepreneur, wrote about his experience building a company from scratch. “I didn’t build the company, I built the code,” he said. “The code was written by the people who are most innovative, by the people who are the most innovative in the world. And they were all using the same code. So, what you are building is just re-writing the code that everyone else already knows how to use.
A simple example of a company code is the one used for creating a new website, so you can see what happens there.
In short, ampere’s Law applies to software products and software code, but it can apply to any product or any code. If the product or code is simple and it’s not a critical part of the product or code, this may not be a problem. But if it’s a critical part of the product or code then it’s important to ensure that the code is maintained in a way that is not vulnerable to the same bugs that were found in the product or code.
The most common way that software bugs are discovered, and fixed, is by a programmer changing the code of the product. If the programmer is aware that the bug exists, and can fix it, then it’s not a problem. If not, then it may be critical. I’ve never heard of a bug that wasn’t fixed by the programmer.
What I’ve heard is that developers (and programmers in general) try to avoid being too smart. They try to make the code as dumb as possible so it will never be discovered and fixed. The problem with making as dumb as possible is that it puts the developer in a very bad position. If you have a problem that you want to solve, then you want to solve it this way.