How does one live with themself
-
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
-
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
Mycroft Holmes wrote:
would think the various testing phases should get 99% of "not working" code!
You are correct, and it should. It is a combination of careless coding and careless testing by certain teams in our company. I am sure these guys know how to code well enough. Burnt out and lost motivation, maybe, who knows.
-
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:
with code that is so poorly written, it doesn't work properly
There are times that code is really poorly written but it works, as long as you don't touch it again. These are the ones that are mostly caused by time constraints IMO. Although some people do write retarded code no matter what, because they are, let's say, not born for coding. I get aggravated a lot because of that.
To alcohol! The cause of, and solution to, all of life's problems - Homer Simpson ---- Our heads are round so our thoughts can change direction - Francis Picabia
-
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:
Ask rather how one will react to the news that he has been made a plural.
This fear of he, him, and his as the standard generic singular pronouns has gone far enough. Men, find your balls. Women, get over yourselves.
(This message is programming you in ways you cannot detect. Be afraid.)
-
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:
Poorly written code that works, and keeps on working, triumphs over elegant code that hasn't been deployed or doesn't work. Also, having the 'OK' button in the right spot means more to users than the architecture of your solution. I've based my 12 year career on putting out crap code that works.
-
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
Exactly!
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
Been there, wont ever go back. If I am the only developer that can provide the solution, my answer quickly become: - Under normal time constraints. 3-4 days. - If you rush this, I will "try" with no promises, but the COST will be 8 days. If you are okay with paying for 8 days of my time to do it wrong, and then to fix it, well of course I will do that. If there is another option for them to develop it with, I ALWAYS let them choose that one, when they want such rubbish.
-
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
-
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:
-
Ask rather how one will react to the news that he has been made a plural.
This fear of he, him, and his as the standard generic singular pronouns has gone far enough. Men, find your balls. Women, get over yourselves.
(This message is programming you in ways you cannot detect. Be afraid.)
-
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'll see your scenario and raise you.. Biz Mgr: The Client says that we have to have the system do this. Dev: Well it's not really how the system is designed work.. Who said we could do that and what are the requirements? Biz Mgr: I'm not sure but this is a deal breaker! Dev's Boss: Ok, well lets hash out the requirements so we can scope it out and get it into the backlog. Biz Mgr: Great! Wait, what's a Backlog? We need this right away, Client rolls out Q1. Dev: WHAT!? It's almost November! So we have to redesign a production system to function in a way it was never designed, for 1 client who can't even give us detailed requirements of how it exactly should work...and we have to have it done yesterday!? Biz Mgr: Sorry, 6 weeks should be plenty though right? It's not like this a complete rewrite. Dev: :wtf: Says to himself "Wow Biz Mgr and now an architect too?" Having witnessed the recurring symptoms of 'clientitus' throughout my career, It has become much easier for me to "live with myself". Gives me an excuse to use more colorful comments in my code. :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:
The universe has provided these idiots to serve you: thanks to them, you will never be unemployed. I do feel, however, that the universe should provide a type of "buy four, get one free" policy - i.e. after having cleaned up the mess that four of them have made, you should be allowed legally to murder the fifth one. It's only sanitary, after all...
-
I'll see your scenario and raise you.. Biz Mgr: The Client says that we have to have the system do this. Dev: Well it's not really how the system is designed work.. Who said we could do that and what are the requirements? Biz Mgr: I'm not sure but this is a deal breaker! Dev's Boss: Ok, well lets hash out the requirements so we can scope it out and get it into the backlog. Biz Mgr: Great! Wait, what's a Backlog? We need this right away, Client rolls out Q1. Dev: WHAT!? It's almost November! So we have to redesign a production system to function in a way it was never designed, for 1 client who can't even give us detailed requirements of how it exactly should work...and we have to have it done yesterday!? Biz Mgr: Sorry, 6 weeks should be plenty though right? It's not like this a complete rewrite. Dev: :wtf: Says to himself "Wow Biz Mgr and now an architect too?" Having witnessed the recurring symptoms of 'clientitus' throughout my career, It has become much easier for me to "live with myself". Gives me an excuse to use more colorful comments in my code. :laugh:
Give an excuse to use non tested technology/methods/procedures in the field, to use dangerous practices, everything will crumb down sometime, why care? all those software are just my experimentation lab, I don't care anymore if it will crash in two days. "You have to be professional" fuck this, they aren't being professional by accepting this shit from clients, that's why this is crazy work, everything is utter shit because of this endemic behavior of the managers, they always take deadlines out of their magic hats.
-
Been there, wont ever go back. If I am the only developer that can provide the solution, my answer quickly become: - Under normal time constraints. 3-4 days. - If you rush this, I will "try" with no promises, but the COST will be 8 days. If you are okay with paying for 8 days of my time to do it wrong, and then to fix it, well of course I will do that. If there is another option for them to develop it with, I ALWAYS let them choose that one, when they want such rubbish.
Yeah - that's fine when you're 'the boss' and can decide what to do. Problem is the majority of developers are in the 'do what the boss says' role without the options. I recently had the situation that, with major issues in the codebase requiring fixing (35 second response times, frequent crashes, simple failure of functionality) we dropped everything and started a sprint - to change the fonts and footers on all the reports so they all look exactly the same The main reason they weren't all the same was because the data required wouldn't fit on some of the reports otherwise. Now, the developers could have stood their ground -- but they're being paid to develop and offer advice - so, advice offered, the choice is do it or move it. Of course, teh ling term result of this sort of thing continuing is redundancy anyway ...
PooperPig - Coming Soon
-
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 transfer the blame on the clients who haphazardly request new features who contradict each other and are meant to be delivered yesterday. :)
CEO at: - Rafaga Systems - Para Facturas - Modern Components for the moment...
