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

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
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
comment Maintainability of Boolean logic - Is nesting if statements needed?
just curious, what language are you working with?
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
comment Hard-copy approaches to time tracking
@David -- I agree entirely, but have yet to find a manager who enables me to single-task
Oct
20
comment Is there a canonical book on Agile?
...so that's where our good kitchen knives and developers from that project went...
Oct
20
comment Is there a canonical book on Agile?
Osherove's book was a GREAT intro to unit-testing--I would also suggest Bob Martin's "Clean Code" for approaches to turning procedural code into OOP
Oct
20
comment Is there a canonical book on Agile?
Uncle Bob can preach quite a bit--but at the end of the day he has some great lessons. His book "Clean Code" was what made me realize what OOP was, and how far off the mark my code had been.
Oct
20
comment Hard-copy approaches to time tracking
printed and glued into my handy-dandy notebook; with some small customizations this could be perfect--we'll see how it serves over a few days
Oct
20
comment Alternatives to time tracking methodologies
A very good and comprehensive approach. The hard part about getting the ball rolling on these approaches is getting developers to understand it's ok for their estimates to be off--so getting them to understand what is done with their estimates and getting them to trust that honest inaccuracies aren't held against them is a critical first-step
Oct
20
comment Hard-copy approaches to time tracking
that very well could be EXACTLY what I need. Multiple tasks tracked in hardcopy with a simple-enough way to switch!!!
Oct
20
comment Hard-copy approaches to time tracking
very nice! I like the Timex still on the stand :D My only concern would be that, in my office, most things that size are made of foam and get thrown at other people :)
Oct
20
comment Hard-copy approaches to time tracking
I like the approach; I've tried something similar with emails where I refuse to check them more than 3-times a day (mid-morning, after lunch, before leaving)--but in that scenario I started to get too many people showing up to reiterate their email--immediately pulling me from my task, and later making me re-read the same email to make sure all questions were answered