Am I a bad programmer?
-
So, the company I work for is pretty small, only about 8 developers. The biggest (web) app is very complicated and is chalk full of errors. To compound the issue, there is absolutly ZERO documentation in the code / database. The DB also has no Foriegn Key contraints and is only marginally normalized. I don't work on the app that much, so I'm not as familiar as everyone else is with it. Whenever a problem comes up, they can jump right to the problem, but it sometimes takes me hours.... The question is "Am I a bad programmer, or are they?" Most of us were drilled with the "document your code" as we were learning either by instructors or books, but no one here does that (except me).:mad: As far as new development goes, IMHO I think I am *better* because I grasp the concepts of normalization, documentation, OOD. All new concepts to them. I had to explain normalization and pursuede them to let me do it on some new tables I added!:mad: And this is no hole-in-the-wall company either, they have some BIG clients. Well, thanks for letting me beef!
-
So, the company I work for is pretty small, only about 8 developers. The biggest (web) app is very complicated and is chalk full of errors. To compound the issue, there is absolutly ZERO documentation in the code / database. The DB also has no Foriegn Key contraints and is only marginally normalized. I don't work on the app that much, so I'm not as familiar as everyone else is with it. Whenever a problem comes up, they can jump right to the problem, but it sometimes takes me hours.... The question is "Am I a bad programmer, or are they?" Most of us were drilled with the "document your code" as we were learning either by instructors or books, but no one here does that (except me).:mad: As far as new development goes, IMHO I think I am *better* because I grasp the concepts of normalization, documentation, OOD. All new concepts to them. I had to explain normalization and pursuede them to let me do it on some new tables I added!:mad: And this is no hole-in-the-wall company either, they have some BIG clients. Well, thanks for letting me beef!
Your not necessarily a bad programmer, but if you have to work with a steaming pile of shit every day it pays to get to know it as well as everyone else rather than to try to convince them all that they are the bad programmers.
"I don't want more choice. I just want better things!" - Edina Monsoon
-
So, the company I work for is pretty small, only about 8 developers. The biggest (web) app is very complicated and is chalk full of errors. To compound the issue, there is absolutly ZERO documentation in the code / database. The DB also has no Foriegn Key contraints and is only marginally normalized. I don't work on the app that much, so I'm not as familiar as everyone else is with it. Whenever a problem comes up, they can jump right to the problem, but it sometimes takes me hours.... The question is "Am I a bad programmer, or are they?" Most of us were drilled with the "document your code" as we were learning either by instructors or books, but no one here does that (except me).:mad: As far as new development goes, IMHO I think I am *better* because I grasp the concepts of normalization, documentation, OOD. All new concepts to them. I had to explain normalization and pursuede them to let me do it on some new tables I added!:mad: And this is no hole-in-the-wall company either, they have some BIG clients. Well, thanks for letting me beef!
Don't worry all those thought's about documentation and explaining code will be beaten out of you by deadlines soon enough.
pseudonym67 My Articles[^] Beginning KDevelop Programming[^]
-
So, the company I work for is pretty small, only about 8 developers. The biggest (web) app is very complicated and is chalk full of errors. To compound the issue, there is absolutly ZERO documentation in the code / database. The DB also has no Foriegn Key contraints and is only marginally normalized. I don't work on the app that much, so I'm not as familiar as everyone else is with it. Whenever a problem comes up, they can jump right to the problem, but it sometimes takes me hours.... The question is "Am I a bad programmer, or are they?" Most of us were drilled with the "document your code" as we were learning either by instructors or books, but no one here does that (except me).:mad: As far as new development goes, IMHO I think I am *better* because I grasp the concepts of normalization, documentation, OOD. All new concepts to them. I had to explain normalization and pursuede them to let me do it on some new tables I added!:mad: And this is no hole-in-the-wall company either, they have some BIG clients. Well, thanks for letting me beef!
15 years since i graduated college and i've never worked at any company where the source and/or DB were documented beyond a few lonely one-liners next to bug fixes. function headers ? hah!
declassified wrote:
Most of us were drilled with the "document your code" as we were learning either by instructors or books
most developers i've worked with didn't go to school for programming and i don't know anyone in real life who reads programming books (other than for reference).
-
So, the company I work for is pretty small, only about 8 developers. The biggest (web) app is very complicated and is chalk full of errors. To compound the issue, there is absolutly ZERO documentation in the code / database. The DB also has no Foriegn Key contraints and is only marginally normalized. I don't work on the app that much, so I'm not as familiar as everyone else is with it. Whenever a problem comes up, they can jump right to the problem, but it sometimes takes me hours.... The question is "Am I a bad programmer, or are they?" Most of us were drilled with the "document your code" as we were learning either by instructors or books, but no one here does that (except me).:mad: As far as new development goes, IMHO I think I am *better* because I grasp the concepts of normalization, documentation, OOD. All new concepts to them. I had to explain normalization and pursuede them to let me do it on some new tables I added!:mad: And this is no hole-in-the-wall company either, they have some BIG clients. Well, thanks for letting me beef!
Having big clients doesn't mean shit. I work for a big IT company and we have very big clients and I work with some big doo doo heads. As for being a bad programmer...well, are you? Something tells me you are not. Document your code judiciously and normalizing a table beyond form 3 is over kill...so I have been told.
-
So, the company I work for is pretty small, only about 8 developers. The biggest (web) app is very complicated and is chalk full of errors. To compound the issue, there is absolutly ZERO documentation in the code / database. The DB also has no Foriegn Key contraints and is only marginally normalized. I don't work on the app that much, so I'm not as familiar as everyone else is with it. Whenever a problem comes up, they can jump right to the problem, but it sometimes takes me hours.... The question is "Am I a bad programmer, or are they?" Most of us were drilled with the "document your code" as we were learning either by instructors or books, but no one here does that (except me).:mad: As far as new development goes, IMHO I think I am *better* because I grasp the concepts of normalization, documentation, OOD. All new concepts to them. I had to explain normalization and pursuede them to let me do it on some new tables I added!:mad: And this is no hole-in-the-wall company either, they have some BIG clients. Well, thanks for letting me beef!
we don't need no stinkin' comments! (well someone had to say it).
-
So, the company I work for is pretty small, only about 8 developers. The biggest (web) app is very complicated and is chalk full of errors. To compound the issue, there is absolutly ZERO documentation in the code / database. The DB also has no Foriegn Key contraints and is only marginally normalized. I don't work on the app that much, so I'm not as familiar as everyone else is with it. Whenever a problem comes up, they can jump right to the problem, but it sometimes takes me hours.... The question is "Am I a bad programmer, or are they?" Most of us were drilled with the "document your code" as we were learning either by instructors or books, but no one here does that (except me).:mad: As far as new development goes, IMHO I think I am *better* because I grasp the concepts of normalization, documentation, OOD. All new concepts to them. I had to explain normalization and pursuede them to let me do it on some new tables I added!:mad: And this is no hole-in-the-wall company either, they have some BIG clients. Well, thanks for letting me beef!
you could document your code..... or you could bask in your new found job security :)
-
15 years since i graduated college and i've never worked at any company where the source and/or DB were documented beyond a few lonely one-liners next to bug fixes. function headers ? hah!
declassified wrote:
Most of us were drilled with the "document your code" as we were learning either by instructors or books
most developers i've worked with didn't go to school for programming and i don't know anyone in real life who reads programming books (other than for reference).
Chris Losinger wrote:
i don't know anyone in real life who reads programming books (other than for reference).
You do now - well, if only by proxy. Then again, my wife does think I'm a complete and utter sad ....:-D
Deja View - the feeling that you've seen this post before.
-
So, the company I work for is pretty small, only about 8 developers. The biggest (web) app is very complicated and is chalk full of errors. To compound the issue, there is absolutly ZERO documentation in the code / database. The DB also has no Foriegn Key contraints and is only marginally normalized. I don't work on the app that much, so I'm not as familiar as everyone else is with it. Whenever a problem comes up, they can jump right to the problem, but it sometimes takes me hours.... The question is "Am I a bad programmer, or are they?" Most of us were drilled with the "document your code" as we were learning either by instructors or books, but no one here does that (except me).:mad: As far as new development goes, IMHO I think I am *better* because I grasp the concepts of normalization, documentation, OOD. All new concepts to them. I had to explain normalization and pursuede them to let me do it on some new tables I added!:mad: And this is no hole-in-the-wall company either, they have some BIG clients. Well, thanks for letting me beef!
declassified wrote:
And this is no hole-in-the-wall company either, they have some BIG clients. Well, thanks for letting me beef!
you can get as big as they come and still run into this. I gave up fighting it for a while, but I saved my ammo. Documentation won't help you "much" (it does a little), when the code is fresh in your mind. Your recall is faster and better than code documentation. BUT it has its limits. A) you don't share your memories with your team, so documentation is the only contact other people have wth your code, be kind, document B) When you put down that project and let your memory work on something else, the old memories get pushed to the bottom and are harder to recall, now documentaton is your only reminder, documentation is your friend, be kind to yourself, document!
_________________________ Asu no koto o ieba, tenjo de nezumi ga warau. Talk about things of tomorrow and the mice in the ceiling laugh. (Japanese Proverb)
-
So, the company I work for is pretty small, only about 8 developers. The biggest (web) app is very complicated and is chalk full of errors. To compound the issue, there is absolutly ZERO documentation in the code / database. The DB also has no Foriegn Key contraints and is only marginally normalized. I don't work on the app that much, so I'm not as familiar as everyone else is with it. Whenever a problem comes up, they can jump right to the problem, but it sometimes takes me hours.... The question is "Am I a bad programmer, or are they?" Most of us were drilled with the "document your code" as we were learning either by instructors or books, but no one here does that (except me).:mad: As far as new development goes, IMHO I think I am *better* because I grasp the concepts of normalization, documentation, OOD. All new concepts to them. I had to explain normalization and pursuede them to let me do it on some new tables I added!:mad: And this is no hole-in-the-wall company either, they have some BIG clients. Well, thanks for letting me beef!
-
So, the company I work for is pretty small, only about 8 developers. The biggest (web) app is very complicated and is chalk full of errors. To compound the issue, there is absolutly ZERO documentation in the code / database. The DB also has no Foriegn Key contraints and is only marginally normalized. I don't work on the app that much, so I'm not as familiar as everyone else is with it. Whenever a problem comes up, they can jump right to the problem, but it sometimes takes me hours.... The question is "Am I a bad programmer, or are they?" Most of us were drilled with the "document your code" as we were learning either by instructors or books, but no one here does that (except me).:mad: As far as new development goes, IMHO I think I am *better* because I grasp the concepts of normalization, documentation, OOD. All new concepts to them. I had to explain normalization and pursuede them to let me do it on some new tables I added!:mad: And this is no hole-in-the-wall company either, they have some BIG clients. Well, thanks for letting me beef!
declassified wrote:
and is chalk full of errors
"Chock" full...
declassified wrote:
o compound the issue, there is absolutly ZERO documentation in the code / database.
The rest of the programmers suck.
"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, 1997
-----
"...the staggering layers of obscenity in your statement make it a work of art on so many levels." - Jason Jystad, 10/26/2001 -
15 years since i graduated college and i've never worked at any company where the source and/or DB were documented beyond a few lonely one-liners next to bug fixes. function headers ? hah!
declassified wrote:
Most of us were drilled with the "document your code" as we were learning either by instructors or books
most developers i've worked with didn't go to school for programming and i don't know anyone in real life who reads programming books (other than for reference).
Chris Losinger wrote:
15 years since i graduated college and i've never worked at any company where the source and/or DB were documented beyond a few lonely one-liners next to bug fixes. function headers ? hah!
Is that why you have your own?
[My Blog]
"Visual studio desperately needs some performance improvements. It is sometimes almost as slow as eclipse." - Rüdiger Klaehn
"Real men use mspaint for writing code and notepad for designing graphics." - Anna-Jayne Metcalfe -
Chris Losinger wrote:
15 years since i graduated college and i've never worked at any company where the source and/or DB were documented beyond a few lonely one-liners next to bug fixes. function headers ? hah!
Is that why you have your own?
[My Blog]
"Visual studio desperately needs some performance improvements. It is sometimes almost as slow as eclipse." - Rüdiger Klaehn
"Real men use mspaint for writing code and notepad for designing graphics." - Anna-Jayne Metcalfei have my own because once upon a time i had too much energy for only one programming job to consume
-
Your not necessarily a bad programmer, but if you have to work with a steaming pile of shit every day it pays to get to know it as well as everyone else rather than to try to convince them all that they are the bad programmers.
"I don't want more choice. I just want better things!" - Edina Monsoon
John Cardinal wrote:
Your not necessarily a bad programmer
A-hem... (cough)... but your Englsih.... :-)
-
John Cardinal wrote:
Your not necessarily a bad programmer
A-hem... (cough)... but your Englsih.... :-)
-
So, the company I work for is pretty small, only about 8 developers. The biggest (web) app is very complicated and is chalk full of errors. To compound the issue, there is absolutly ZERO documentation in the code / database. The DB also has no Foriegn Key contraints and is only marginally normalized. I don't work on the app that much, so I'm not as familiar as everyone else is with it. Whenever a problem comes up, they can jump right to the problem, but it sometimes takes me hours.... The question is "Am I a bad programmer, or are they?" Most of us were drilled with the "document your code" as we were learning either by instructors or books, but no one here does that (except me).:mad: As far as new development goes, IMHO I think I am *better* because I grasp the concepts of normalization, documentation, OOD. All new concepts to them. I had to explain normalization and pursuede them to let me do it on some new tables I added!:mad: And this is no hole-in-the-wall company either, they have some BIG clients. Well, thanks for letting me beef!
No, you're not a bad programmer. In fact, you sound like a very good programmer. But I think you're an idiot to work with these bozos! ;P (please take that with the humor it was intended to be, off color as it may sound) Marc
-
I know, I know, it's my Achilles heel. In a world where "nite" is increasingly a valid spelling, I don't see why we can't just combine your and you're and call it even. ;)
"I don't want more choice. I just want better things!" - Edina Monsoon
John Cardinal wrote:
Achilles heel
:-) strictly speaking, of course, there should be an apostrophe in there: Achilles' heel :-)
-
I know, I know, it's my Achilles heel. In a world where "nite" is increasingly a valid spelling, I don't see why we can't just combine your and you're and call it even. ;)
"I don't want more choice. I just want better things!" - Edina Monsoon
John Cardinal wrote:
In a world where "nite" is increasingly a valid spelling
Obviously not the same world I inhabit.
Upcoming FREE developer events: * Glasgow: db4o: An Embeddable Database Engine for Object-Oriented Environments, Mock Objects, SQL Server CLR Integration, Reporting Services ... My website
-
John Cardinal wrote:
Achilles heel
:-) strictly speaking, of course, there should be an apostrophe in there: Achilles' heel :-)
-
John Cardinal wrote:
In a world where "nite" is increasingly a valid spelling
Obviously not the same world I inhabit.
Upcoming FREE developer events: * Glasgow: db4o: An Embeddable Database Engine for Object-Oriented Environments, Mock Objects, SQL Server CLR Integration, Reporting Services ... My website