Lazy programmer

Jan 19, 2015 3:37 PM

tuxedobob

Views

6327

Likes

13

Dislikes

5

Lazy programmer

I'm going to be using this for an internal project. Other programmers might enjoy dropping this in their projects too.

sql

"This is very important data, I have no backup" -dumb customers

10 years ago | Likes 4 Dislikes 0

I fire programmers who don't check their work. Our whole team goes down in the customer's eyes.

10 years ago | Likes 2 Dislikes 0

SQL is just a language to query the db. Could you just query to see if its in there?

10 years ago | Likes 1 Dislikes 0

I could. Or I could click the link and see if it's on the page it belongs on. It's not exactly important if it fails. :)

10 years ago | Likes 1 Dislikes 0

Ew, SQL is the bane of my existence..

10 years ago | Likes 1 Dislikes 0

Why? It's not like it's difficult.

10 years ago | Likes 1 Dislikes 1

its tedious as shit and most compilers dont have syntax and error checkers that are really helpful. Most just say there is an error and

10 years ago | Likes 1 Dislikes 0

not what or where it is.

10 years ago | Likes 1 Dislikes 0

You should rarely be doing SQL by hand, you should be using Hibernate or some variant depending on language.

10 years ago | Likes 1 Dislikes 0

I used Netbeans when I did my project, very little by hand. But what I did by hand had a few errors and I was only given a null pointer

10 years ago | Likes 1 Dislikes 0

Even though the actual error wasnt a nullpointer.

10 years ago | Likes 1 Dislikes 0

Are you not using a transaction?

10 years ago | Likes 2 Dislikes 0

Not really important enough.

10 years ago | Likes 1 Dislikes 1

Inconsistent data is ok with your application or just that particular trip to the database?

10 years ago | Likes 1 Dislikes 0

In practice, it's essentially a single-user system. There's no risk of dirty reads.

10 years ago | Likes 1 Dislikes 1