3 ms·
No part of a system is the most important part, from a car to a huge organization, all parts are equally required to interact and hence make such system 'work'.
by bikamonki 11y ago
No part of a system is the most important part, from a car to a huge organization, all parts are equally required to interact and hence make such system 'work'.
Having a clear functional organization at the start (and respect it throughout development) is very important, but after that is equally important to code clean and efficient code, to test, to debug, etc. Then, going up and dow on the solution stack is important to make the right decision on hardware, OS, server, services, etc.
- erikb 11y agoOkay, if you need to be so detailed you also have to argue keep in mind that some parts are more important than others. Example with the car: If you leave out the head-rest you might sell your car for a few bucks less or have a harder time to get a customer (low importance), but if you have a car without some kind of motor you don't even have a car (high importance). While there are many things that are important they all have different priorities, though. All that said I'm also very sceptical that there is one thing you can learn and then you are a the best programmer. You have to learn thousands of things. And sometimes learning a currently low priority thing now might save you hundreds of hours of pain further down the road. So it's really hard to say what you have to learn.
- bikamonki 11y agoNope, a car is not a system that was built to be 'sold', it was built to transport people/things safely. If you remove a part of a system and the system still works as intended, it was not part of the system. The head-rest can be removed and the car will still run but with less safety. Hence: all parts of the system are equally required to interact and make the system do what the system should do.