936 reputation
814
bio website not-implemented.com
location
age
visits member for 4 years, 3 months
seen Dec 4 at 19:15

Jul
16
comment Working as a sole developer: getting code looked over
@david: I understand now, makes sense
Jul
16
comment Working as a sole developer: getting code looked over
@david: you mentioned looking back at code after a fixed amount of time, even if there is no need to at the moment. You didn't initially say to look back at the code only when you have to do so in order to add new features.. So if - according to what you said - you have to eventually look back at all old code, why not do so in a moment that's relevant instead of after a fixed time period?
Jul
15
comment Working as a sole developer: getting code looked over
In theory this could work, in practice there is NO WAY IN HELL he's going to go look back at code he wrote 2 weeks ago if it works. Nor should he, probably.. If it works going back to spend time on it for the sole reason of making it "prettier" is a waste of time, it should be done when and if it is touched again.
Jul
13
answered Too much version control and bug tracking overhead per change?
Jun
15
comment What's the deal with programming languages as strict job requirements?
@kevin: it's clear that you don't know what you're talking about. C++ is one of the most complex languages with more quirks than you can even imagine. There is no way anyone can learn it in 8 hours (a day's work!!!). You can't even learn languages like PHP in that time.
Jun
14
comment What's the business in developing a programming language?
It's like making money playing quake or world of warcraft professionally though.. There are a few people who do and millions who don't. Considering the enormous time investment and the close to 0 chances it's not really a viable way to make money
May
25
comment Stuff every programmer needs while working
@Pierre: out of curiosity, what language? I program in C++.
May
25
comment Stuff every programmer needs while working
@Pierre: Building a project is not disk insensitive. Maybe you noticed that your CPU spikes at 100%; this means it's CPU intensive.
May
25
comment How to apologize when you have broken the nightly build
+1 but for a slightly different reason.. If one of my developers does something stupid I don't want them to apologize, it means nothing, I just don't want them to do it again. Now, I wouldn't consider breaking a build "something stupid", in fact I don't think it's a big deal, but every company is different and if they consider it a big deal then do not apologize. Just don't do it again.
May
10
comment isn't number localization just unnecessary?
I hate localization and even if I'm italian the 1.234 format confuses the hell out of me (I assume it's 1,234, ie, 1 thousand etc).. Same with dates, if it's 04/05/2010 I have no idea whatsoever what it might be
Mar
26
awarded  Scholar
Mar
26
accepted Can I sell apps on the apple's US app store market?
Mar
26
revised Can I sell apps on the apple's US app store market?
edited title
Mar
26
asked Can I sell apps on the apple's US app store market?
Mar
9
comment Not getting paid for hours you've worked?
+1, Finally someone who likes working overtime!
Mar
1
awarded  Nice Answer
Feb
28
answered How big of a team do you need to benefit from bug tracking software?
Feb
8
comment Do I deserve a promotion/higher salary?
you can't be passive with this sort of things.. If you want one, ask for one, aggressively. If you are willing to quit over it, make it clear to your company that you are.
Jan
9
comment What can I do when the interviewer doesn't know the answer to his/her own question?
For what it's worth I didn't know that they could myself, and I would call me a "C++ expert". I even asked this very same question on some interviews I did a month ago, and no one - including me - knew I guess. Did you try to give the interviewer an example, even if they acted skeptical? If yes and they wouldn't listen then yes it's better if you don't work there, but if you didn't provide an example then sorry but it's your fault
Dec
28
comment Should I point out spelling/grammar related mistakes in someone's code?
@Rei: whether English is their native language or not should be irrelevant in a professional environment; if it's not then too bad for them but it's no excuse, they should be held to the same standards.