Permabanned
- Joined
- 10 Dec 2008
- Posts
- 4,080
- Location
- London
1) Is your code commented (yes including all the 'amazingly simple' buts) and does it apply to inter-company and industry wide standards?
2) Do you use all the functions of the language, or not bother with ones you don't understand because you can program around them and it kinda works so who cares what the 'xxxx' function does you don't need it?!
3) Do you use variables/routines/filenames called things like 'Banana' and 'Rhubarb' or do you follow a pre-defined naming convention (hopefully corporate wide convention)?
4) Do you modularise (or library) your code as much as possible, so other people can use bits of it later on if they need to, called from THEIR code?
5) Do you document what you do especially if you wander off spec for some crazy reason (because you think you've thought of a better way than the analyst thought up!!!! Aargh bane of my life when developers do this!)
6) Can you decisively ask a business analyst what exactly he wants when he's written a vague spec. Can you stop assuming things (Don't ever assume anything! God this has cost my client a lot of money!)
7) Can you take criticism of your code OK, or take it as a personal insult so defend yourself loudly and be in a snotty mood with the tester for 2 days?
8) Does your code 'compile with warnings, but who cares about warnings?'. Does it god forbid have memory leaks? Does it use compiler functions that are due to be phased out on the next release of the compiler?
9) Does your code work on multiple platforms, or 'who knows, but it works on my platform' - 'Oh , they're still using Windows '95 up in Grimsby branch and you've spent £4000 rolling it out to there? Oh god no it won't work I didn't think of that)
10) Do you have good change control systems? Do you use pre-existing libraries to do stuff or 'can't be bothered to find them, I'll just program it again'.
11) Can other people take on your half finished project easily, knowing where all the stuff is etc. if you get hit by a bus? Don't tell me they're starting from scratch because it's all in wierd places on your C-drive?
12) In 16 years when the spec has been lost, can someone easily reverse engineer your code and figure out easily what it does and why?
13) Can you happily use an old cruddy version of compiler/interpreter/PC because your client is too ***** to get you bleeding edge tools?
14) Can you NEVER exclusively lock tables, and always think that other programs may be after the same resource you are (normally table) so make your program work 'nicely' with whatever else may be running (even stuff that hasn't been programmed yet)
15) Can you call other modules easily even if they are programmed in a different language?
That was a brainstorm by the way!
2) Do you use all the functions of the language, or not bother with ones you don't understand because you can program around them and it kinda works so who cares what the 'xxxx' function does you don't need it?!
3) Do you use variables/routines/filenames called things like 'Banana' and 'Rhubarb' or do you follow a pre-defined naming convention (hopefully corporate wide convention)?
4) Do you modularise (or library) your code as much as possible, so other people can use bits of it later on if they need to, called from THEIR code?
5) Do you document what you do especially if you wander off spec for some crazy reason (because you think you've thought of a better way than the analyst thought up!!!! Aargh bane of my life when developers do this!)
6) Can you decisively ask a business analyst what exactly he wants when he's written a vague spec. Can you stop assuming things (Don't ever assume anything! God this has cost my client a lot of money!)
7) Can you take criticism of your code OK, or take it as a personal insult so defend yourself loudly and be in a snotty mood with the tester for 2 days?
8) Does your code 'compile with warnings, but who cares about warnings?'. Does it god forbid have memory leaks? Does it use compiler functions that are due to be phased out on the next release of the compiler?
9) Does your code work on multiple platforms, or 'who knows, but it works on my platform' - 'Oh , they're still using Windows '95 up in Grimsby branch and you've spent £4000 rolling it out to there? Oh god no it won't work I didn't think of that)
10) Do you have good change control systems? Do you use pre-existing libraries to do stuff or 'can't be bothered to find them, I'll just program it again'.
11) Can other people take on your half finished project easily, knowing where all the stuff is etc. if you get hit by a bus? Don't tell me they're starting from scratch because it's all in wierd places on your C-drive?
12) In 16 years when the spec has been lost, can someone easily reverse engineer your code and figure out easily what it does and why?
13) Can you happily use an old cruddy version of compiler/interpreter/PC because your client is too ***** to get you bleeding edge tools?
14) Can you NEVER exclusively lock tables, and always think that other programs may be after the same resource you are (normally table) so make your program work 'nicely' with whatever else may be running (even stuff that hasn't been programmed yet)
15) Can you call other modules easily even if they are programmed in a different language?
That was a brainstorm by the way!
Last edited:
