Reputation
221
Top tag
Next privilege 250 Rep.
View close votes
Badges
2 9
Impact
~3k people reached

Jan
4
comment Should I be using advanced techniques most of the time at my new job just because I can?
@user3834459 I would hope that your first reaction would be to just tell the developer to cut out the fancy crap instead of firing him over an easily correctable quirk! This is a common misconception for new programmers that's easily resolved by simply explaining the importance of maintainability and simplicity in a real-world environment.
Jan
4
awarded  Notable Question
Dec
1
comment How to deal with a bug which seems to have fixed itself?
@Frisbee Honest communication is a good way to either confuse non-technical users or piss them off. As for my assumptions, see this comment. I don't really see the point of arguing semantics here.
Dec
1
comment How to deal with a bug which seems to have fixed itself?
@Frisbee As djechlin said, that's just a standard phrase to give to a user. My assumption that there was a release is that the bug was apparently reproducible a month ago but isn't any longer. While there are a variety of reasons for that (like changes to the data involved), a release of a new version is one of the more likely. As for investigating, what exactly are you suggesting that the OP do then? Either the bug is indeed no longer there, in which case you mark it resolved or it's still there and someone has to investigate the cause, after the user has reported that it's still there.
Dec
1
comment How to deal with a bug which seems to have fixed itself?
Frankly, while I appreciate that a Programmers mod wanted this question migrated here, I'd recommend closing it as a duplicate/unclear until the OP actually signs on here and can flesh out the question.
Dec
1
comment How to deal with a bug which seems to have fixed itself?
@Frisbee If I had to investigate every phantom bug ever reported by a user my brain would have liquified years ago. Unless you're dealing with a reliable user and a critical bug in a critical application you generally shouldn't waste time on an unconfirmed bug. The critical phrase in the question is "no longer" reproducible.
Dec
1
comment How to deal with a bug which seems to have fixed itself?
This just calls for a pretty standard boilerplate response: "Dear [user], The issue with X that you reported on the Yth seems to have been resolved with the latest release of Z. Please mark the issue as resolved if that is indeed the case. If not please send this back to me with details on how you encountered it."
Aug
27
revised Explaining new or uncommon syntax in comments
added 15 characters in body
Aug
27
comment Explaining new or uncommon syntax in comments
@SteveJessop Poor choice of words I suppose. I added that disclaimer to prevent single-line answers amounting to "write code that doesn't need comments" without further clarification. Another summary of my question could be "Should I comment code that doesn't need comments for up-to-date developers?". I'll reword that phrase (it was referring to the linked answer's conclusion: "Explaining yourself is good, not needing to do so is better.").
Aug
27
awarded  Yearling
Aug
27
comment Explaining new or uncommon syntax in comments
Excellent points and something I'll have to consider. Not sure why this gained a downvote, +1.
Aug
26
awarded  Popular Question
Aug
26
awarded  Nice Question
Aug
26
comment Explaining new or uncommon syntax in comments
@gnat Tried to clarify the differences.
Aug
26
revised Explaining new or uncommon syntax in comments
explained differences with suggested dupe
Aug
26
revised Explaining new or uncommon syntax in comments
added 183 characters in body
Aug
26
comment Explaining new or uncommon syntax in comments
I see that I should have been clearer in my original post, this is indeed what I'm doing, for example "This logic uses the new GROUP BY logic from ABAP release 7.40 SP08".
Aug
26
revised Explaining new or uncommon syntax in comments
added 221 characters in body
Aug
26
comment Explaining new or uncommon syntax in comments
Dont' worry @cxw , I expected to get that reaction and I understand where you're coming from. I've updated my question to explain the benefits of using the new syntax as they're generally quite significant.
Aug
26
revised Explaining new or uncommon syntax in comments
added 1064 characters in body