geronimo, Great comment,I work with guys who bitch all day. About the job, the work, the company changes, the 401k, health care, the job, work, company changes, 401k, health care... repeat and repeat... then they have lunch. After lunch, they bitch about the job, the work, the company changes, the 401k, health care, the job, work, company changes, 401k, health care... repeat and repeat, I tell them that there are other companies, and other jobs inside of the same company, they laugh and say they don't want to leave and then proceed to bitch about the list above.
@GrumpyrainOO does *not* help with security. If you are cutting and pasting code, you're likely to do that in any language. Languages like java almost encourage such things (aspectj helps a lot here).
1. Communicate! Don't waste time when you get stuck or have questions. Ask for help right away. 2. Keep it simple stupid. There is no one to impress but yourself.3. Conceptual Integrity. Look it up, and remember it always.4. When talking to customers, remember that YOU are the professional. You are supposed to have an opinion.
3. Learn to say noProbably the best advice on the article. Within the first two months of getting my first software developer gig I nearly quit the whole thing simply because I was too eager to please and nearly bunt myself out.
8. It all comes down to working softwareBut what if it works, but the code is ugly ? That's the real question.To refactor or "If It's Not Broken, Don't Fix It". There is usually no time allocating specifically to refactoring, if you are doing it you are doing it at your own risk. You may save time on the later code maintenance or modification, but may be not...
That's a valid concern.I really do think we can architect/plan/organize our applications better, I just feel that for most applications, oo is just of no value.I don't have an answer or THE answer...my gut keeps telling me this is the wrong approach...If it works for you, go ahead and use it. But please don't make me out to be a jerk if i don't support what you support.Actually I found this article rather well written, and well thought out.I really do want to be a better programmer, just not always some one to ask questions, at times, it feels there are no real support for programmers, especially web-based ones. I know there are user groups, but unless you follow a certain way of doing things, that are trendy, which i don't follow because trendy does not equal correct.I guess my few words of wisdom are.1. Plan well2. long term vs short term always pays offIf you make more monkey code, when it honestly just needs to be redone, your only making it harder on yourself by not maintaining the code/applications as you work on them.Care about the quality of the code on the outside and inside, this is your craft, this is what people look at.
Same here. I'm about to start on a software engineering career and I take advice openly, but only use the pieces of advice I like, and I like almost all of these.
nubi78Mar 23, 2007
geronimo, Great comment,I work with guys who bitch all day. About the job, the work, the company changes, the 401k, health care, the job, work, company changes, 401k, health care... repeat and repeat... then they have lunch. After lunch, they bitch about the job, the work, the company changes, the 401k, health care, the job, work, company changes, 401k, health care... repeat and repeat, I tell them that there are other companies, and other jobs inside of the same company, they laugh and say they don't want to leave and then proceed to bitch about the list above.
d03boy_Mar 23, 2007
Let me guess, you know the singleton pattern?
aznmikex215Mar 23, 2007
oops.
dlsspyMar 23, 2007
@GrumpyrainOO does *not* help with security. If you are cutting and pasting code, you're likely to do that in any language. Languages like java almost encourage such things (aspectj helps a lot here).
abjorck9Mar 23, 2007
1. Communicate! Don't waste time when you get stuck or have questions. Ask for help right away. 2. Keep it simple stupid. There is no one to impress but yourself.3. Conceptual Integrity. Look it up, and remember it always.4. When talking to customers, remember that YOU are the professional. You are supposed to have an opinion.
ham__Mar 23, 2007
3. Learn to say noProbably the best advice on the article. Within the first two months of getting my first software developer gig I nearly quit the whole thing simply because I was too eager to please and nearly bunt myself out.
strdMar 23, 2007
8. It all comes down to working softwareBut what if it works, but the code is ugly ? That's the real question.To refactor or "If It's Not Broken, Don't Fix It". There is usually no time allocating specifically to refactoring, if you are doing it you are doing it at your own risk. You may save time on the later code maintenance or modification, but may be not...
crosenblumMar 23, 2007
That's a valid concern.I really do think we can architect/plan/organize our applications better, I just feel that for most applications, oo is just of no value.I don't have an answer or THE answer...my gut keeps telling me this is the wrong approach...If it works for you, go ahead and use it. But please don't make me out to be a jerk if i don't support what you support.Actually I found this article rather well written, and well thought out.I really do want to be a better programmer, just not always some one to ask questions, at times, it feels there are no real support for programmers, especially web-based ones. I know there are user groups, but unless you follow a certain way of doing things, that are trendy, which i don't follow because trendy does not equal correct.I guess my few words of wisdom are.1. Plan well2. long term vs short term always pays offIf you make more monkey code, when it honestly just needs to be redone, your only making it harder on yourself by not maintaining the code/applications as you work on them.Care about the quality of the code on the outside and inside, this is your craft, this is what people look at.
fuzzynyankoMar 23, 2007
Same here. I'm about to start on a software engineering career and I take advice openly, but only use the pieces of advice I like, and I like almost all of these.
domesterzMar 23, 2007
OO is not easy to design but it easys to develop after design is finish !
sarahmaddelsonMay 11, 2007
Thanx a lot for the info. That's true, I confirm.