r/code • u/ScrabbleKnight • May 06 '22
What differentiates a good programmer from an average programmer?
6
u/kd9019 May 07 '22
A good programmer knows how much he doesn’t know. Follow me for more deep quotes.
5
u/cblegare May 07 '22
Good programmers will learn enough about the domain and use creativity and divergent thinking to anticipate possible improvements (features) in order to write code that they won't need to completely trash the next week, also without overengineering anything and writing the absolute minimum amount of code to solve the problem at hand.
4
u/E-ID10T May 07 '22
Many things, but in my opinion their ability to truly understand a problem both from a big picture perspective and the detail simultaneously.
What I mean is, an average programmer will see a problem. And go, OK let me write this code to solve THIS problem, a good programmer will look at the problem holistically and realize that if I do this thing, it might have an impacct down stream or on an existing peice of the system. Good programmers understand their tool, their system and the context in which they code and they utilize all of that to develop a well though out and robust solution to a problem.
This might sound strange but I found that many lack this ability, and it is through no fault of their own. Many courses, degrees and boot camps focus only on code and tools, and do not put enough emphasis on thinking through a problem and truly thinking like a programmer.
2
May 07 '22
That’s something I do often is just think i have a solution then my brain goes wait but won’t that fuck something else up
1
1
u/ZbP86 May 07 '22
Well, I met 'hollistic' programmer once, and frankly it was quite a disaster.
1
u/E-ID10T May 07 '22
Really? I'd love to hear the details on why it ended up being a disaster if you don't mind sharing
1
u/ZbP86 May 09 '22
As word Holistic become buzzword in past decade, it kinda lost it's original meaning. Guy was not holistic in sense that he was able to perceive problem in complex way, past its boundaries and beyond. Let's say he was clueless. His coding skills were almost non-existing but he believed he can code in some esoteric, intuitive way. TL;DR it didn't worked out well.
7
May 06 '22
Google searches:
Average programmer: How to loop through 2 array and find comment values between them
Good programmer: Site:https://stackoverflow.com "matching values between 2 arrays"
5
1
May 07 '22 edited May 07 '22
It's highly opinionated, but I think a good programmer knows the basics basis, and an average programmer counts on some sort of frameworks.
1
u/ScrabbleKnight May 07 '22
Can you expand on this? What do you define as the basics, and what do you define as frameworks?
2
May 07 '22 edited May 07 '22
Sorry I meant to say basis. And I think if I get a chance to comment again. I would say a good programmer always gets things done. And I think people knows the basis tend to have better judgements therefore tend to get things done.
When I said basis and frameworks, An analogy would be making a car (basis) vs driving a car (frameworks). You cannot go faster than the car's speed limit if you know only driving a car. But if you know to make a car, there is a chance you could make a faster car therefore go faster.
3
u/Significant-Bed-3735 May 07 '22
Ability to learn.
There are people that are stuck being mediocre at best, because they are reluctant to learn from their mistakes, from code reviews or from any advice given to them.
Then there are those that have to spend years to get good at a particular language/ problem domain. Ending up as OK programmers in general.
And then there are those that use every bit of advice, information and feedback available to improve. Those are usually the best and after a few years the difference between someone eager to learn becomes glaring.
2
May 07 '22
Good programmers are craftsmen (or craftswomen) Their code is easy to read and follow. They think about the poor slob that will inherit their code someday. They actually provide enough documentation, breadcrumbs and examples, that someone else can use the program without a massive investment of time reading and rereading every line of code.
I’m always baffled by programmers that invest hundreds if not thousands of hours writing a program, but can’t spend a few hours writing a usable man page or README file.
2
1
u/oleg0 May 07 '22
A good programmer can always prove to the chef - that this program does not need to be developed
1
1
1
1
u/RunawayDev May 07 '22
Ability to stay in scope. Falling into the overengineering pitfall is typical for the enthusiastic but ultimately oblivious to project scope junior dev.
1
1
0
0
8
u/heeroena May 07 '22
the willingness to read the documentation