Reputation
5,797
Top tag
Next privilege 10,000 Rep.
Access moderator tools
Badges
1 13 31
Newest
 Custodian
Impact
~267k people reached

Aug
24
comment Is directly using Make considered obsolete?
Yes, i stand corrected. Actually, I remember one criticism of autotools is precisely that it contains code even for very old systems, so scratch the "recent". I still stand by the Windows part, though.
Aug
20
comment Is directly using Make considered obsolete?
"will compile virtually everywhere" -> "will compile on most recent Unix-like systems". I don't think autotools works to any relevant degree on a Windows system, for example (discounting Cygwin/MingW, which is really a Unix-like system on top of Windows).
Aug
17
comment Is it better to call a function that doesn't have an effect at that point, IF it improves code clarity?
@ChrisCirefice: If the number of views grows, you can create some kind of "ViewState" object/class, which enforces this invariant. Then use that for switching etc. With so many views, some kind of manager object probably makes sense anyway.
Aug
7
comment Modern.IE VM license
@Andy: Thanks for the information. Consider posting this as an answer :-).
Aug
7
comment Modern.IE VM license
@Andy: Yes, I wondered about that, too. I don't know why the license is the way it is - though I suppose MS have their reasons. As to MSDN downloads: I just looked at one of their licenses (MS Visual Studio Community edition ) and it does not restrict to non-commercial use. Still, even IANAL and all that, I do not see how developing software for money can not be considered "commercial use", so I stand by my answer.
Jul
16
awarded  Custodian
Jul
16
reviewed Close Is it common to have downtime at a programming job?
Jul
16
reviewed Leave Open Balance between “right tool for the job” and familiarity
Jul
16
reviewed Leave Open My coworker commits and pushes without testing
Jul
16
comment How do we control which features get released?
@gnat: Yes, this means more testing, as I mentioned. Nothing is free in life :-). However, in my experience this is manageable, as long as you keep the number of feature flags under control.
Jul
15
revised How do we control which features get released?
expanded
Jul
15
answered How do we control which features get released?
Jul
10
revised Source code “prints” at release
expand "CM"
Jun
17
comment When is optimization not premature and therefore not evil?
Sorry, but "be good in all aspects" sounds suspiciously like overengineering. Plus, it's probably not realistic - life is always about tradeoffs.
Jun
11
comment Is turning UI (or other) features on and off based on dates-a code smell?
Yes, testing is really tricky if the UI can change based on various factors. If it must be done, it must be done, but it helps to keep variation to a minimum - and to provide a way to toggle the UI for testing, independent of things like current date.
Jun
11
comment Is turning UI (or other) features on and off based on dates-a code smell?
"it's better to simply deploy an update at the correct time" Nitpick: Not necessarily... . For example, deployment may require downtime, which is not practical at the time the switch must be made. Or maybe there will be some period of parallel use... it really depends.
Jun
11
comment Is turning UI (or other) features on and off based on dates-a code smell?
@ArturoTorresSánchez: The former - the whole idea is to put the business logic (such as date calcluation) into the server. Anyway, this would make a good question of its own :-).
May
31
comment verify a defect is a production defect or not
"If testers raise bugs ad hoc rather than against the specific requirements the developers are working too it causes delay and frustration." That sounds like a dangerous attitude. Are you saying the testers should just ignore obvious problems because that's not what they are supposed to test? Note that new bugs need to be prioritized (just like features), so not having time assigned should not be a problem - you fix the bug once it has been prioritized and queued for fixing.
May
7
answered Modern.IE VM license
Apr
30
comment Commit at a logical checkpoint only, or also when you're at a stopping point?
If you have changes that you do not want to push without rebasing/amending them, you can start your commit message with "WIP" (git -m "WIP: dirty test code"), and activate the pre-push hook under .git/hooks/pre-push. Then git will refuse to push as long as the commit exists.