Current Events > SQL is the easiest programming language to learn

(+) Yeah! (+)

I like threads like these bc they're a reminder that you need to have a strong, self-driven work ethic and do all sorts of stuff on your own, for free, if you want to eventually become a reliable working professional

---

DaveTheUseless posted...

Literally confusing Java and JavaScript O_O

They used to be superficially similar at one point, and the name "ECMAScript" never caught on.

Veggeta_MAX posted...

companies won't need JSON certified people

What's even the point of JSON certification? If you're ever hand-building json objects, something has gone terribly wrong.

Giant_Aspirin posted...

disagree. "it depends". there are very valid use cases for nosql / document databases

Until youve developed your entire app around it and then some dumb ass salesman requests a new feature and youll be kicking yourself wishing you had have gone relational from the start

Also, that a bachelor's degree in comp sci in and of itself only means so much

---

DaveTheUseless posted...

Also, that a bachelor's degree in comp sci in and of itself only means so much

Agreed. In the world of IT, experience means much more than a piece of paper.

---

Giant_Aspirin posted...

there are very valid use cases for nosql / document databases

usually very bad reasons but that's just me being old and not wanting to learn new things >_> taking sql from me makes me feel handicapped.
pinky0926 posted...

I work for a database CRM. The reason for why this amazing gulf exists (i.e. everyone needs SQL developers and it's "easy") is because the scope for SQL is huge, per my previous post. I can find a thousand generic Sys Admin IT guys that say they know SQL, but finding an actual developer that can confidently write scripts and reports using SQL is rare.

A lot of it is speed. It's great that you know python and C++ and everything else, but if it takes you 4 hours to write a SQL script that a dedicated SQL developer can do in 40 minites, guess who's getting the job...

hiring a programmer to be a sql report writer is dumb (and will make your programmer hate you). Like hiring a DBA to be a programmer would be dumb.

---

DaveTheUseless posted...

that you need to have a strong, self-driven work ethic

nothing says strong self-driven work ethic like shit posting on ce during work hours.

---

DaveTheUseless posted...

I like threads like these bc they're a reminder that you need to have a strong, self-driven work ethic and do all sorts of stuff on your own, for free, if you want to eventually become a reliable working professional

I love threads like these because they are a reminder of how you can't get two or more devs together to discuss anything as inane as what colour the sky is today without an argument ensuing.

---

I Like Toast posted...

nothing says strong self-driven work ethic like shit posting on ce during work hours.

The future is bright for Vegy and I

---

If things ain't broke then you are doing an amazing job.

---

pinky0926 posted...

I love threads like these because they are a reminder of how you can't get two or more devs together to discuss anything as inane as what colour the sky is today without an argument ensuing.

we all agree that marketing department is the root of all problems and our managers are morons that wouldn't be employed if not for us.

---

Also in my case I'm college faculty, so I have the benefit of somewhat making my own work hours, l0l

---

I Like Toast posted...

we all agree that marketing department is the root of all problems and our managers are morons that wouldn't be employed if not for us.

Oh I am aware of how important devs are, they make sure to tell me every day

---

pinky0926 posted...

Oh I am aware of how important devs are, they make sure to tell me every day

this seems obligatory now:

IYO, what's the difference between an engineer and a IT person?

---

Questionmarktarius posted...

this seems obligatory now:

lol, indeed

---

Customers are really dumb at explaining what they want, though.

---

Basic was the easiest I thought but I dont know if its used anymore, I havent seen it since the commodore 64

Veggeta_MAX posted...

Customers are really dumb at explaining what they want, though.

Devs tend to be belligerent and anti-social and actually proud of how few soft skills they possess while simultaneously being in a permanent state of anger that therefore someone else must exist to try and be an interface between the person wanting to buy the thing and the person who has to design it

(lol im just shitposting at this point, but the ego of devs is as funny as the technical incompetence of salesmen)


---

Questionmarktarius posted...

this seems obligatory now:

At least the engineers saw the atrocity handed to them by the architect and improved on it

pinky0926 posted...

(lol im just shitposting at this point, but the ego of devs is as funny as the technical incompetence of salesmen)

there's a reason you needed a bill gates to pair with paul allen and a steve jobs with Wozniack for those to become what they did.

---

Questionmarktarius posted...

this seems obligatory now:

Better'd



---

Patience and communication skills is key to being an IT worker.

---

Squirrel is the tastiest animal to eat

---

The only thing that sucks about SQL is ya gotta know how database works.

---

I Like Toast posted...

we all agree that marketing department is the root of all problems and our managers are morons that wouldn't be employed if not for us.

+1

---

Veggeta_MAX posted...

The only thing that sucks about SQL is ya gotta know how database works.

In the DVD commentary for "Lemon of Troy", Matt Groening states that Database is his least favorite recurring character.

---

Kloe_Rinz posted...

Until youve developed your entire app around it and then some dumb ass salesman requests a new feature and youll be kicking yourself wishing you had have gone relational from the start

that can happen, yeah. but evolving requirements is a threat to consider when picking _any_ technology during your design phase. every single piece of tech in your application stack should be replaceable with minimal impact to the rest of the code. if swapping one persistence technology for another has huge ripple effects throughout your code base, you're too tightly coupled to it and could use a layer of abstraction.

where i work we have a gigantic Hadoop cluster that holds millions of records that have no relation to each other at all. we search against it and retrieve documents and it's worked very well so far.

I Like Toast posted...

usually very bad reasons but that's just me being old and not wanting to learn new things >_> taking sql from me makes me feel handicapped.

agreed. i find whenever the "new hotness" is out people gravitate towards it even when it's not a good the use case. i call that "resume driven development".

im not against learning new things, but i do avoid the "new hotness" until it's cooled down a bit. so many promising new technologies come along only to be replaced by something better in a year or two. *hugs Java and RDMBS*

---