Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
-
There are different types and need for developers. In some cases it's going to be how much you are able to chern out code as fast as possible and in other cases it's going to be able to sit back and really think things through before you fuck shit up.
It's kind of like saying, what type of runner is the best?
It's an open ended question without a real answer. Because it depends on the situation. -
Also, a team can use both focused developers that are experts on some parts and others that are more generic.
A developer can be better at one role but worse for another.
Comparing two requires context, a 40 year veteran in cobol will beat most in old banking systems but would probably loose to a freshman in webdesign since there are so much different requirements in how you think, its not just another language. -
I think people who are adaptable and able to seemlesly transition between tasks / programming languages / APIs are the most valuable. By that I mean people who are open to learning new things but also people who go above and beyond to make sure they are properly adopting the philosophy/best practices of what they are learning. To give you an example, someone coming from Java or C# to C++ should focus on really understanding the language rather than forcing there Java/C# habits into there coding style. (I've seen it where people wrap everything in classes even helper functions just because that's how it's done in Java or whatever.) That way when you start working with a group that has been using C++ you mesh in and your code conforms better without a bunch of refactoring.
-
I’m in ops so I can only speak to my interactions with and observations of developers. As far as pure coding ability goes I can’t give any input.
In my mind the gap between good and great programmers is perspective and communication. Not only understanding how their work fits into a larger whole *but being able to communicate this understanding clearly* is the dividing line.
A programmer can develop a web service. A good programmer can explain how to interface with that web service to other programmers or technical people. A great programmer can convince non-technical business staff to invest in the development of this service, then build it.
Related Rants
Found something true as 1 == 1
On the most serious of notes, and i need yall to think hard about this.
What makes you a good developer whether Backend or Frontend or Web or mobile.
What qualities actually make you a good developer?
I mean, we all use google, github, stack overflow etc. So what makes Programmer A better than Programmer B.
and in a more practical sense, ive been coding for two years now and i have deployed an API written in node and an instagram automation tool in PHP (which is down now due to lack of funds), i lack frontend knowldge (but i want to make up for that) and i have projects that when i finish, with my connections can and will blow up in terms of income. now you on the other hand, what makes you better than me?
and lastly, how much code do you have to change from an existing project, lets say from github for you to comfortably say, yes this is mine.
question
node
php
developers
github
api
frontend
mobile
backend
what makes you better
stack overflow
web