Some myths about computer engineering
Software Engineer myths:
“The biggest myth is to believe you are a software engineer”.
All people who come into contact with software may suffer from various myths associated with developing and using software, they are :
Management myths
Myth: My employer will help me manage my career.
Reality: Sometimes true but rarely, and even then rarely as much as you might think. The only person who really cares about your career is you. Your employer only wants to maximize the money they make off you, which may mean keeping you ignorant of the opportunities that await elsewhere, or at higher levels of the company, or even just in different departments.
Myth: The developer who can code the best is the one that would make the best leader, manager, supervisor
Reality: In some cases it is possible who is good in writing a code or developing a software make supervisor or manager. But manager and supervisor need communication skills distribute the work and knowledge about software engineering terms and rules then he/she will be a manager and supervisor.
Myth: young people are the best programmers because they have energy and creativity.
Reality: No. They're just less expensive. They may be exceptional, or not, but that's not an aspect of being young.
Myth: Old people are the best programmers because they have experience.
Reality: No. It's not about having experience, it's about how you use it. And the best experience is knowledge about ones own strengths and weaknesses.
Myth: Design is a waste of time, I have done much bigger projects earlier.
Reality: Lost in a maze, in the middle of project and must re-do the entire stuff.
Myth: Users are stupid.
Reality: If they choose not to buy your software because you've shipped them something that's hard for them to use, then you'll ultimately be the one with the problem. They won't buy your software.
Myth: Meetings are a waste of time
Reality: No, it is not true. Meetings are very important and useful to make some good decisions regarding your firm or working on a project .
Myth: Designing before Coding.
Reality: And them many times, when software engineers get into designing they come up with this intricate monstrosity that no one else can understand. KISS. Use established patterns of design. You can always refactor later.
Customer Myths:
Myth: Occur any error during testing it means that developer has not good skills to make a product
Reality: it is not true, always chance of mistakes. Because we are human not machines
Myth: Requirement changes are easy to accommodate because software is flexible.
Reality: It is wrong
Myth: Share idea with management they consider he will design and implement what in my mind.
Reality: No, It is not true when you share idea after that Q/A session start and roughly sketch. What they want.
Myths: Changing requirements can be easily taken care of because software is so flexible.
Reality: This is not true: the longer that development on the software has proceeded for, the more work is required to incorporate any changes to the software requirements.
Programmers myths:
Myth: Everything I learned in school (data structures, algorithms, etc.) is not useful. I'm in the "real" world now. That stuff is just theory.
Reality: No, it is not true, these subjects are the basic building blocks of computer engineering.
Myth: If I can write a program to print "Hello World", I can build the world using it.
Reality: Big NOOOOO! and just HAHAHAHAHA!
Myth: I don’t know SQL, Hence I am a NoSQL Expert
Reality: those who don’t know database he will not distinguish between what is NoSQL and SQL.
Myth: I am a Rockstar.
Reality: Careful, you may just churn out something 'extremely epic' over the weekend and your poor peers spend the next month picking up the pieces (coding the error cases, tests, etc.) resulting in poor morale and productivity on their part. If 'being the smartest and best' results in a net loss of team productivity, you're not a rockstar.
Myth: I know what I'm doing.
Reality: that type person is overconfident. Not much experience of software field. At the end they will face difficulties to code.
Myth: I will commit all my changes at once, once I am done.
Reality: It goes wrong somewhere, or previous version might be better than this and there is no way to go back, rather than writing from scratch.