1,100 reputation
622
bio website yourcodeisshowing.wordpress.c…
location Quebec City, Canada
age 37
visits member for 4 years, 1 month
seen Oct 27 at 18:55

Developer with 8 years experience. I work with J, C, C++, C#, SQLite, MySQL, VBA, and a bunch of other odds and ends.

On Twitter: @MPProg


Feb
26
awarded  Caucus
Feb
13
accepted Keeping tech support on the latest software version
Feb
13
revised Keeping tech support on the latest software version
edited title
Feb
13
asked Keeping tech support on the latest software version
Feb
5
comment How can I deal with a team member who dislikes making comments in code?
@Saul, I've been there too. It's hard to change people. Keep at it. Another approach, after about 6 months, your old code doesn't even look familiar. It's become someone elses. Let him re-read some of his old stuff from a while ago. Or, you can use peer pressure: "I can understand everyone else's code at a glance." At some point, you (and he) have to understand that you're paid to create software. Time is precious. Optimize time developing by leaving no ambiguities.
Feb
5
comment How can I deal with a team member who dislikes making comments in code?
@Saul In that case, reply "I've read it and could not understand it all. I should not have to run it to know what it does."
Nov
28
comment Keeping an enum and a table in sync
Well yes, that's the idea. But if I set the ID's to one place an to others, I'm working off the assumption that they are both right. It's a loose link, no?
Nov
28
comment Keeping an enum and a table in sync
@suslik They are both pronounced the same. Synch and Sync.
Nov
28
comment Keeping an enum and a table in sync
It's not so much about new statuses (which would definitely warrant a modification of both database and program), but Id values.
Nov
28
revised Keeping an enum and a table in sync
deleted 1 characters in body; edited title
Nov
28
asked Keeping an enum and a table in sync
Nov
2
awarded  Notable Question
Oct
30
awarded  Yearling
Sep
26
awarded  Excavator
Sep
26
revised Why is prefixing column names considered bad practice?
Just like prefixing column names, prefixing questions with a tag is frowned upon
Sep
26
comment What good reasons are there to capitalise SQL keywords?
Capitalizing SQL keywords I can understand. Most table declarations and queries I see capitalize EVERYTHING, table names and columns included.
Sep
26
suggested approved edit on Why is prefixing column names considered bad practice?
May
18
comment Should the most recent date be named 'start' or 'end'?
There's also a case to be made for reading left to right. The order goes that way in more languages than the reverse. Both human and programming languages.
May
18
comment Should the most recent date be named 'start' or 'end'?
I agree with the desire to make something adequate and clear. I'm working with an old code base where any notion of "first" and "last" are labelled "a" and "z"... "Start" and "End" sound much more natural.
May
18
comment Should the most recent date be named 'start' or 'end'?
Simply "StartDate", "EndDate", and good documentation. There is a case to be made for documentation. A well made API has appropriate documentation. Furthermore, if you want to get cocky, throw an Exception if EndDate < StartDate, and document that too.