|
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'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!
|
|
|
|
|
Damn I must be missing something interesting, series 3 of what? (I may get to binge on 1&2)
Never underestimate the power of human stupidity -
RAH
I'm old. I know stuff - JSOP
|
|
|
|
|
The Mandalorian[^] But between series 2 and 3, you need to watch The Book of Boba Fett[^] as the last three episodes continue the Mandalorian story line and there'd be a "big jump" or "plot hole the size of Tatooine" if you didn't! 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!
|
|
|
|
|
I watched the first one and was not overly impressed, but now I can binge watch both, by which time s3 should be complete. This is going to piss off the better half, I going to want the BIG TV.
Never underestimate the power of human stupidity -
RAH
I'm old. I know stuff - JSOP
|
|
|
|
|
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!
|
|
|
|
|
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.
|
|
|
|
|
Some of the best advice everyone or anyone can use, especially writing code.
"A little time, a little trouble, your better day"
Badfinger
|
|
|
|
|
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 ...
|
|
|
|
|
Learn assembler : this forces you to also understand how a computer works.
|
|
|
|
|
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 
"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  .
|
|
|
|
|
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.
|
|
|
|
|
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
|
|
|
|
|
Reading a core dump. I miss those days.
"Before entering on an understanding, I have meditated for a long time, and have foreseen what might happen. It is not genius which reveals to me suddenly, secretly, what I have to say or to do in a circumstance unexpected by other people; it is reflection, it is meditation." - Napoleon I
|
|
|
|
|
Study other programming libraries and languages for their good ideas.
Ex.
C++ STL (Standard Template Library) design principles and performance.
SmallTalk - amazing pure OO design. I really like the Boolean design with SmallTalk.
SQL - amazing power built on top of a few, consistent building blocks
Functional Programming concepts. Leads to very testable/provable code
State based design
Etc
|
|
|
|
|
I think only hard work and learning from your mistakes and trying to be better will help... no tools or packages will help.. all the other thinks you can learn but end of the day its your code that matters
Caveat Emptor.
"Progress doesn't come from early risers – progress is made by lazy men looking for easier ways to do things." Lazarus Long
|
|
|
|
|
wisdom, sagacity, discernment, patience, imagination, non-defensiveness, curiosity.
«The mind is not a vessel to be filled but a fire to be kindled» Plutarch
|
|
|
|
|
Defend your code like pirates defend their treasure. But also know when to bury it and supply only a hastily scrawled map (documentation) to it. 
Bond
Keep all things as simple as possible, but no simpler. -said someone, somewhere
|
|
|
|
|
Understanding the domain you are writing code for. I know that's quite specific per project, but nonetheless important I feel.
|
|
|
|
|
Not a package nor tool, but you need to know how to debug, either with the help of an IDE/debugger tool (like VS) or without it (the old way, by placing messages or flags sent to screen, database, or console).
Also you need to know how to search for help, may sound a little odd, but a few new guys/gals I work with seem to be lost on how to look for help on internet... i remember when I started, you have to look at books and magazines, now it's easier with search engines, sites like codeProject, etc, but you still need to know how to ask questions/look for answers, how and what to search, and that comes with experience (and some common sense).
HTH
|
|
|
|
|
Analytical puzzles. Debugging and trouble-shooting code is a significant portion of one's time writing & maintaining code - no one writes perfect code the first time, every time. If you can't quickly analyze the issue and fix it, then you spend a lot of time on wasted efforts and dead-ends.
This also applies to unit testing. Determining the minimum number of valid tests to test meaningfully different scenarios is as much art as science. Most developers know to test the happy path and the extremes (like testing for one-off errors when working with arrays). But there are many cases that might be less obvious for any specific scenario.
Bond
Keep all things as simple as possible, but no simpler. -said someone, somewhere
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
