3 ms·

Sure, this sounds like good advice. But I'm relatively new at developing software, and I cant really identify "stupid shit" just yet. So what are some dumb thin

• Deestan 15y ago
  > So what are some dumb things developers constantly do? People will give tons of various anecdotes on this, but they apply to them, not you. The stories they tell are just the scorched remains of a unique learning experience that can rarely be communicated verbally. Keep doing things that seem interesting and hard. Don't be afraid to do stupid things. Everyone has to do a stupid thing at least once to learn from it. Identifying and eliminating your own stupidity afterwards is what will make you good. Whether you identify the stupidity yourself, or has it pointed out by some helpful master is up to you. Both work. TL;DR: http://ed-thelen.org/comp-hist/samp-IBM-think-sign.jpg http://ed-thelen.org/comp-hist/samp-IBM-think-sign.jpg
• dekz 15y ago
  > "If it's not broken don't fix it." Definition of stupid shit is relative though, what's stupid in the codebase today may not have been so stupid 3 years ago. What might look stupid upon first visit might actually be the only reasonable way to solve the problem. But then there's other stupid shit, hacks for quickly solving a certain edge case. For example abusing Java type erasure and collections. Other stupid shit from experience is avoiding risk of "new" technologies, (Still on CVS).
• qeorge 15y ago
  Not commenting code. Not updating a variable's name when its purpose changes. Not refactoring long blocks of code into functions. Skimping on documentation. Making changes on master that should have been made on a branch. The list goes on.. In short, being lazy when you know better.