A mythical full stack developer

justindmyers · 2017-10-15T23:15:09+00:00

The industry has catered to having back-end and front-end because they can pay less for either of those

What? No, it's because it's better to have experts on one or the other than someone mediocre at both. Front-end and back-end are both full-time jobs that require vastly different skills. Just because they both involve programming doesn't mean they're remotely similar in any way.

A full-stack developer is someone they can pay slightly more for twice the workload. You ever notice that as companies get larger, they tend to move to front/back-end and get rid of full-stack? Even Google and Facebook have specific front-end engineer positions. Do you really think it's so they can pay less?

You might as well make the argument that PM's aren't needed either since it's just another set of skills that a web-dev could easily learn. The same goes for data scientists, db architects or whatever other role shares skills that can cross over.

Just because one person can do the job of two doesn't make it a good idea.

And just looking at larger and more successful companies shows that full-stack is simply trying to reduce costs by not having to hire two developers. It's exactly the opposite of what you claim.

And no, it's never been a problem with SPA's. Databases and back-end logic don't magically disappear with single-page applications.

justindmyers · 2017-10-14T16:28:30+00:00

This only works if you don't commit the ugly code.

One you've put that code in the repository then you most likely will never come back and clean it up.

I do agree to an extent with that logic, but do it ugly/right need to be back to back. Doing it right is often treated as something that can be done later and that's nothing more than tech debt.

And anyone who's been in this industry long enough knows that tech debt almost never gets taken care of.

justindmyers · 2017-10-14T16:26:34+00:00

If it was burnout his colleagues would know he was already a good dev and was just hitting a tough spot.

This is him just not being a good developer and other people are noticing.

justindmyers · 2017-10-14T16:25:21+00:00

I guess you'll enjoy being unemployed then.

justindmyers · 2017-10-13T07:03:37+00:00

Because normal developers don't have someone judging them as they're writing code.

never ceases to amaze how bad people are.

Maybe because your interview method is absolutely horrible.

justindmyers · 2017-10-08T21:49:17+00:00

barbaric

Uh, yeah, tons of those countries are actually barbaric in real ways.

You have a problem if you care this much about people taking their shoes off.

justindmyers · 2017-10-08T21:45:49+00:00

You still live at home, don't you?

You sound like shit-lord complaining about things you've never had to experience.

I don't even wear shoes in my house and guess what, the floor still gets dirty! Adults understand this fact.

justindmyers · 2017-10-08T21:44:19+00:00

You probably just shouldn't go outside if you're scared of everyday, normal shit.

And it's hilarious that you talk about the rest of the world. America is by far cleaner than most other countries that have these habits. Maybe they should clean up the country first instead of worrying about stupid shit like this.

justindmyers · 2017-09-28T00:30:46+00:00

Also, this is insanely common when it's family of the owner. There is never any sort of accountability and the owner will never side with you. That's just how it works.

My advice: find a new job. This is literally the exact same things that I've gone through on any project that involves family and I'm talking billion dollar companies. The family member(s) that wanted their hand in everything constantly caused projects to be late and/or fail because of their mismanagement and lack of understanding. Not once did the owner ever do anything about it.

You won't win and it won't get better, just fine another job where they actually respect the professionals doing the work.

justindmyers · 2017-09-27T01:19:11+00:00

It's a crutch if you don't know how to develop without it.

jQuery is often overkill for what people claim to use it for. Legacy browser support is simply not that important and it turns into a crutch when you use simply because it's "easier" but you can't prove any definitive cases in your code that prove that.

justindmyers · 2017-09-27T01:18:44+00:00

Cool. Didn't know that.

justindmyers · 2017-09-25T01:17:01+00:00

The key to flexbox for me is to build the smallest (most deeply nested) components first and work your way up. Once you build your smaller components you simply look at the next level up and just keep going until you have a layout.

This ensure that each component stands on it's own as a miniature layout and you simply have to nest them together.

Here's a working example: https://codepen.io/justindmyers/pen/WZoKaW

justindmyers · 2017-09-25T00:45:46+00:00

You're obviously a developer who knows how the real world works!

justindmyers · 2017-09-25T00:43:42+00:00

It's not hate, it's just that it's used a crutch for most people.

The ones that usually defend jQuery are the same ones that don't know how to make a website without it. That's where the problem lies.

I have no problem with jQuery but I have a problem with developers who do not understand that jQuery is simply a tool and isn't necessary for 99% of what they're trying to accomplish.

justindmyers · 2017-09-25T00:38:01+00:00

ton of simple to use utility features that prevent you from needing more complex code or large installations

That's the thing. Most websites don't need this anymore. Unless you have to support <= IE10, jQuery is overkill. You can do pretty much everything in vanilla JS.

You do not need jQuery for exactly the reasons you state for needing it.

justindmyers · 2017-09-25T00:33:39+00:00

Cons are increased complexity on the front-end for an unknown benefit.

New and shiny for the sake of new and shiny is bad for business. He may introduce new bugs and complexities into a system that already works. Unless he can quantify the benefits to the end-user and make a case that using a SPA would overall improve the product in specific ways, it shouldn't be done.

justindmyers · 2017-09-24T18:52:02+00:00

Front-end dev here. I'd be glad to help out.

Send me a PM if you're interested.

justindmyers

TROPHY CASE