Programming question
-
If you are writing an app that no one will see (other devs), do you still follow best practices i.e. creating classes, data access layers, blah, blah, blah? or, do you say f'it and write the app like a retard? i.e. putting all 5-8K lines of code in one form class and calling it a day. I am being asked by a senior dev to do something that I feel is fundamentally wrong as a programmer but he is the "senior" dev and thus must be obeyed.
Just along for the ride. "the meat from that butcher is just the dogs danglies, absolutely amazing cuts of beef." - DaveAuld (2011)
"No, that is just the earthly manifestation of the Great God Retardon." - Nagy Vilmos (2011)My philosophy is to write all my code as though it is going to be put up on a screen with all my peers there to see it. It keeps me motivated to mind my p's and q's. Also, remember that given time, you may also become a senior developer and the code you write on the way up may find its way into the hands of the next more junior guy to come along. Write code that you would stand behind, or at minimum, make sure the comments are very, very clear as to why you are creating the thing in a crappy way.
I wasn't, now I am, then I won't be anymore.
-
For God's sake, do it right! I have seen too many /quick jobs/ that evolved from helping one person to becoming used company wide. Where the code is shyte, the extensibility is greatly reduced and at some point the whole shedangs need to be redone. [edit] Looks like I can not spell today.
Panic, Chaos, Destruction. My work here is done. Drink. Get drunk. Fall over - P O'H OK, I will win to day or my name isn't Ethel Crudacre! - DD Ethel Crudacre I cannot live by bread alone. Bacon and ketchup are needed as well. - Trollslayer Have a bit more patience with newbies. Of course some of them act dumb - they're often *students*, for heaven's sake - Terry Pratchett
I've seen this to. I currently support a couple "proof of concept" applications that are in live production environments.
I wasn't, now I am, then I won't be anymore.
-
My philosophy is to write all my code as though it is going to be put up on a screen with all my peers there to see it. It keeps me motivated to mind my p's and q's. Also, remember that given time, you may also become a senior developer and the code you write on the way up may find its way into the hands of the next more junior guy to come along. Write code that you would stand behind, or at minimum, make sure the comments are very, very clear as to why you are creating the thing in a crappy way.
I wasn't, now I am, then I won't be anymore.
Marcus Kramer wrote:
My philosophy is to write all my code as though it is going to be put up on a screen with all my peers there to see it. It keeps me motivated to mind my p's and q's.
A very good philosophy at that. I agree.
Marcus Kramer wrote:
Also, remember that given time, you may also become a senior developer and the code you write on the way up may find its way into the hands of the next more junior guy to come along. Write code that you would stand behind, or at minimum, make sure the comments are very, very clear as to why you are creating the thing in a crappy way.
:thumbsup:
Just along for the ride. "the meat from that butcher is just the dogs danglies, absolutely amazing cuts of beef." - DaveAuld (2011)
"No, that is just the earthly manifestation of the Great God Retardon." - Nagy Vilmos (2011) "It is the celestial scrotum of good luck!" - Nagy Vilmos (2011) -
Tell him you're getting a woody, and he'll leave you alone. Trust me on this. EDIT ============== 1-voted AGAIN! Geeze! And to think this isn't even the funniest thing I've posted today... :)
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass." - Dale Earnhardt, 1997Do you think telling him you have a nine-iron could have the same effect ? best, Bill
"For no man lives in the external truth among salts and acids, but in the warm, phantasmagoric chamber of his brain, with the painted windows and the storied wall." Robert Louis Stevenson
-
Tell him you're getting a woody, and he'll leave you alone. Trust me on this. EDIT ============== 1-voted AGAIN! Geeze! And to think this isn't even the funniest thing I've posted today... :)
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass." - Dale Earnhardt, 1997John Simmons / outlaw programmer wrote:
the funniest thing I've posted today
now that's a matter of opinion... Just thought I'd notify you of my intention of down-voting everything you post from now on - as your responses to 1-votes are far more entertaining than your normal posts :) And if you'd told my previous project manager you were getting a woody, he would more likely ask you to attend a private scrum meeting than be put off..
MVVM# - See how I did MVVM my way ___________________________________________ Man, you're a god. - walterhevedeich 26/05/2011 .\\axxx (That's an 'M')
-
Erudite_Eric wrote:
or die
Until six months later when you try and edit the code. :)
See, this is where I have a problem. Loads of people say classes classes classes when talking about quality, easy to read code, yet I have ssen worse spaghetti code using classes than with procedural code.
============================== Nothing to say.
-
For God's sake, do it right! I have seen too many /quick jobs/ that evolved from helping one person to becoming used company wide. Where the code is shyte, the extensibility is greatly reduced and at some point the whole shedangs need to be redone. [edit] Looks like I can not spell today.
Panic, Chaos, Destruction. My work here is done. Drink. Get drunk. Fall over - P O'H OK, I will win to day or my name isn't Ethel Crudacre! - DD Ethel Crudacre I cannot live by bread alone. Bacon and ketchup are needed as well. - Trollslayer Have a bit more patience with newbies. Of course some of them act dumb - they're often *students*, for heaven's sake - Terry Pratchett
I agree that many projects go from being used by one person to being used company wide. But many more don't. If what you care most is to have your program up and running ASAP, go for it. No need to setup proper security or error handling or input checking. If it turns out that the program is valuable enough to be extended and maintained, rewrite it from scratch right away. I usually write neat code, no matter what, because it always takes way more time to decide what your program is going to do, than it does to write the actual code. I care more about the code being *reusable* and understandable when I come back to it in one month, than about objects, naming conventions, magic numbers, and having the names of servers written in the code. I don't mind having one class with 4 methods, if I deem the code clear and concise.
"Computer Science is no more about computers than astronomy is about telescopes." - Edsger Dijkstra
-
See, this is where I have a problem. Loads of people say classes classes classes when talking about quality, easy to read code, yet I have ssen worse spaghetti code using classes than with procedural code.
============================== Nothing to say.
Had a guy who loved classes so much everything was a class. We canned his code when he was asked to make a change and he could not decipher his "classes". Every variable had a class! By the way there were no comments.
-
If you are writing an app that no one will see (other devs), do you still follow best practices i.e. creating classes, data access layers, blah, blah, blah? or, do you say f'it and write the app like a retard? i.e. putting all 5-8K lines of code in one form class and calling it a day. I am being asked by a senior dev to do something that I feel is fundamentally wrong as a programmer but he is the "senior" dev and thus must be obeyed.
Just along for the ride. "the meat from that butcher is just the dogs danglies, absolutely amazing cuts of beef." - DaveAuld (2011)
"No, that is just the earthly manifestation of the Great God Retardon." - Nagy Vilmos (2011)Is there a possibility that you'll be asked to maintain that app at some future time?
Programs have a way of confounding our expectations for "how long they'll live." I wrote what I thought was a throwaway in 1995 that's still in use today -- and I still get calls to extend it. By contrast, I put three years of my life into a microprogram that was obsoleted within four months and never used again.
If you can't be sure, err on the side of caution. Make it easy for you to understand and maintain, no matter how much time should pass.
(This message is programming you in ways you cannot detect. Be afraid.)
-
Is there a possibility that you'll be asked to maintain that app at some future time?
Programs have a way of confounding our expectations for "how long they'll live." I wrote what I thought was a throwaway in 1995 that's still in use today -- and I still get calls to extend it. By contrast, I put three years of my life into a microprogram that was obsoleted within four months and never used again.
If you can't be sure, err on the side of caution. Make it easy for you to understand and maintain, no matter how much time should pass.
(This message is programming you in ways you cannot detect. Be afraid.)
Fran Porretto wrote:
Is there a possibility that you'll be asked to maintain that app at some future time?
Absolutely. This is why I am concerned.
Just along for the ride. "the meat from that butcher is just the dogs danglies, absolutely amazing cuts of beef." - DaveAuld (2011)
"No, that is just the earthly manifestation of the Great God Retardon." - Nagy Vilmos (2011) "It is the celestial scrotum of good luck!" - Nagy Vilmos (2011) -
If you are writing an app that no one will see (other devs), do you still follow best practices i.e. creating classes, data access layers, blah, blah, blah? or, do you say f'it and write the app like a retard? i.e. putting all 5-8K lines of code in one form class and calling it a day. I am being asked by a senior dev to do something that I feel is fundamentally wrong as a programmer but he is the "senior" dev and thus must be obeyed.
Just along for the ride. "the meat from that butcher is just the dogs danglies, absolutely amazing cuts of beef." - DaveAuld (2011)
"No, that is just the earthly manifestation of the Great God Retardon." - Nagy Vilmos (2011)They are called best practices for a reason. They are not made for other developers, they are made for every developer, including yourself. The initial overhead might suck, but it surely pays off on the long run. You don't want to have your own magic code come after your ass later on. And there's no such thing no one else will see. Eventually someone will see it, you never know when a project gets more people involved, or when it switches hands. Be kind to the developer that comes to support your application when you're gone. He might even give you a call to say thank you, instead of "what the hell you've done here?"
"To alcohol! The cause of, and solution to, all of life's problems" - Homer Simpson
-
I've seen this to. I currently support a couple "proof of concept" applications that are in live production environments.
I wasn't, now I am, then I won't be anymore.
Marcus Kramer wrote:
I've seen this to. I currently support a couple...
Are we talking about code or Henry's hairy balls here? :omg: Danny
-
If you are writing an app that no one will see (other devs), do you still follow best practices i.e. creating classes, data access layers, blah, blah, blah? or, do you say f'it and write the app like a retard? i.e. putting all 5-8K lines of code in one form class and calling it a day. I am being asked by a senior dev to do something that I feel is fundamentally wrong as a programmer but he is the "senior" dev and thus must be obeyed.
Just along for the ride. "the meat from that butcher is just the dogs danglies, absolutely amazing cuts of beef." - DaveAuld (2011)
"No, that is just the earthly manifestation of the Great God Retardon." - Nagy Vilmos (2011)If it's throw-away code, for example, something I am just trying out, then, no, I don't always follow best practices. But, other than that, yes, I always do. Bad code will haunt you at night... :~
The world is going to laugh at you anyway, might as well crack the 1st joke! My code has no bugs, it runs exactly as it was written.
-
Nagy Vilmos wrote:
becoming used company wide
Or worse. I was asked to do a rush demo about 25 years ago - work through the weekend, hurl it together job for demo on Monday. "OK," says I "provided everyone understands it's a demo only, and we will need months to get the full thing working properly." "Yes, yes - just do it" comes the reply. Take the computer home, coffee, pizza, hack hack. Monday the demo is up and limping. What happens? The sales guys sold it and we had to maintain that POS for three years...
Ideological Purity is no substitute for being able to stick your thumb down a pipe to stop the water
-
From 25 years ago? Probably dead of liver failure, given the amount "good" salesmen tend to drink...
Ideological Purity is no substitute for being able to stick your thumb down a pipe to stop the water
-
If you are writing an app that no one will see (other devs), do you still follow best practices i.e. creating classes, data access layers, blah, blah, blah? or, do you say f'it and write the app like a retard? i.e. putting all 5-8K lines of code in one form class and calling it a day. I am being asked by a senior dev to do something that I feel is fundamentally wrong as a programmer but he is the "senior" dev and thus must be obeyed.
Just along for the ride. "the meat from that butcher is just the dogs danglies, absolutely amazing cuts of beef." - DaveAuld (2011)
"No, that is just the earthly manifestation of the Great God Retardon." - Nagy Vilmos (2011)We don't follow good coding practices to show others! We follow those for our own sake. He is probably a Senior dev by accident. You may write such crappy code if you are sure you will never ever have to maintain any part of it. But remember God is watching u. :)
-
It is the celestial scrotum of good luck!
Panic, Chaos, Destruction. My work here is done. Drink. Get drunk. Fall over - P O'H OK, I will win to day or my name isn't Ethel Crudacre! - DD Ethel Crudacre I cannot live by bread alone. Bacon and ketchup are needed as well. - Trollslayer Have a bit more patience with newbies. Of course some of them act dumb - they're often *students*, for heaven's sake - Terry Pratchett
Rotflmfao
-
They are called best practices for a reason. They are not made for other developers, they are made for every developer, including yourself. The initial overhead might suck, but it surely pays off on the long run. You don't want to have your own magic code come after your ass later on. And there's no such thing no one else will see. Eventually someone will see it, you never know when a project gets more people involved, or when it switches hands. Be kind to the developer that comes to support your application when you're gone. He might even give you a call to say thank you, instead of "what the hell you've done here?"
"To alcohol! The cause of, and solution to, all of life's problems" - Homer Simpson
well said and very true.
Just along for the ride. "the meat from that butcher is just the dogs danglies, absolutely amazing cuts of beef." - DaveAuld (2011)
"No, that is just the earthly manifestation of the Great God Retardon." - Nagy Vilmos (2011) "It is the celestial scrotum of good luck!" - Nagy Vilmos (2011) -
If you are writing an app that no one will see (other devs), do you still follow best practices i.e. creating classes, data access layers, blah, blah, blah? or, do you say f'it and write the app like a retard? i.e. putting all 5-8K lines of code in one form class and calling it a day. I am being asked by a senior dev to do something that I feel is fundamentally wrong as a programmer but he is the "senior" dev and thus must be obeyed.
Just along for the ride. "the meat from that butcher is just the dogs danglies, absolutely amazing cuts of beef." - DaveAuld (2011)
"No, that is just the earthly manifestation of the Great God Retardon." - Nagy Vilmos (2011)Always do it right. If the "senior" says you need to do it wrong... Make sure it is known by other people that he ordered you to do it wrong. And protest heavily. That's what I would do.
-
If you are writing an app that no one will see (other devs), do you still follow best practices i.e. creating classes, data access layers, blah, blah, blah? or, do you say f'it and write the app like a retard? i.e. putting all 5-8K lines of code in one form class and calling it a day. I am being asked by a senior dev to do something that I feel is fundamentally wrong as a programmer but he is the "senior" dev and thus must be obeyed.
Just along for the ride. "the meat from that butcher is just the dogs danglies, absolutely amazing cuts of beef." - DaveAuld (2011)
"No, that is just the earthly manifestation of the Great God Retardon." - Nagy Vilmos (2011)
