@ZethMatthews I stuck with 'em for ages out of habit. Question is, is habit the only reason we're doing it?

@swchang10 That applies to pretty much everything, though. Hell, I'd say 90% of what I know and use on my job was something I learned freely and online...why am I 50k in debt? 😂

@Vip3rDev Couldn't begin to guess

Then again, with the zoomed out picture...no socks? You're good 😂

You don't need to be more professional, you need to find a job that allows more freedom 😂

You should validate on both the client AND the server. Client side validation helps the user spot mistakes, saving them time and a page load. Server side validation prevents bad data from getting into the DB.

Beat me to it...

I'll have another for naturalizer.com once our rebrand goes live 😂

On bzees.com, with a mobile device, if you go to the "fetching hope" page, click the slider arrow down the page, and then shake your phone a dog will bark.

On lifestride.com, if you search for "our puppy", a full screen picture of a dog appears

I'd say that jQuery is used on a vast majority of sites, so being familiar with it is almost a necessity. I agree with all the common complaints: it's large if you're only using one or two things, IE is up to speed (kinda) so it's not as necessary, it can add overhead when vanilla js works just as well, among others. That said, look at job postings. There's a ton out there with jQuery experience either necessary or a plus. Knowing it can get your foot in a lot of doors.

Lol, just a laugh and an eye roll, but still

Tried the FTDI drivers, tried the CH340 drivers in case I had a cheap clone and didn't know it. Also tried a new cable. Also tried a few terminal commands that were rumored to fix one thing or another. Sending it back, I guess.

A developer with a passion for learning can pick up a framework fairly quickly. With that said, if they haven't even heard about ES6 I would find it hard to believe that they have that passion.

I don't think the issue is CSS per se, but rather the inconsistencies across different browsers. When you do server side code, when you get it working it works. With CSS, you get it working, and then have to get it working in IE, Opera, Safari (the new IE), and all the older browsers you're forced to support.

I was a student developer at MU. When I graduated they created a full time position for me, and I rolled straight into it.

This makes me want to cry....

Brackets

Toss the ideas my way, I'll Zuckerberg ya ;)

keep at it, we've all been there.

300 ++...wow, ty devRant community!

ha! I have the same issue at my job.

This adds, funnily enough, yet another post about Pokemon Go... :)

There, have another! :)

lol....5 comments and 1 ++

They ran out on mine. The batch was sub-par. Should be here soon though, good email contacts!

Meh...Safari is the new IE

stress ball!

Mine bought me vodka and a sugar free Red Bull...it was a brutal week...

KISS - Keep It Simple, Stupid. So many techs in web development that you'll get overwhelmed quickly. Try something small first :)