Which tools or packages should be known by a developer irrespective of programming language to be a better developer?
-
I know that being a developer doesn't only mean writing good code. Agreed that it is a primary responsibility of a developer, but he/she should have good knowledge about other tools like Code version control (GIT, SVN etc.), Project management tools (Jira, Zoho etc.), Good communication skills, knowledge about shortcuts of the editor they use for better productivity. What else comes to your mind, that can help a developer to write better code?
-
I know that being a developer doesn't only mean writing good code. Agreed that it is a primary responsibility of a developer, but he/she should have good knowledge about other tools like Code version control (GIT, SVN etc.), Project management tools (Jira, Zoho etc.), Good communication skills, knowledge about shortcuts of the editor they use for better productivity. What else comes to your mind, that can help a developer to write better code?
Good code doesn't come from packages, or software: it comes from experience. Practice, practice, practice. And then practice some more. This is the way.
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony "Common sense is so rare these days, it should be classified as a super power" - Random T-shirt AntiTwitter: @DalekDave is now a follower!
-
Good code doesn't come from packages, or software: it comes from experience. Practice, practice, practice. And then practice some more. This is the way.
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony "Common sense is so rare these days, it should be classified as a super power" - Random T-shirt AntiTwitter: @DalekDave is now a follower!
-
Good code doesn't come from packages, or software: it comes from experience. Practice, practice, practice. And then practice some more. This is the way.
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony "Common sense is so rare these days, it should be classified as a super power" - Random T-shirt AntiTwitter: @DalekDave is now a follower!
-
Good code doesn't come from packages, or software: it comes from experience. Practice, practice, practice. And then practice some more. This is the way.
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony "Common sense is so rare these days, it should be classified as a super power" - Random T-shirt AntiTwitter: @DalekDave is now a follower!
Agreed, but we can gain experience either from past mistakes or getting guidance from the sr. teammate. In this fast-paced competitive world, learning from mistakes is not a good thing. so, I prefer the second way to get knowledge about things that can make a programmer a good programmer.
-
Agreed, but we can gain experience either from past mistakes or getting guidance from the sr. teammate. In this fast-paced competitive world, learning from mistakes is not a good thing. so, I prefer the second way to get knowledge about things that can make a programmer a good programmer.
Software of any type will help you produce code faster, but not better. Anyone can produce bad code quickly: good developers produce good code, expert developers produce good code quickly. Experience is what differentiates between them. There are two type of learning: rote and skill. Rote learning is memorising stuff: history dates, capital cities, whole books, programming languages. Skill learning is how to do something: riding a bicycle, driving a car, flying a kite, playing a violin, writing code. And learning from your mistakes is how you learn. You don't learn much from anything that works first try - it takes humans effort to learn skills. Think about riding a bicycle: you can read theory, you can watch experts riding in the Tour de France as mush as you like: the first time you get on a bike, you will fall off (unless you have a parent or trainer wheels). And the second time you might get further before falling off. Eventually, your body learns the tiny shifts and adjustments to make all the time and it just works - but you couldn't explain how to do that to anyone in a way that means they get on a bike of the first time and win a race because you don't "know"! Similarly, you can jump in a car for the first time and employ what you learned from watching your dad: you start the engine like this, mash this peddle to the floor, slam this stick thataway, floor the other peddle and let go of the first one. You're off! But you will wipe out on the first corner because you don't have the skill to know how fast is safe. Or you'll overcompensate, clip a curb, and flip the car. Or blow the engine to pieces. It's the same with any skill - the only way to get good at it is to practice!
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony "Common sense is so rare these days, it should be classified as a super power" - Random T-shirt AntiTwitter: @DalekDave is now a follower!
-
I know that being a developer doesn't only mean writing good code. Agreed that it is a primary responsibility of a developer, but he/she should have good knowledge about other tools like Code version control (GIT, SVN etc.), Project management tools (Jira, Zoho etc.), Good communication skills, knowledge about shortcuts of the editor they use for better productivity. What else comes to your mind, that can help a developer to write better code?
What I often miss with developers (especially young ones) is cautiousness, they get over-enthousiastic by new trends and hypes and think they have to use the newest techniques while these are often not time tested and proven. As OG already said its all a matter of practicing, they often have to learn the hard way ...
-
I agree with OriginalGriff (where did that name come from)
"A little time, a little trouble, your better day" Badfinger
My real world name is not a secret - it's Paul Griffin. When I signed up, that name was gone. So was "Griffin", "PGriffin", "Griff", "TheGriff" and every other combo until I got to "OriginalGriff" So that was my name. I've kinda grown into it now, so I respond to "Paul" (Herself), "Paul Griffin" (Herself when I've been bad), "Griff" (Loads of people), "OG" (Some people, mostly here), "Mr Griffin" (Telesales and policemen). I use it a lot on t'interwebs now as it's generally untaken.
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony "Common sense is so rare these days, it should be classified as a super power" - Random T-shirt AntiTwitter: @DalekDave is now a follower!
-
Series 3 out today! Yay! :-D
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony "Common sense is so rare these days, it should be classified as a super power" - Random T-shirt AntiTwitter: @DalekDave is now a follower!
-
I know that being a developer doesn't only mean writing good code. Agreed that it is a primary responsibility of a developer, but he/she should have good knowledge about other tools like Code version control (GIT, SVN etc.), Project management tools (Jira, Zoho etc.), Good communication skills, knowledge about shortcuts of the editor they use for better productivity. What else comes to your mind, that can help a developer to write better code?
Learn assembler : this forces you to also understand how a computer works.
-
Software of any type will help you produce code faster, but not better. Anyone can produce bad code quickly: good developers produce good code, expert developers produce good code quickly. Experience is what differentiates between them. There are two type of learning: rote and skill. Rote learning is memorising stuff: history dates, capital cities, whole books, programming languages. Skill learning is how to do something: riding a bicycle, driving a car, flying a kite, playing a violin, writing code. And learning from your mistakes is how you learn. You don't learn much from anything that works first try - it takes humans effort to learn skills. Think about riding a bicycle: you can read theory, you can watch experts riding in the Tour de France as mush as you like: the first time you get on a bike, you will fall off (unless you have a parent or trainer wheels). And the second time you might get further before falling off. Eventually, your body learns the tiny shifts and adjustments to make all the time and it just works - but you couldn't explain how to do that to anyone in a way that means they get on a bike of the first time and win a race because you don't "know"! Similarly, you can jump in a car for the first time and employ what you learned from watching your dad: you start the engine like this, mash this peddle to the floor, slam this stick thataway, floor the other peddle and let go of the first one. You're off! But you will wipe out on the first corner because you don't have the skill to know how fast is safe. Or you'll overcompensate, clip a curb, and flip the car. Or blow the engine to pieces. It's the same with any skill - the only way to get good at it is to practice!
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony "Common sense is so rare these days, it should be classified as a super power" - Random T-shirt AntiTwitter: @DalekDave is now a follower!
Thanks for clarifying. I didn't mean to get the list of tools to quickly generate the code. For example, I can produce good code, but if I know the code version tool, I can maintain it in a proper way without creating a local backup multiple times just to make sure that I don't lose the track of last working code. Similar way, If I know certain things in the code editor, for example renaming a variable with a shortcut. I can do it automatically rather than going to each place and changing the variable where it was used.
-
Series 3 out today! Yay! :-D
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony "Common sense is so rare these days, it should be classified as a super power" - Random T-shirt AntiTwitter: @DalekDave is now a follower!
-
Bad news I'm afraid: it's on weekly drops ...
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony "Common sense is so rare these days, it should be classified as a super power" - Random T-shirt AntiTwitter: @DalekDave is now a follower!
-
Bad news I'm afraid: it's on weekly drops ...
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony "Common sense is so rare these days, it should be classified as a super power" - Random T-shirt AntiTwitter: @DalekDave is now a follower!
-
I know that being a developer doesn't only mean writing good code. Agreed that it is a primary responsibility of a developer, but he/she should have good knowledge about other tools like Code version control (GIT, SVN etc.), Project management tools (Jira, Zoho etc.), Good communication skills, knowledge about shortcuts of the editor they use for better productivity. What else comes to your mind, that can help a developer to write better code?
Ravi-from-India wrote:
What else comes to your mind, that can help a developer to write better code?
Education. If not schooling, then books. Knowing how a CVS works is assumed, you should be able to write your own or get out.
Bastard Programmer from Hell :suss: "If you just follow the bacon Eddy, wherever it leads you, then you won't have to think about politics." -- Some Bell.
-
I know that being a developer doesn't only mean writing good code. Agreed that it is a primary responsibility of a developer, but he/she should have good knowledge about other tools like Code version control (GIT, SVN etc.), Project management tools (Jira, Zoho etc.), Good communication skills, knowledge about shortcuts of the editor they use for better productivity. What else comes to your mind, that can help a developer to write better code?
A text editor. Learn how to compile/build at the command line. Learn how to track down bugs without a debugger, then how to track them down with a debugger, and learn when to use each technique effectively. Learn not to simply follow "advice" from "experts" -- think about the bigger picture, what subset of a topic is the expert covering. Presenters tend to have a narrow view of what they intend to present, they cannot cover the whole topic in a TED Talk or a YouTube video -- RTFM. One cannot innovate by "following best practices". Safety must never be first or you will never accomplish anything. This is the way.
-
Ravi-from-India wrote:
What else comes to your mind, that can help a developer to write better code?
Education. If not schooling, then books. Knowing how a CVS works is assumed, you should be able to write your own or get out.
Bastard Programmer from Hell :suss: "If you just follow the bacon Eddy, wherever it leads you, then you won't have to think about politics." -- Some Bell.
Eddy Vluggen wrote:
Knowing how a CVS works is assumed, you should be able to write your own or get out.
Hmm, yeah, except last month when I introduced a bug into one of mine and couldn't then fetch out the previous version :sigh: .
-
I'll wait for it to be done and then binge it. This is the way.
Yeah, a week is a long time in politics, but it's even longer between episodes of something good.
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony "Common sense is so rare these days, it should be classified as a super power" - Random T-shirt AntiTwitter: @DalekDave is now a follower!
-
I know that being a developer doesn't only mean writing good code. Agreed that it is a primary responsibility of a developer, but he/she should have good knowledge about other tools like Code version control (GIT, SVN etc.), Project management tools (Jira, Zoho etc.), Good communication skills, knowledge about shortcuts of the editor they use for better productivity. What else comes to your mind, that can help a developer to write better code?
Relational databases (SQL) - learn how and when to use them and only then make a decision when/if not to use them. Code profilers - because nobody is as smart as they think they are and the sooner you can see that you are doing something wasteful the less likely it is to make it into production
-
A text editor. Learn how to compile/build at the command line. Learn how to track down bugs without a debugger, then how to track them down with a debugger, and learn when to use each technique effectively. Learn not to simply follow "advice" from "experts" -- think about the bigger picture, what subset of a topic is the expert covering. Presenters tend to have a narrow view of what they intend to present, they cannot cover the whole topic in a TED Talk or a YouTube video -- RTFM. One cannot innovate by "following best practices". Safety must never be first or you will never accomplish anything. This is the way.
PIEBALDconsult wrote:
-- RTFM.
If there is one and it is not fully crap.
M.D.V. ;) If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about? Help me to understand what I'm saying, and I'll explain it better to you Rating helpful answers is nice, but saying thanks can be even nicer.
