5,782 reputation
1227
bio website
location
age
visits member for 3 years, 7 months
seen Jul 8 at 14:29

Sep
14
comment Bogarting the Data Access Layer
@spaghetti: Yea...I'm probably worse than most because I've done a lot of DBA work, so I have twice the "I know how to do it better!" than most programmers. I will say this: with databases, it's a lot more important to get it right early...If you keep adding until late in the project, it's almost certainly going to cause issues.
Sep
10
comment Don't like my current job, want to leave, how to explain this in a job interview?
@job: That's why you take your prospective coworkers out for a beer later. There is nothing wrong with being honest, but don't be negative. Managers imbibe that "power of positive thinking" crap with their breakfast cereal every morning.
Sep
9
comment Don't like my current job, want to leave, how to explain this in a job interview?
+1: NEVER air dirty laundry in a job interview. It just makes you look like an unpleasant, negative person.
Aug
25
comment Do you sign each of your source files with your name?
@sleske: Effectively impossible, I'm afraid. We're not remotely standardized, and any attempt I made to push something like this would devolve into a pissing contest among larger business units about what sort of repo, who'd host it, code naming conventions...Yuck.
Aug
25
comment Do you sign each of your source files with your name?
@sleske: In my industry it's pretty common to pass source around among different business units. Even with compiled code, I put my name on the config files, so when there are issues, they know who to call.
Aug
17
comment Do you sign each of your source files with your name?
@scorchio: I don't send repos to people. I send finished, deployable code.
Aug
17
comment Do you sign each of your source files with your name?
@scorchio: Did you even read what I wrote? The vast majority of people who use my code don't have access to my VCS, so how would that help them?
Aug
4
comment Submit code during interview
I like that answer. If it's specific to their database, what else are you going to do with it? Write it off as the price for interviewing. Also, chances are you're not going to be blowing their minds with your brilliance...Not being mean, but I know enough of that sort of people to know that they never look for jobs, or interview.
Jul
28
comment Where do you use ROT13?
@graham: Yea, I didn't want to go there. I thought about saying the "English" alphabet, which would make sense, but is kinda anglocentric.
Jul
28
comment Where do you use ROT13?
@green Ell. Oh. Ell. 13 is ROTing my brain.
Jul
19
comment How do you keep all those languages straight in your head
+1 for not being all, "Well if you're a real programmer, you won't have any problems." If you program in enough different languages, syntax references are a must.
Jul
18
comment When is code “legacy”?
@jerry: So what made it legacy? Legacy isn't a synonym for "bad".
Jul
18
comment When is code “legacy”?
I agree with this answer most. Legacy is more about being stuck on an obsolete platform than being annoying (yet modern) code that you don't want to support. Legacy code is often quite good (otherwise no one would care if you left it behind!) but it's usually wedded to obsolescent hardware and antiquated languages/libraries/databases/etc.
Jul
13
comment Revenue sharing with customer who is unable to pay development fee
@maple: Agreed. For 50% I would expect the other person to have done just an extraordinary job of planning the app, and also to have some non-technical skill to contribute (art or writing or sound or something)
Jul
6
comment I'm forced to write bad code. How do I save my face?
@ashamed: Sometimes it's more important to have it quick than to have it good. (siryes.blogspot.com/2010/11/…)
Jul
1
comment Humor in Documentation
I leave comments like this when I'm forced to include some horrible inelegant crap due to feature creep, just as an FYI to my hypothetical replacement. "Yes, yes, I am aware that this is bad. It's not wholly my fault."
Jun
30
comment Is it a bad idea to list every function/method argument on a new line and why?
Too many people reduce arguments by dumping them in an array. I'd rather see an ugly mess than cleaner-looking code with hidden complexity.
Jun
29
comment Changing jobs and leaving a project without a leader (aka, me)
Show them the exact loyalty they'd show you. No, I take that back. A professional should never crap on his bosses desk.
Jun
29
comment Be a better programmer or an irreplacable employee?
I've made a career of wandering through the code left behind by "irreplaceable" people, and the surprising thing is how sloppy they tend to be. Generally the only real barrier to fixing their mess is time. And the little bottlenecks they put in to make themselves "irreplaceable" are usually pretty simple: they're lazy, remember? So it's usually not much work to take that stuff out, and then you can fix the rest at your leisure.
Jun
29
comment Be a better programmer or an irreplacable employee?
Everyone is replaceable. If you think you're not, you're lying to yourself.