How to become a bad software developer? How to guarantee it?

Why would anyone want to know how to be a poor developer ?😲

OK
mmmm
FINALLY I COMMIT -- I am a very poor Prmg. Developer

vinuchel24Why would anyone want to know how to be a poor developer ?😲

These are going to be just the points that developers here can express so that those with common sense can avoid them at all costs.

OK
Point 1- During my initial stage of learning abut programming I never give much Honour to the Importance of " HEADERS "
n they beat me evry time .. huh

hiiii am final year computer science student ,can u people suggest ideas for my final year project on c

R.prashanthhiiii am final year computer science student ,can u people suggest ideas for my final year project on c

Dear Prasanth,
You can choose from below if you want -
1. Customer Billing System Project in C
2. Hospital Management System Project in C
3. Library management
4. Employee record - Enhancements
5. Telecom billing
6. Bank management

As per my understanding and experience, my advise is - whatever the project you choose, you should have a complete knowledge about the in and out of the system. Everything must be very clear, technical and sound. You should not reject simple projects thinking the faculties award lesser marks to simpler projects. They always wants the project to be made in genuine manner and the persons who did the project, do know the in and out of the project. Please let us know if you need further help on this. Good luck my dear friend. Thanks. 😀

Ankita KatdareMany engineers around here are coding or have been into programming at some point of their life. You all must've made mistakes or started off on a bad foot or know someone who really is pretty bad at it. What are the characteristics according to you that make a bad developer? What practices or advice one can follow to guarantee that they become a really poor developer? Share in replies! 😀

1. One who do not know the process flow of the problem statement. Must have flowchart in mind or on paper. 😀
2. Redundant code
3. Comments missing - Which makes the task of the future editor of the code to understand the logic in one go.
4. Not following the standards to assign the name of variables/function name.
5. Not doing thorough unit testing of the code
Will update the list if I recall more!! 😀
----------------------------------------------------------------
#-Link-Snipped-#
---------------------------------------------------------------

It's basically for code review but if you write code like this. You are a bad programmer.

Bad Coders :

• No indenting in code.
• No comments.
• No Naming conventions.
• No exception Handling.
• Worst Complexity of algorithms

.........and the list goes on 😨
Well, to have all flaws, it gotta be deliberate bad coding 😛

I agree with this line from Kaushal
"1. One who do not know the process flow of the problem statement. Must have flowchart in mind or on paper. 😀"

I have seen many programmers just writing program without actually understanding the problem statement completely which in turn at the end leads to problem or buggy code, so if someone who thinks, if I know what is "if", "for loop", "while loop" then I am a software programmer makes me good programmer, programming is not just about syntax, it is about logic

Koushal Patel3. Comments missing - Which makes the task of the future editor of the code to understand the logic in one go.

This is so true. Sometimes it feels like the original programmer believes that he is the one and only creator of the code and no one will ever touch it again. Hell, even if he goes to read his own program after 5 years, he won't be able to make out which function serves what purpose. Why You No Add Comment, folks?

Magic numbers is something I really have tough time with, when I try to understand code written by some one else.
Rest all is fine with me.
3-4 level nested loops, ifs and else can be digested, complexity can be optimized
but I would never get hang of magic numbers.
Well this is just my opinion 😀

- Code optimization
- Profiling
But hey, rule number one : First make it work, rest all (the two factors mentioned above) comes later.

Adding to my list
1. If someone fails to learn from his/her mistakes and does the mistake repeatedly. Ignores the peer review comments.
2. A programmer who doesn't know what he doesn't know and isn't interested at all to find out.
3. Programmers, who knows what the code does, but not, how the code does!!
4. Those who ignores warnings and only bothered about errors. 😉
5. Who do not welcome criticism.
6. When they do not worry about the syntax, nomenclature and possess "chaltaa hai re" attitude!! 😉😀😉😁
7. Suppose, You run their code in your machine, and you get a defect and their first reply, "In my machines, it worked absolutely fine!! 😛😁 "
----------------------------------------------------------------
#-Link-Snipped-#
----------------------------------------------------------------

See my coding either in QTP or Selenium (Java) I am the worst programmer.

You know why, when i have to debug my code it takes me 20 mins to understand what i was trying to do.

So the complexity is something that makes me a worst programmer! I dont add comments or any headers I just make it work 😀

The best piece of code is one with comments !

1.forgets to leave comments.
2.leaving exceptional handling.
3.not providing meaningful names to program and variables(even the programer who is 1st to work on ends up in confusion )
4.not using configuration files.
5.writing all code in a single file.
6.giving less importance to security leaving there code vulnerable to attacks.
7.not discussing with the team before starting.

beingchinmayThe way to altering this is programming liabilities. PCs are additionally the main mass-market customer thing where the merchants acknowledge no obligation for deficiencies. The reason cars are so very much planned is that makers face liabilities in the event that they spoil. An absence of programming risk is viably an immense government sponsorship of the PC business. It permits them to create more items quicker, with less worry about wellbeing, security, and quality.

Cool story, bruh!
How is it related to the topic, can you elaborate it ?