How does one live with themself
-
Yeah, what I've learned is, even though I consider myself one of the non-retarded devs, there are times I write retarded code. Like when under time constraints, etc.
Jeremy Falcon
Jeremy Falcon wrote:
there are times I write retarded code. Like when under time constraints,
You can disagree with me here, but there is no excuse to write retarded code. Where I work, you can get into A LOT of trouble you submit bad/not working code into production. My grievance goes beyond aesthetics or "code style", but rather with code that is so poorly written, it doesn't work properly.
-
knowing that their code smells worse then dinosaur farts?! Honestly, I could not advertise myself as a competent software engineer, if I knowingly produced such excrement. and yet these "senior" engineers are still employed. :wtf: :omg:
-
Jeremy Falcon wrote:
there are times I write retarded code. Like when under time constraints,
You can disagree with me here, but there is no excuse to write retarded code. Where I work, you can get into A LOT of trouble you submit bad/not working code into production. My grievance goes beyond aesthetics or "code style", but rather with code that is so poorly written, it doesn't work properly.
Slacker007 wrote:
You can disagree with me here, but there is no excuse to write retarded code. Where I work, you can get into A LOT of trouble you submit bad/not working code into production.
When I say retarded, I don't mean completely asinine. I mean not "perfect". There are times it happens. Is it great? No. I do like it? No. Is that just the world works? Yup. If you're thinking something along the lines of, let's just say, not having a single point of reference, not using constants, not being consistent with formatting, etc. then I totally agree with you. There's never an excuse for that.
Jeremy Falcon
-
Slacker007 wrote:
yet these "senior" engineers are still employed.
And posting in Q&A. :laugh:
Richard MacCutchan wrote:
And posting in Q&A. :laugh:
Laughed so hard at this, my soda went out my nose. Ah, the burn. :thumbsup:
-
Slacker007 wrote:
yet these "senior" engineers are still employed.
And posting in Q&A. :laugh:
And posting "Articles" here as well... :sigh:
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
-
knowing that their code smells worse then dinosaur farts?! Honestly, I could not advertise myself as a competent software engineer, if I knowingly produced such excrement. and yet these "senior" engineers are still employed. :wtf: :omg:
;P
-
knowing that their code smells worse then dinosaur farts?! Honestly, I could not advertise myself as a competent software engineer, if I knowingly produced such excrement. and yet these "senior" engineers are still employed. :wtf: :omg:
That's why you need a good peer-review system. For one thing, it encourages people to make a little more effort to get it right first time, because they realise that trying to save time will cost a lot more. For another, when everyone is used to others finding gaffes in their work, and critiquing it honestly and openly, it gets rid of any ego problems.
I wanna be a eunuchs developer! Pass me a bread knife!
-
And posting "Articles" here as well... :sigh:
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
And steal your profile picture :laugh:
-
They live by themselves in themselves for themselves, ins't it obvious? I think therefor I am sort of thing I guess :laugh:
-
knowing that their code smells worse then dinosaur farts?! Honestly, I could not advertise myself as a competent software engineer, if I knowingly produced such excrement. and yet these "senior" engineers are still employed. :wtf: :omg:
My experience is, that people who are writing bad code have also bad habits. So I often critize bad code to hit these guys. :cool: God bless we only a small amount of this slack. (but I know one - one of my collegues)
Press F1 for help or google it. Greetings from Germany
-
That's why you need a good peer-review system. For one thing, it encourages people to make a little more effort to get it right first time, because they realise that trying to save time will cost a lot more. For another, when everyone is used to others finding gaffes in their work, and critiquing it honestly and openly, it gets rid of any ego problems.
I wanna be a eunuchs developer! Pass me a bread knife!
Mark_Wallace wrote:
when everyone is used to others finding gaffes in their work, and critiquing it honestly and openly, it gets rid of any ego problems.
Because it leads to homicide and suicide and, thus, removes the cause of the ego problems ?
« There is only one difference between a madman and me. The madman thinks he is sane. I know I am mad. » Salvador Dali
-
knowing that their code smells worse then dinosaur farts?! Honestly, I could not advertise myself as a competent software engineer, if I knowingly produced such excrement. and yet these "senior" engineers are still employed. :wtf: :omg:
Hey, you're not the boss of me. So Ha Ha my code smells like dinosaur's farts. :-D
-
knowing that their code smells worse then dinosaur farts?! Honestly, I could not advertise myself as a competent software engineer, if I knowingly produced such excrement. and yet these "senior" engineers are still employed. :wtf: :omg:
-
And posting "Articles" here as well... :sigh:
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
-
Brainblaze, I think...;)
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
-
knowing that their code smells worse then dinosaur farts?! Honestly, I could not advertise myself as a competent software engineer, if I knowingly produced such excrement. and yet these "senior" engineers are still employed. :wtf: :omg:
I know exactly how you feel, same here! :omg: :((
My programming get away... The Blog... DirectX for WinRT/C# since 2013! Taking over the world since 1371!
-
Yeah, what I've learned is, even though I consider myself one of the non-retarded devs, there are times I write retarded code. Like when under time constraints, etc.
Jeremy Falcon
Client: We need this and we need it now. Dev: That will take 3 or 4 days to do Client: We need it today or you don't get paid! Dev: No way - only way I could do that would be to do a real quick and dirty - bypass the ORM , directly access the Db via ... Client: lala lalalla lalala Dev's Boss: The Dev said he could do it! nSo Doit Do it DO IT! Dev: BUt it's just a quick fix, right, we'll re-engineer it straight away, right? In the next sprint? Dev's Boss: Sure. :rubs hands together: Dev: I hate my life!
PooperPig - Coming Soon
-
Jeremy Falcon wrote:
there are times I write retarded code. Like when under time constraints,
You can disagree with me here, but there is no excuse to write retarded code. Where I work, you can get into A LOT of trouble you submit bad/not working code into production. My grievance goes beyond aesthetics or "code style", but rather with code that is so poorly written, it doesn't work properly.
Slacker007 wrote:
submit bad/not working code into production.
I would think the various testing phases should get 99% of "not working" code! We do most our specification in UAT, get an idea what the user wants to achieve, build a POC, send it to UAT and actually get something from the users that makes sense.
Never underestimate the power of human stupidity RAH
-
Mark_Wallace wrote:
when everyone is used to others finding gaffes in their work, and critiquing it honestly and openly, it gets rid of any ego problems.
Because it leads to homicide and suicide and, thus, removes the cause of the ego problems ?
« There is only one difference between a madman and me. The madman thinks he is sane. I know I am mad. » Salvador Dali
There have been times I've considered homicide as a method for handling this, yes.
I wanna be a eunuchs developer! Pass me a bread knife!
-
Client: We need this and we need it now. Dev: That will take 3 or 4 days to do Client: We need it today or you don't get paid! Dev: No way - only way I could do that would be to do a real quick and dirty - bypass the ORM , directly access the Db via ... Client: lala lalalla lalala Dev's Boss: The Dev said he could do it! nSo Doit Do it DO IT! Dev: BUt it's just a quick fix, right, we'll re-engineer it straight away, right? In the next sprint? Dev's Boss: Sure. :rubs hands together: Dev: I hate my life!
PooperPig - Coming Soon
I wrote an article along the very same lines on the subject of technical debt, which is what your point refers to. There's nothing intrinsically wrong with taking a conscious shortcut if there is a justifiable reason to do so e.g. there may be a bonus for hitting a deadline or compensation if you don't. But as long as you repay that shortcut then there's not a problem. The problem is that you never get the time to go back and address the shortcut, as you are already onto the next shortcut etc etc. [^]
"There are two ways of constructing a software design: One way is to make it so simple that there are obviously no deficiencies, and the other way is to make it so complicated that there are no obvious deficiencies. The first method is far more difficult." - C.A.R. Hoare
