4 ms·
This methodology is so simple that it is brilliant. My favorite one was the file extension problem... of course ubuntu would solve everything. No file, no probl
by GrandMasterBirt 18y ago
This methodology is so simple that it is brilliant. My favorite one was the file extension problem... of course ubuntu would solve everything. No file, no problem! I am surprised he didn't tell the receptionist to roll on the floor saying hail linux while he did a witchdoctor dance. Now only if my office had a receptionist so we can do this.
As to why computer jobs require competence, it is because any engineering position (computer, or otherwise) requires competence. Would you live in a building without knowing that it won't collapse tomorrow because the construction company didn't know how to calculate the required strength of the steel beams needed to support the structure?
A company won't go under because a secretary does not know how to make perfectly formatted word files from the get-go. Where as it will fail if a software company's key product is managed/coded by incompetence.
- Decibel 18y agoHaving worked as a EE, I can assure you that 99.9% of software is NOT engineered. It's not even close. Truth is, if you actually took the time to properly engineer software odds are your company would fail, because basically no one knows how to actually manage it. On top of that, people have grown to accept buggy software (unless it's an embedded system, and even that's eroding).