Signs You're a Crappy Programmer

[nagatonichan]

---

i'm soooo crappy

[bolivar1985]

for me this one i like...hehehe...

Your users are stupid. Really stupid.

can you believe they would forgot the process how to transac the application they propose?
sometimes they even forgot their username and password...eee..e..e.e....

[SYNCH]

1. Java is all you'll ever need.
.NET is created to allow other programming languages use its power. You are not limited to any programming language as long as your programming language emits IL which .NET understands (I'm not advocating .NET in anyway, but this is one where it shines)

2. "Enterprisey" isn't a punchline to you.
It depends on the kind of app you are going to do. You are not going to be "Enterprisey" in order to create a blogging system, right?

3. You are adamantly opposed to function/methods over 20 lines of code.
I prefer a function that I can read without scrolling below. I hate reading some "if" condition back-n-forth to check where it ends and start

4. "OMG! PATTERNS!"
...is a way of life. If the app is designed to perfection, patterns will be of great use. If it's a crappy design and so is the usage of the patterns

5. CPU cycles are a precious commodity and your programming style and language reflects that belief.
See HowBig

6. You think no function/method should have multiple return points.
What's the point of going all through the routine and yet it doesn't do anything because it's invalid. Just return it and be done with it

7. Your users are stupid. Really stupid.
User-friendly is not enough these days, we need idiot-friendly which Vista/ribbon-style made users idiots

8. You take great pride in the high volume of code you write.
KISS

9. Copy and paste is great, it helps you write decoupled code!
Sometimes, it does. Premature optimisation/generalisation can cause chaos creating flags just to behave your generalised function a certain way. But we should always refactor at times.

10. You think error handling means catching every exception, logging it and continuing on.
Unhandled and unexpected exceptions/errors are meant to be exploded in the app.

11. You model all your code in UML before you write it.
Good if with teams and your work is just to design. There's this attempt to visualise logic (Windows Workflow) which already existed with/adapted from BPEL, we'll just see if this work out to small ISVs

12. Your code wipes out important data.
Crap!

[L1Technician]

Copy and paste

99.9% of Software Engineers do this.

[kamsky]

if you find in your for-loop index has more or less 1 number then you try to add or subract your index to make your program working with trial and error and without understanding why you have more or less 1 of your index.

I hate this kind of programmer.

[..mykel..]

everyone might be crappy, but make sure you know what are you doing so you won't loose your logic..

[Rainerius]

Walay crappy oi, kulang lang cguro sa knowledge or guidance. Pareho ra ta tanan naay utok.