818 reputation
511
bio website
location
age 29
visits member for 4 years, 2 months
seen Nov 7 at 12:44

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.
Oct
22
comment Are code reviews necessary for junior developers?
@Gratzy -- I absolutely swear by it; normally it adds ~%10 to the dev-cycle; a small investment for how much we catch early on.
Oct
22
awarded  Critic
Oct
22
comment Are code reviews necessary for junior developers?
I couldn't disagree more. Every line of code should go through at least 2x reviews... the original developer should review absolutely every line-change prior to commiting them, and at least one other developer should perform a peer-review as follow-up. Very rarely does code make it through a review without at least 1 good question being raised; peer reviews also increase awareness between team-members of what--and how--others are completing their assignments.
Oct
21
comment Hard-copy approaches to time tracking
It's off to a good start, but one shortcoming is that I still have to track my start/end times to tally them in the checkboxes. I'll be continuing with it to see if I improve--but I've already caught myself starting a few tasks and forgetting when I started them
Oct
21
comment How do you keep focused through long compiles
@Jonn if you buy into Spolsky's take on Evidence Based estimates then they are part of your time-on-task :)
Oct
21
awarded  Editor
Oct
21
revised Maintainability of Boolean logic - Is nesting if statements needed?
added 346 characters in body
Oct
21
answered Maintainability of Boolean logic - Is nesting if statements needed?
Oct
21
comment Maintainability of Boolean logic - Is nesting if statements needed?
just curious, what language are you working with?
Oct
21
answered Who does test-driven development?
Oct
21
answered How do you keep focused through long compiles
Oct
20
comment What should a tester (Quality Assurance) person do on a scrum team?
A good position to place them! It keeps them up-to-date on what's happening, and they can be involved in as many side-conversations as needed to ensure they're aware of the details as they evolve.
Oct
20
answered What should a tester (Quality Assurance) person do on a scrum team?
Oct
20
revised Hard-copy approaches to time tracking
retagged