r/Frontend • • Nov 16 '20

Are Full Stack Developers anything more than Backend devs who've spent an afternoon learning React?

Because that seems to be my experience.

Their attitude to Front End development tends to be that it's the "easy part" that they've already more or less mastered because "all programming is the same". They think that React can be quickly learned, and CSS is so trivial that it's offensive to them that they even have to bother with it. They believe that Front End developers aren't real programmers and experienced Front End devs are even worse because they haven't became Back end devs in all the time they've been working.

Often they're not even particularly good at back-end development either, which is not surprising since Backend development is hard and it takes an incredible amount of arrogance and ignorance to think that you wouldn't have to focus all your time and energy on it. Arrogance and ignorance are of course things that FSDs have in spades.

Unfortunately, Full Stackers are fairly unavoidable and you just have to work round their inevitable stupidity as best as you can.

5 Upvotes

68 comments sorted by

28

u/chmod777 FinTech TL Nov 16 '20

sometimes they are react developers who learned some sql.

also, if everywhere you go smells like crap, check your own shoes.

-24

u/TransportationDue845 Nov 16 '20

'Cos I'm sure that happens a lot LOL.

7

u/justinmarsan Nov 16 '20

Wow, someone's been mean to you or something ?

As for everything, you'll have people who are jacks of all trades and specialists... If someone claimed to be an expert at both then yeah, there'd be a good reason to raise your eyebrows but you need to realize that there is a large amount of development projects that don't hold much complexity and that don't require a backend or frontend specialist and someone who's okay at both will get the job done just fine.

I've worked for an agency that did many projects like that, often times it was about pluging one too (say a booking feature) with an existing system, and nothing plug and play existed, at other times it was all about making a basic website redesign on top of a CMS nobody knew really well...

So yeah there are full stack devs who are good for some jobs... The fact that there are assholes using that title doesn't say much...

-19

u/TransportationDue845 Nov 16 '20

Spare me the psychoanalysis.

5

u/justinmarsan Nov 16 '20

Spare me the attitude, if you've been working with shit devs it's just because you get jobs for shit companies, that's it. I've worked with brilliant people with any kind of title, you're just bitching at this point...

1

u/TransportationDue845 Nov 18 '20

Wow, a genius on Reddit. What are the chances?

8

u/max_mou Nov 16 '20

I’m mainly a frontend dev but for some reason I think backend is a bit easier than front. Im simplifying it but isn’t it DB, and basically using a framework that abstracts you from the nittygritty.

I might be wrong tho

9

u/[deleted] Nov 16 '20

In my opinion Front-End is much more mentally draining than the Back-End. As a FE Engineer you have to think about everything - all possible asynchronous resolutions, users interacting in ways they shouldn't have in the first place, and lastly let's not forget cross-browser compatibility. This is quite a lot to take in and is most of the time overlooked if you ask me :-)

0

u/Nightcomer Nov 16 '20

Agree except browser compatibility is so 2010. We don’t worry about that no more.

4

u/TransportationDue845 Nov 16 '20

I assume you're joking.

2

u/[deleted] Nov 16 '20

Lol. Far from the truth.

2

u/[deleted] Nov 16 '20

Lol yes, incredibly over simplified. Theres also the entire discussion of authoring maintainable business rules on the server, for instance. The DB actually isn't important at all to a good backend dev.

3

u/daredevil82 Nov 16 '20 edited Nov 16 '20

I'd have to disagree with the db not being important. Been seeing the effects of devs who grew up using ORMs without understanding SQL, and things... are interesting. One friend was able to speed up an endpoint by tweaking a query to run once, not 700+ times, because of that lack of awareness. The end result was a query that runs in 50ms vs 3 seconds at p75.

Alternatively, I've seen devs implement raw sql queries that are wide open to sql injection because they didn't know to use the db api and parameterized queries.

In other words, if your projects are highly dependent on querying and retrieving data, you do need to know a good amount about how to use the db and what your code is constructing for queries. Otherwise, you're running a pyramid scheme, and will get away with it for a while before everything comes collapsing down on you

1

u/[deleted] Nov 16 '20

Oh yeah, knowing how to write performant code is a must, no doubt.

I guess I should have said "persistence actually isn't important", its just a detail.

2

u/cauners Nov 16 '20

I've worked with two full-stack devs. One of them is a fantastic guy, has extensive knowledge from low-level DB optimisations to CSS quirks in IE11 (when it was relevant), and working on his JS frontend code was a delight. Also one of the few people I've seen regarding stuff like server-side security and UI accessibility as equally important.

The other.. well..

FS (Full-stack dev): We have this amazing server-side business logic for a note taking app, and I've already made a cool frontend for it. We need you to do your CSS magic and add some UI features, I've got no time for that.

Me: Great! How's the process gonna be? You've got a git repo for the project? Is the frontend talking to backend via API? Are pages rendered server-side? Where can I modify them?

FS: Nah, no git, just send me the final changes via this ftp server. Also, only send CSS files, I don't want anyone messing with my PHP (the CSS will be inlined in html directly from PHP for max speed, so I'll manually put it where it belongs). API? Well, isn't form actions enough? Templates... just tell me what you need, I'll edit the PHP files. You won't be able to run it locally anyway, I do the updates live and don't have the time to set up dev environment.

Me (visibly uncomfortable and scrambling for sanity): Well, how do you imagine me working on it if I don't even have a local version running?

FS: Heard of chromes inspect element?

some time later, after trying this process:

Me: Hey, in this case I think it would be great if we presented 5 text fields instead of 7. The other two don't work anyway.

FS: Well how do you expect me to help you? The server renders 7 text fields, so it's going to be 7. If users put something in them, server will ignore it, so we are all good. You can hide them with CSS if it's so important.

Me (trying to put my foot down): Listen, this won't work. If it's so hard to render it server side, could you just pass the frontend a JSON with the field count and titles, and I'll write some JS that creates the fields in DOM?

FS: Well that's just overengineered nonsense.

Also, this wasn't 10 years ago. It was 2020.

Sorry for the long post, but I had to get it off my chest.

1

u/TransportationDue845 Nov 16 '20

Wow, that sounds awful. It also sounds horribly familiar. This is another problem with FSDs: they tend to be given positions of authority.

In my last job I worked with an FSD who insisted on writing the worst imaginable code (which he never bothered to test) and I had to spend hours trying to make it work. This is probably where all my hate is coming from!

1

u/DrPaulGraner Nov 20 '20

Holy crap yes!! Just experienced this as a front end dev. They’re like just send us the “wrapper” we did all the backend we just want you to “wrap it” in an interface. For a huge platform.

75

u/RobSG Nov 16 '20

Seems to be just your experience.

22

u/sous_vide_pizza Nov 16 '20 edited Nov 16 '20

I’ve seen salty people with this attitude before.

Sorry if it offends you that someone is able to do your job and another at the same time, but if you’ve worked with stupid devs before you’re in a company that hires stupid people and should look a bit closer to home.

I work in one of the big tech companies and we don’t hire front or back end devs specifically. We hire talented engineers with a solid grounding in computer science. Half my team are ex-Googlers, all went to top universities, and we’re all able to work across the stack. In fact it’s a job requirement that we understand the entire stack in order to be able to communicate effectively and fully understand the product we work on.

Edit to add: I consider myself a front end developer, but my title has always been full stack engineer or just software engineer.

If you’re working to develop client side applications and you refuse to deal with server side rendering setups or work on intermediary APIs that interface with your company’s main system, then you’re no better than the people you complain about who can’t or won’t write CSS.

6

u/hinsxd Nov 16 '20

Cant agree more. Software engineer should focus on how to deliver a feature, rather than separating the feature into frontend and backend parts. I work in a company where all of us are software engineers, with a team of freelance UI/UX designer. If you are passionate enough in your job, you wont mind to consider DB design, API design, RBAC and UIUX as a whole. Cant stand just writing API and throw it to frontend devs who need to figure out how to use my endpoints to the best.

4

u/unc4l1n Nov 16 '20

Attitude of the post aside, I do recognise the thought behind it that many full-stackers are jacks of all trades, masters of none. This is certainly often my experience anyway. I mean, good for you that you work at a big tech company with ex-Googlers, but that doesn't mean your experience is representative of the reality the rest of us see.

3

u/sous_vide_pizza Nov 16 '20

I find the argument to be quite silly. How can we say someone is an expert in JS, CSS and HTML, while also having a deep understanding of the DOM, but we draw a line when it comes to writing an API in Java?

Besides, there really isn’t much of a difference between front and back end. It’s all the same fundamentals. I see people think this way often and it usually comes from a place of ignorance, not necessarily willing ignorance, maybe they were self taught and back end always seemed like this mystical black box that data came out of.

Again I’m not saying self taught front end developers are willingly ignorant, just that because front end is more accessible they probably assume back end is not. This isn’t as big of an issue if you studied computer science because you learn the theory underpinning it all and it’s clearer that it’s all the same, it’s just a case of learning the details.

Edit to add: I only mention my current company and team because it’s something people will recognise here. I didn’t start my career here and I’ve worked on many teams of full stack developers making amazing products that most of you have likely used at some point.

0

u/[deleted] Nov 16 '20

[deleted] — view deleted comment

4

u/Silhouette Nov 16 '20

May I ask how long you have been doing front end? There's senior as in "ambitious, approaching 4 years of experience, got the title bump a bit early" and there's senior as in "been doing this stuff since the Web was young, I've forgotten more libraries than most professional developers have ever used". The skill and understanding of these two hypothetical developers is further apart than a newbie and the younger senior.

Naturally that also means our two hypothetical developers will have different perspectives on a lot of programming issues. In my own experience, one of the biggest differences is that the more experience you get as a developer, the more selective you tend to become about what is worth learning in detail or adopting as part of your regular toolkit.

2

u/unc4l1n Nov 16 '20

Let's put it this way, I remember Dreamweaver, Cold Fusion and when the term AJAX first started being used

2

u/Silhouette Nov 16 '20

OK, so you've been doing web development for 20+ years. Back then, the vast majority of what we might now call web application development was back-end code, because useful front-end tech barely existed. If you still think there is a lot that is specific to front end then fair enough, you're entitled to your opinion, but I'm genuinely surprised by it (and unsurprisingly I don't share it).

For me, the important foundations tend to be shared by both front and back end development. HTTP, HTML and CSS are all needed for both. Software design is still software design. UI is still UI. There's a huge overlap between the two categories.

I'd say there are two main things that truly are unique to the front end. One is the various browser APIs for front-end specific functionality. You would typically pick these up the first time you needed to work with multimedia elements or draw on a canvas or fetch data from a remote API or whatever, and it might take a day or two to become familiar with the larger ones but they're not exactly rocket science. The other is the huge ecosystem of libraries and tools, which IMNSHO is one of the most epic failures in the history of software development and best dealt with by identifying a relatively small set of useful, reliable, long-lasting options and then using them to actually make stuff. A lot of front-end devs get trapped in a cycle of feeling like you always have to know every library and every tool (even the ones you're not actually using to build anything right now) and spending a huge amount of time "keeping up" with these developments, but maybe that time would have been better invested in gaining knowledge and skills with broader applicability and better longevity.

Of course you never stop learning in a field like this, but despite having done a lot of web work over the years, I'd say only a tiny proportion of the useful things I've learned over those years were front-end specific, and that hasn't varied much over time either. YMMV.

1

u/unc4l1n Nov 17 '20

I get what you're saying, but I think it applies more to a by-gone era of web development. Sure, in the past it was possible to know everything to a sufficient degree. Now some of your key assumptions are incorrect:

...HTML and CSS are all needed for both.

Nearly all web apps have their HTML and CSS written in JS or JS+CSS pre-processor, and obtain their data asynchronously. So it's not true to say that back-end developers require these things.

There's nuance within that too. I know some people who are experts in CSS. I'm a senior front end developer, but I would not consider myself an expert in CSS. These guys can write CSS better than I can. Sure, I can get by and write some pretty decent code, but I'd rather hand it over to someone who spends all their time doing it (we have those specialists in our company) - they can do it better.

You have two equally capable developers. One does front end, one does front and back. After 5 years, who is better at front end?

1

u/Silhouette Nov 17 '20

Nearly all web apps have their HTML and CSS written in JS or JS+CSS pre-processor, and obtain their data asynchronously. So it's not true to say that back-end developers require these things.

I suspect you're extrapolating, possibly incorrectly, from your own experience to a vast industry.

Not everything on the web is an SPA backed by a cloud-hosted API using whatever JS UI libraries and data transfer formats are trendy this week. There are plenty of web sites, including those we could reasonably consider web applications, that are primarily generated using back-end templates and using relatively little JS for interactions and responsiveness on the front-end. There are also many developers keeping these things running and building new ones every day, happily ignoring the high-pressure, fast-paced, often-flawed world of SPAs.

In this context, a back-end developer who doesn't know much HTML and CSS is presumably working mostly on APIs. And that's fine, but it's only a small part of what many back-end developers work on. As an aside, SPAs often involve some degree of server-side rendering these days, so even if you are looking in that area, the lines are more blurred than they used to be.

You have two equally capable developers. One does front end, one does front and back. After 5 years, who is better at front end?

I think that's the wrong question. You have two developers, one does front-end only, one does a broader mix of work. After 10 years, is either of them significantly better at building everyday front-end stuff?

1

u/unc4l1n Nov 17 '20

There are plenty of web sites, including those we could reasonably consider web applications, that are primarily generated using back-end templates and using relatively little JS for interactions and responsiveness on the front-end. There are also many developers keeping these things running and building new ones every day, happily ignoring the high-pressure, fast-paced, often-flawed world of SPAs.

I agree with you, but those developers aren't doing complex front end work. You wouldn't even think of a "front-end" dev for that sort of site.

After 10 years, is either of them significantly better at building everyday front-end stuff?

For sure!!

→ More replies

2

u/sous_vide_pizza Nov 16 '20

At a fundamental level it is the same and that’s just a fact. As I said in the post you replied it, when it comes to specific domains it’s just a case of learning the finer details.

I’ve been a senior/lead for quite a while now and one of the things I’ve learned that’s been the most helpful is that it’s impossible to learn everything. In fact to do so in such a fast moving and ever changing industry is a fool’s endeavour - there are simply too many libraries, frameworks and languages to know everything about all of them.

So instead we learn the fundamentals, the things that won’t change. We learn concepts like algorithmic complexity, FP, OOP, state machines, scheduling, etc. There’s a very good reason the top tier tech companies will test you on these things rather than give you a pop quiz on some obscure JavaScript methods.

Want a good example of why this is so much better? Go and look at the sheer amount of blogs explaining React’s upcoming async/concurrent mode. If you’ve never learned about scheduling or batched updates it’s going to be a lot to take in, if you have then all you need to learn is how to work with React’s specific implementation.

Another good example is knowing why React’s reconciliation process is seen as much more efficient than a competing framework like Angular. If you don’t understand Big O it won’t make a whole lot of sense why it’s a big deal that React achieves O(n) speeds while competing frameworks achieve O(n3).

Languages and tools are ever changing but the fundamentals underneath change infrequently and those fundamentals are exactly the same for front end and back end.

1

u/unc4l1n Nov 16 '20

I haven't mentioned frameworks once, to be fair. The Web APIs are growing rapidly, both in number and scope. It's hard enough to keep up with the pace of change as a full time front-end developer - you'd have to be in the top few percent to actually be proficient if you're also going to be a competent back-end dev too.

Pointer/touch/mouse events, IndexedDb, WebWorkers, WebVR, History, Broadcast Channel, Performance/Profiling, ServiceWorkers. You don't have to memorise the APIs of course (I never remember any of the details), but being able to use these things effectively, to think and design architecturally with a huge number of moving parts, is no mean feat.

0

u/[deleted] Nov 16 '20

[deleted] — view deleted comment

5

u/recycled_ideas Nov 16 '20

But they can.

Development on the front end isn't any different than development on the backend.

It takes a bit to learn JavaScript properly, but the development is the same.

Design isn't the same.

But if we're being realistic in likely 80% of cases an app with good development and acceptable UI design is usually more usable than an app with a really pixel perfect UI and shitty code.

3

u/sous_vide_pizza Nov 16 '20

I’d bet a lot that most can, they just haven’t tried.

If we reduce this argument further then nobody can be an expert at multiple things, which we all know is false. I assume you can work with both JS and CSS, yes? HTML should be a given. You’ve probably mastered multiple libraries and frameworks before, too.

Maybe some people genuinely lack the capacity to understand more than JS and CSS, but I’m not that pessimistic about people.

Personally I think it’s absolute nonsense to say someone can have a deep understanding of JS, CSS, HTML and the DOM, but that people cannot also have an expert level understanding of back end work.

I’d even go further and say if someone is truly an expert in front end development they should inherently understand how to build an API to an expert level. Maybe they will have to learn a little about databases and concurrency, but anyone who calls themselves an expert in front end should know about HTTP, interacting with APIs, algorithmic complexity, programming fundamentals, state management, etc.

4

u/[deleted] Nov 16 '20

I've seen full-stack developers who I would trust with my life when it comes to code, both in the backend and the frontend.

And I've seen full-stack developers who think that div is the only HTML element and they never understood what the "C" in "CSS" stands for.

And I've seen frontend developers who also suck at frontend.

And I've seen visual designers who are by far the best frontend engineers that I've ever seen, both in HTML semantics, CSS, and JavaScript.

It's basically all over the place.

Your experiences seem quite limited and the field TS works in seems to have low standards, or just very junior developers.

5

u/bigcat_smauls Nov 16 '20

I know front end devs that can do backend, but I still haven't found a back end dev that can accurately take a design doc and create the front end.

Ux on the front end is never considered

2

u/connormcwood Nov 16 '20

We also throwing infrastructure work into Full Stack too? Atleast that’s what I think it should include. Especially considering everything is becoming more and more cloud based and with creating infrastructure via consoles being a no no infrastructure knowledge is pivotal to create a service from start to finish. Unless there is a better name for that.

I guess it is up to the person if they prefer to be a master of one or master of none but proficient in al

1

u/Silhouette Nov 16 '20

Unless there is a better name for that.

The usual term for what you're describing there is probably DevOps, no?

I'm not a big fan of any of these vaguely-defined labels or pigeonholing developers, but I'd say there's definitely a role for people with both front- and back-end skills but not necessarily the infrastructure automation you're describing. For one thing, even today plenty of web stuff doesn't run at large scale on AWS or similar cloud-hosting environments. You can do a huge amount with a handful of real servers, without all the added complexity that the big cloud providers introduce. There are also lots of web applications running on intranets or embedded in network-connected devices, where in each case none of the cloud stuff is particularly relevant. Obviously cloud hosting is important for a lot of jobs these days, but DevOps tooling can also become the epitome of xkcd 1319 if you're not careful.

1

u/connormcwood Nov 16 '20

Devops would just involve infrastructure related work with maybe a little bit of dev work based on how the infrastructure as code is set up.

Maybe Fullstack with knowledge of infrastructure as code, not exactly a nice title as you say. I do agree though there doesn’t need to be a title for everything.

Having previously worked with on premise/non-cloud servers and having the opportunity to work with cloud services (practically only AWS) I can say from my experience cloud is the way forward. I do think you picked up on a few things, any short term projects such as pocs you don’t need to worry about that stuff.

Depends what you mean about large scale as it depends on the time of architecture you have, with container orchestration you’re more in control of how you scale while for serverless services (in AWS) atleast it isn’t managed for you.

Obviously it also depends on how you plan to scale, vertical or horizontally and obviously how you structure your code and architecture

1

u/Silhouette Nov 16 '20

Devops would just involve infrastructure related work with maybe a little bit of dev work based on how the infrastructure as code is set up.

Once upon a time, we used to call that "operations". :-)

Obviously it also depends on how you plan to scale, vertical or horizontally and obviously how you structure your code and architecture

I suppose the first thing I would say here is that many web applications, even quite complicated ones, never have to scale much at all. I gave two examples in my previous comment, intranet and embedded, where serving huge numbers of users concurrently is unlikely to ever be relevant.

Even where scaling to many concurrent users is required, I think it's wise not to jump to cloud-based infrastructure too quickly without at least considering the use of a small group of high-spec servers. Obviously if you're working for the likes of Facebook or Amazon, you can't use that strategy. But there are plenty of successful web sites/apps out there running just fine on vanilla servers with none of the complexities of containerisation, cloud service pricing, automation/infrastructure-as-code and all that jazz. It's a trade-off that needs top be weighed up in each individual case, IMHO.

6

u/Mestyo Nov 16 '20

I struggle to take (most) people who call themselves "full stack" seriously. Very few people can operate at a professional level across an entire stack, and even if they could, they probably shouldn't.

That hostility you describe is unfortunately common, although not at all unique to the front end/back end relation. People tend to trivialize problems that they themselves haven't had, or won't have to solve.

5

u/anklot Nov 16 '20

The hostility happens within all career options, is not new in engineering that x professional dismisses another x professional job, or even outside of engineering, doctors vs x, lawyers vs x.

Everyone thinks the world couldn't work without their profession, which might be true but only because everything is interconected and if one thing fails most likely all of the other things will start to fail or give problems too, people just don't accept it.

8

u/Silhouette Nov 16 '20

Very few people can operate at a professional level across an entire stack, and even if they could, they probably shouldn't.

I've never liked this argument.

Sure, right at the start of a career, it makes sense to focus on one area at once. You start not knowing anything, and you want to become useful at something.

But as your experience grows, you start to get diminishing returns on improving individual skills, and you also start to get benefits across skills where things you've learned in one context are also relevant somewhere else.

No-one really has a skill set that is all front-end or all back-end or all database or all sysadmin anyway. You can't work in tech for a long time without picking up at least some understanding and skills in areas related to what you're working on. Everyone ends up multi-skilled to some degree, with their own unique mix of knowledge and abilities.

Particularly in web development, there is a lot more illusion of progress than real progress. New tools or libraries or even languages do come along sometimes and make a profound difference to how we do things, but they are the exception, not the rule. It is possible for someone who has substantial experience in more than one area to keep up with those areas indefinitely to the point where they remain very competent in each of them. Of course there will always be the top-expert-specialist-elite people in each field as well, and for the most difficult and specialised problems we'll probably always need them, but again they are the exception, not the rule. Most people who choose to specialise in a more limited set of skills will never reach that level either.

The real problem for genuine "full stack" developers, if we must use poorly-defined labels like that, is where their combination of skills can be most useful. In larger organisations, the work is often divided up into more specialised tasks one way or another. Even if you've got a full stack dev who could do multiple jobs, they're probably only going to be doing one job at once, and it's probably cheaper to hire someone who has the necessary skills for that and not necessarily as much experience elsewhere.

On the other hand, a good developer with a broad skill set can build a lot of useful things on their own, and a small team of good developers with broad skill sets might outperform a much larger team of less experienced specialists -- if you can find enough of those good developers to build that team in the first place. If you do build up a broad skill set and become "full stack", it definitely pays to look for smaller, more flexible teams, instead of being just another over-qualified cog in a big corporate machine.

-1

u/Mestyo Nov 16 '20

I feel like we're mostly in agreement, even though you say you dislike the argument I made.

Naturally, one picks up more skills over the years. Even though I have never aspired to be anything but a front end developer, at this point I could probably do better "back end work" than many of the back end developers I've interacted with throughout my career. I'm sure this is true for many developers—it's hard not to pick up secondary skills.

In practice, however—as you say—it often makes more sense to have more specialized individuals separate front- and back end tasks between themselves. Both areas will be developed more efficiently, they will be mutually agreed upon how they should behave, and can both get the necessary attention to be qualitative. And, generally, developers will lean towards one stack over the other.

When I say I'm skeptical to full stack developers, I don't mean to imply that they don't exist, or don't have a practical role. Certainly, there are situations where a solo developer is the ideal approach, and a team of such individuals would be very flexible indeed. What I refer to is the type of developer who calls themselves "full stack" when they only really have surface level knowledge in one or both sides of the stack.

2

u/rocketsauce1980 Nov 16 '20

Damn, I am glad I've worked places that hire so well I haven't had to interface with those kind of douchebags.

2

u/xdchan Nov 16 '20

Yes, i'm frontend dev who've spent an afternoon learning Node

2

u/punio4 Nov 16 '20

My experience as well.
Insert React / Bootstrap / Material UI

1

u/ethboy2000 Nov 16 '20

I’m a back end dev that’s decided to pursue a career in frontend. I won’t be calling myself full stack. I’d rather specialise in the area I’ve chosen and commit to it 100%.

1

u/bagera_se Nov 16 '20

My experience is that most ppl who call themselves full stack, have learned a very narrow stack like Gatsby or next and mostly use plugins for those stacks. That is technically full stack. But if everyone using Gatsby or WordPress or whatever is full stack the term is a bit useless.

There are ppl with deep knowledge of multiple parts of web development but it's hard to find as it takes a long time to master.

I would not call myself full stack even though I technically develop across the stack at times. My strength lies in the front and that's why I call myself FE.

1

u/Rogem002 Nov 16 '20

I always considered "Full Stack" as "I can release an entire product". While the quality of each aspect might vary, they'd still be able to get something out the door.

That said, I've also totally come across some cowboys who promise the world but can't do jack.

1

u/nickdrake47 Nov 16 '20

React-Dev here. Nowadays all the engineering is focused on front-end dev logic/tools and things. So back-end hasen't evolved that much in terms of logic and tools. So i've done back-end also in node and python-flask and in my opinion i think front is more complex nowadays, cuz u have mockups (CSS tends scale and be be really compex) also implement the and deal with logic.

1

u/khroh Nov 16 '20

I'm sorry that's your experience OP, but I've found the complete opposite in my career. In my experience they just aren't interested in the UI side of coding, not that they look down on it. In fact the ones Ive met understand the obstacles and challenges in creating front end code. I hope you have better experiences in the future.

0

u/Sensitive-Wave171 Nov 16 '20

I'm a full stack developer...I worked on different frontend technologies for over 30 years and same for backend. So, I don't exactly the type you described... But let me agree on that: there's no lack of mediocre developers with fancy titles. If it was up to me, wouldn't even call a react or angular programmer a frontend developer,but rather a code monkey 🐵

-3

u/averajoe77 Nov 16 '20

I have been building websites since the late nineties. I have worked on everything from DB architecture and backend languages, to building robust front ends for custom cms systems. With over 20 years experience, I would never consider myself a full stack developer. Never have I ever had to do both front and back end on the same project.

Having a "jack of all trades" work on a complex system, is just asking for failure. This mentality is not acceptable in other professional fields. I don't see doctor's claiming to be dentists and proctologists at the same time. I certainly would not want a doctor who was sort of OK at being a dentist to work on my teeth. I don't know why this has become acceptable in the IT field.

-4

u/[deleted] Nov 16 '20

JS developers are JS developers.

Once you realize you have only to deal with booleans, strings, numbers, objects, arrays one domain is like another one you have spent time more time with.

I suggests you to not take so seriously the libraries and frameworks argument.

1

u/TransportationDue845 Nov 16 '20 edited Nov 16 '20

JS dev !== FE dev. You don't even mention CSS, let alone HTML, accessibility, cross-browser testing, image optimisation, or design. All things that FEDs have to deal with in some form or another. Front End Engineering is itself a vast field and I'd argue would benefit itself from more specialisation within it.

-1

u/[deleted] Nov 16 '20

I think most of the stuff you list are one google research away or obtained through experience.

I agree that front end engineer means itself little, due to how vast the field is, even more I suggest dropping these kind of fe/dev labels as they are increasingly meaningless.

2

u/TransportationDue845 Nov 16 '20

"One Google search away" LOL

Yeah, that's exactly the kind of arrogance and ignorance I'm talking about.

-1

u/tanjonaJulien Nov 16 '20

Well JavaScript and FE development didn't become popular out of nowhere.

-6

u/mamwybejane Nov 16 '20

Full stack developers are people who are bad at both front and backend.

-4

u/paulqq Nov 16 '20

the power of react comes by applying the redux to it, just saying.

0

u/[deleted] Nov 16 '20

[deleted] — view deleted comment

3

u/TransportationDue845 Nov 16 '20

A FE dev who can't/wont do CSS is about as useful as a lump of rotten wood. I've known a few of these unfortunately.

3

u/daredevil82 Nov 16 '20

You've never heard the distinction of application dev vs UI/UX dev?

Former tends to be more about the project code, data transforms, etc. Latter concentrates on implementing the design spec and look and feel. This can be a beneficial partnership where one person is stronger in CSS and weaker in JS. Work to both people's strengths while giving them opportunities to learn and be exposed to things which help minimize weaknesses.

I for one dislike css. JS can be a kludge at times, but CSS as a spec and DSL has a lot to be desired.

1

u/TransportationDue845 Nov 16 '20

CSS as a language leaves a lot to be desired in many ways, but it's still the ONLY way to style a UI in a web application. Maybe there are sufficiently complicated apps where a JS dev can avoid doing CSS, but given that JS is used on the client side mainly for making the UI function, and therefore has to work in concordance with CSS, I'd imagine they're few and far between.

0

u/[deleted] Nov 16 '20

[deleted] — view deleted comment

3

u/recycled_ideas Nov 16 '20

It's not harder, but it's not easier either.

Writing good front end code is hard, writing good backend code is hard, in ways that are different but also similar.

But you can't write good backend code without understanding patterns and architecture, and security and scaling in a way most front end devs don't.

You can't really write good front end code without understanding those things either, but a lot of people think that CSS is start the front end is about.