As a fullstack developer I don’t appreciate you calling me out like this. Write an efficient SQL query you framework monkeys.
But also, this is very true.
DROP TABLE
That seems like a pretty efficient query!
I see you’ve met my boy Bobby
I hope you’ve learned to sanitize your inputs
Where’s my trusty CASCADE?
Not understanding SQL (and in some cases NoSQL DBs) and the underlying database are a reason that so many full stack devs suck. Just because they use an ORM, they think the database work is magically solved, until they realize it’s just doing what they’re telling it to do and their lack of DB understanding has created an awful database structure. And then a DBA comes in, and then the entire ORM layer has to be scrapped because it’s trash, so on and so forth. A full stack engineer doesn’t have to be a DBA, but they sure as hell need to know what the ORM is doing to their data they are CRUDing
And then a DBA comes in
I’m convinced that’s a mythical being. In my 20+ years of experience I’ve never encountered one.
They don’t write sql they just use some god awful orm or cram it all into a nosql db.
Backend Requirements: “When x,y goes in, I want x+y to come out!” - Okay
Frontend Requirements: “Well it needs to be more user-friendly, and have this rockstar wow effect” - Yea wtf are you even talking about? You want me to add random glitter explosions, because I found a script for that, that’s pretty ‘wow effect’ right?
Actually the front end stuff is more like “we need to make the ‘sign in’ button bigger. No one can click it because it’s tiny, and it’s in German.”
I spent years as a mobile developer and the thing that always drove me the most nuts was being handed a software design with lots of tiny buttons that were nearly impossible to tap with a finger. I generally implemented the UI by increasing the size of the tappable regions (without increasing the apparent size of the buttons) making it actually usable, but one time the designer discovered that I was doing this and went apeshit and convinced the project manager to order me to undo all this and make the tappable regions the same size as the buttons. The grounds for this was that implementing the larger tappable regions would take too much extra time - despite the fact that this had already been done and it took additional time to undo it.
So wait you actually had to undo it all? What kind of designer would make mobile buttons small?
I usually just do what they requested and when they come to complain I just tell them “well, you’re the one who requested this” and pull up receipts. My DM to myself on Slack is filled with screenshots and links to confirmations for bullshit requests that the product team made.
My DM to myself on Slack is filled with screenshots and links to confirmations for bullshit requests that the product team made.
How good does it feel when you pull out those screenshots to say, ‘no u’?
Someone who has tiny fingers
What kind of designer would make mobile buttons small?
Have you ever used a mobile app? Every commercial mobile app I’ve ever used has tons of tiny fucking buttons.
Fucking apeshit craze-balls, makes sense, business as usual.
Marketing want us to add more typos to make the site feel more “friendly”.
As a SaaS founder I’m now wondering if this actually works. Will have to talk to the front-end devs on Monday.
Please don’t
Plese donot
Isn’t our main audience German? If you wanted non German stuff you shoulda asked for regional translations. Not only is that a change request, but you’re gonna be pushing the release window by months.
But it doesn’t even say “Sign in” in German. It says “Das Bootton” because someone thought it would be funny and never changed it.
That someone was RIGHT!
Man, if only backend demands were algebraically tractable. Often they’re related to frontend demands that may or may not make backend sense, since the frontend is all users see.
Yeah if you have shitty UX people frontend will just built what they’re told. Or actually more often, you could have really talented UX people and management decisions are like “needs more buy now buttons, the 3 visible on the screen aren’t enough.” Shit flows downhill
Yeah that’s not a real back end
6 E Q U J 5 wow!
I can’t be the only person who thinks “full stack” translates to “master of nothing.” One of the best career moves I ever made was shrug off the pressure to go full stack, and dedicate myself to backend only.
Full stack means we do it because nobody else will.
I feel seen.
I might get that sentence embroidered on a pillow.
You don’t have to be a full stack dev for that to happen to you
No, but when it does happen, you’ll probably turn into one.
When it happens? That happened to me a long time ago. I’m still a backend developer. I can create UIs and I can spin up and manage docker CI infrastructure but I sure as hell don’t want to. A properly run company team should have separate professionals for UX, front end, back end, sysadmin, etc. Just because I am capable of doing those things does not mean I should.
Just because I am capable of doing those things does not mean I should.
This is the crux of why so many companies, especially smaller and medium sized ones, are a hot mess. capable of << good at, but of course it’s cheaper to just get johnny to do everything.
I think knowing about frontend is important for a senior or higher level engineer. I would expect someone at that level to be able to contribute where necessary, and know enough to make sane decisions and know when those decisions impact backend/frontend. But to be equally good at both isn’t reasonable
A backend engineer that has adequately put in the time to operate at a senior level, will more than likely have worked closely enough with FE to check those boxes. They should be familiar with technical design and processes, which if done effectively, teach an engineer to ask those questions.
“I’m capable of not making a fool of myself with UI” does not equate to “I’m a full stack developer”
As someone who likes to dip their toes into everything, I feel a bit called out by “master of nothing”.
My apologies. My intention wasn’t a dig at engineers themselves, but rather the trend of employers seeking “full stack” engineers, and the implications of them shopping for a singular engineer willing to do the job of multiple engineers-- IE be taken advantage of, and the first to be let go, because of a lack of specialized domain knowledge, etc.
No worries. Wasn’t really offended. ;)
Fuck that employer behavior, though.
The truth is that there is value in both a generalist and a specialist.
It just means he can’t do it by himself.
Yours won’t be perfect, but you can do the whole thing by yourself.
Why would I want to do it by myself, in a professional team setting?
In my case, it was to increase the number of available job opportunities rather than any genuine interest.
My company started with full stack devs only and we’ve transitioned to specialized back end and front end since we realized that 1 specialized BE Engineer and 1 specialized FE Engineer can work faster with better quality than having 2 Full Stack Engineers.
Thank goodness issues respect the FE/BE break out.
deleted by creator
In my experience it’s normally frontend programmers that go full stack.
Exactly, this meme is backwards
It works in either direction.
That would make sense. They’re both very different from the other.
In my experience, that bottom image is equally applicable when Front End devs go Full Stack lol
Frontend dev here, can confirm. Last week I had to look at some Java code and was instantly greeted by some AbstractFactoryBuilderImpl. Nightmare fuel if you ask me.
Yeah, it’s accurate both ways
Most disciplines get more specialized as they evolve. Full Stack goes against that trend, and this meme points at the problem with that. I don’t think it’s going to last.
Overspecialisation can also suck eggs. Interdisciplinary research is trendy in science for the that reason. Even I occasionally read a paper and can see they’re missing some basic fact from another field or subfield that totally undercuts their result.
This meme is backwards
le front end not actual work amirite
This is the dumbest trope. It’s not the same kind of job, or even very coding-ish, but all the frontends I’ve made are horrifyingly ugly, and I hated making them.
As a full stack developer (more experienced in back end) working on a full stack task at work I can confirm, yes, this is very true lmao.
Both should be the bottom picture to be honest.
This is me.
I would say I’m a fairly proficient dev overall, though on this one project I had to work the frontend. It was shit. Everything was shit.
The backend was a steaming pile of crap, and all of the implications of terrible design decisions were offloaded to the frontend. The frontend became the source of every single delay as it was where all crap started to surface. They were ignoring it, so besides frontend communication was also crap. Eventually, in line with ignoring all other issues, they sacked me.
Long story short, backend devs: treat your FE devs well.
It’s always Patrick, so both are the same
this is what starter kits are for lol
@LinearArray that 2nd image is me.
