Am I a bad programmer?
-
Yeah, I know (ssh!) - I am old enough and fortunate enough to have benefitted from a classical education - when Britain still had an education system to be proud of... nowadays we have to rely on the likes of French Canadians of Russian descent (?) to teach us our own language... cheers / za vas Fred
My education was fine and I only finished university a few years ago! :) Don't buy into the media's perception of our education!! To the original poster - you're fine, and so are they. You just both enjoy different styles, if it works for the company and not for yourself then maybe you should think of joining a company that is a little more structured. If the system is obviously weak because of the coding, then you should speak up and change things.
-
John Cardinal wrote:
Achilles heel
:-) strictly speaking, of course, there should be an apostrophe in there: Achilles' heel :-)
-
Actually, according to the last example of Rule 2 at http://www.grammarbook.com/punctuation/apostro.asp[^] , because the name is singular (even though it ends with s), the correct version is "Achilles's".
What do Americans know about English? Bah, I say... I defy you to find ONE example in *Englsih* literature anywhere that uses that abomination! "Achilles's" indeed. :rolleyes: :^)
-
What do Americans know about English? Bah, I say... I defy you to find ONE example in *Englsih* literature anywhere that uses that abomination! "Achilles's" indeed. :rolleyes: :^)
-
It's in our genes... we only spell things the way we do to annoy and confuse the French!
-
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!
Bad Programmer! BAAAAD Programmer (I say as I smack you on the nose with a rolled up newspaper)! Now go outside and don't come back in until you are paper-trained. :)
m.bergman
-- For Bruce Schneier, quanta only have one state : afraid.
-
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!
While the rest of the clowns in here debate the nuances of shades-of-gray grammatical meaningless, I will try to give you a reasonable answer. GET THE H@LL of that place now before they ruin you for life!!! Find a group that appreciates the proper way of doing IT and go to it now. There are plenty of fine companies that know what is the right way. Your current company is on the road to disaster. I am serious - save your soul and get out now.
-
What do Americans know about English? Bah, I say... I defy you to find ONE example in *Englsih* literature anywhere that uses that abomination! "Achilles's" indeed. :rolleyes: :^)
-
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're not a bad programmer. I work in a company with the same problems. Now I'm still working on a project started 2 years ago, and with me there are 3 programmers. I wrote some code, other parts were written by each other. Every line of code, every table in the DB, and every flow is still undocumented at all. :confused: Unfortunately it's hard to make the company's boss understand this :mad: when you was selected on the task. To them, the only important thing is to solve the problem in the faster and less expensive solution. :cool: regards, Aniel
-
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!
Sounds so much like the company that I used to work for. Good Luck... in some cases, the more time you spend on trying to prove someone isn't doing their job correctly and the less time you spend actually working turns out poorly in the end. Let me know what your perspective is in 20 years...
Suz