Reputation
783
Next privilege 1,000 Rep.
See votes, expandable usercard
Badges
5 12
Impact
~21k people reached

  • 0 posts edited
  • 1 helpful flag
  • 101 votes cast
Jul
22
comment Is a programmer's gut instinct an acceptable answer with regard to design decisions?
@Thomas Owens: I think you read the title and not the question. The last sentence is key "I know where to start looking, and I might even make a recommendation, but it's almost a subconscious effort. When is this acceptable (if ever)?"
Jul
22
comment Is a programmer's gut instinct an acceptable answer with regard to design decisions?
Too harsh. Good developers, with experience, build good instincts--they certainly need to be vetted, but never following your instinct is almost guaranteeing you're taking the long-road every time.
Jul
20
comment Refactoring into lots of methods - is this considered clean or not?
I would strongly advise you to read a copy of Robert C. Martin's "Clean Code", which contains several specific metrics that advise you on how much/little to put in your methods.
Jul
14
comment I'm a manager. How can I improve work relationships and communication with programmers?
The old rule-of-thumb for turning an estimate into a delivery-date is to multiply it by 400%. Estimates often forget to include all the ancillary coding, and it's critical a development manager knows how much to pad estimates rather than trying to eek out more accurate numbers in the first place.
Jul
14
comment I'm a manager. How can I improve work relationships and communication with programmers?
@kevin -- don't forget external training as well. Each engineer has probably already paid $100k out of their pocket for their degree; and that degree is probably severely out of date (technologies change more-or-less annually). Make sure they're being sent to refreshers frequently (a major conference every year or two, small conference a couple times a year). A few thousand dollars in keeping an existing developer up-to-date is significantly cheaper than on-boarding a new hire.
Feb
28
comment Is writing comments inside methods not a good practice?
I agree with your basic conclusion--but I would offer a different interpretation. Whenever your code is unclear, you should consider whether you need to clean-up the code, or whether you have to add a comment. Comments don't resolve the real issue, and they should be a last-resort in correcting difficult code.
Feb
28
comment Is writing comments inside methods not a good practice?
...I agree, but you can also explain the "why" in code. Sometimes this means wrapping a system-call inside a well-named method; comments are not the only means of explaining why
Dec
27
comment Which things instantly ring alarm bells when looking at code?
@Steve314 -- I agree, there is always a minimum level of complexity that can be reached, and in some/many cases the result is still quite complex. Rather than leaving it in a single method though I would consider refactoring into a new class of simple methods
Nov
12
comment Do I need to understand algorithms and data structures to be called a programmer?
"software simian" is always the preferred terminology
Nov
11
comment Should I return from a function early or use an if statement?
eww. Is that pre-validation? Or is it in a validation-dedicated mehtod DoSomeFunctionIfSomeCondition?
Nov
10
comment Would you put your Stack Overflow profile link on your CV / Resume?
It's always a good response to the "what programming-related activities do you do outside of work?" question.
Nov
4
comment Is it ever ok to have an empty catch statement?
Like @Michael says -- it's not quite empty since you've got the comment there; it should be obligatory to add a "this catch intentionally left blank" comment if there isn't a statement
Nov
2
comment What makes C developers so curious if “i++ == ++i”?
it's still important to understand the differences in C# -- just because you seem to only use them in for/each loops doesn't mean that's the only place you'll find them
Oct
27
comment Is Entity Framework ready for production?
Working with both is a great way to learn how to work with both. It's a little like learning both VB.NET and C#--you ask questions when you see differences, and asking those questions greatly enhances your understanding in the end.
Oct
27
comment Maintainability of Boolean logic - Is nesting if statements needed?
good to know. I'm not familiar with Delphi but in C# you can be confident in the && and || operators performing short-circuit evaluation. Going from one language to another usually has some gotchas, and it's good to be firm about doing code reviews to help catch those little issues.
Oct
26
comment Why does adding more resource to a late project make it later?
+1 for citing THE answer to this question
Oct
25
comment Which things instantly ring alarm bells when looking at code?
@Prof Plum -- What example can you give? Usually the alternative to multiple nested if's is to break it out into (many) methods. Junior developers tend to avoid this as though it's less desirable than the if's; but usually when pressed they say "if's do it in fewer lines". It takes someone confident in OOP to step in and remind them that fewer lines != better code.
Oct
22
comment Are code reviews necessary for junior developers?
juniors also learn much faster reviewing a senior's code--it lets the senior lead-by-example without having to explicitly tow the junior along. It can be fun to ask a junior to review code and ask them, as homework, to come up with an alternative solution to compare and contrast. I'd rather have a junior follow precedence than re-invent a wheel (which usually comes out oblong)
Oct
22
comment Are code reviews necessary for junior developers?
@Gratzy -- simply because we're not perfect. Our team has grown significantly, and we have some turnover (mostly contractors). In the past when we back off on the review policy problems creep back in nearly immediately. The review process is simply a critical step in maintaining an effective team and producing a quality product. Reviewing all code isn't difficult; especially if you have a couple senior devs who are very good at finding uneeded code. Most duplicate code originates from developers who do well, but just aren't aware of an existing approach.
Oct
22
comment Are code reviews necessary for junior developers?
@tia -- I understand the need to rush, but our early-investment has always made a positive ROI. Inevitably not doing an early code-review lets issues through that delay our ship-dates and result in other features being cut to address the features we thought were done.