Embark on a journey of knowledge! Take the quiz and earn valuable credits.
Take A QuizChallenge yourself and boost your learning! Start the quiz now to earn credits.
Take A QuizUnlock your potential! Begin the quiz, answer questions, and accumulate credits along the way.
Take A QuizKindly log in to use this feature. We’ll take you to the login page automatically.
LoginGeneral Tech Technology & Software 3 years ago
User submissions are the sole responsibility of contributors, with TuteeHUB disclaiming liability for accuracy, copyrights, or consequences of use; content is for informational purposes only and not professional advice.
Most people don’t understand what we do at all, and don’t care, and we don’t care whether they know or care.
The only thing that annoys me about public perceptions of programmers, is that everyone I know wants me to fix their personal computer for free. “Since it would be so easy for you.” Knowing how to write a program isn’t the same as knowing how to fix one, when you don’t have the source code or access to any of the internal structure. And it probably isn’t a software bug at all. More likely they don’t know how the app is supposed to work, and I don’t know either, unless I use that app a lot. We don’t know how to fix computers better than anyone else who works with them regularly, unless we have studied up on that for other reasons. Such as providing free tech support to our relatives.
Hiii Everyone,
Same with writing software - you have to do more than just type in stuff. You have to understand your presentation platform, your service and data layers (if applicable), the performance implications of the decisions you make, interoperability concerns, modularization, architecture, networking, etc. A lotgoes into developing software, and it takes a lot of work to do it, and do it well.
That it it not "engineering", and the spec can change mid development because it is just code! I wrote the control system for a supersonic wind tunnel. The facility manager kept adding features, which caused months of code to be thrown out. After 4 cycles of throwing up to 6 months of code at a time away, I refused to make any changes without a software specification. The manager was a mechanical engineer, so I asked him to design a gearbox for my truck, then I kept changing the specs. He got rather upset and stopped working on it for me. After asking why he can't just hack the gearbox because it is just gears, he started to see why I wanted specs. My job got far easier after that.
No matter what stage you're at in your education or career, TuteeHUB will help you reach the next level that you're aiming for. Simply,Choose a subject/topic and get started in self-paced practice sessions to improve your knowledge and scores.
Kindly log in to use this feature. We’ll take you to the login page automatically.
LoginReady to take your education and career to the next level? Register today and join our growing community of learners and professionals.
Your experience on this site will be improved by allowing cookies. Read Cookie Policy
Your experience on this site will be improved by allowing cookies. Read Cookie Policy
manpreet
Best Answer
3 years ago
As a software engineer, what do most people get wrong about coding that drives you crazy?