A: So are you the programmers of this software?

B: Yeah, I did the front end

A: Oh it looks so fantastic! It is simple, yet beautiful and responsive. Truly great design, you are so talented!

C: I did the back end...

A: Oh, you mean the server stuff?

C: Yeah

A: Niceeee

Designers always get the love.

Maybe they think backend is equivalent to a godown where you dump stuff, rather than a hotel kitchen :-/

@stackodev yup, even more than fullstack developers

@stackodev and the hate.

It goes both ways

I identify with c. Especially when the convo at one of my last jobs was

A: good job B on fixing that performance bug.
B: actually that was C. I just did the front end. It was a database issue.
A: and it looks great (leaves)

Oh how much I can relate to this as back-ender

Dont care about the opinion of people that know nothing. Measure your self bij the opinion of your peers and there feedback. De client is just one that helps you pay the bill.

Well that's a bit different at my current project. The PM forwards bugs and requests to me and I then assign them to the frontend developer or myself. When it's done I report back and it's like " B,C - Great work! " most of the time

@chasb96 Have you looked at Static websites ?

When my friends ask why I'm studying front end; show them this post

In most of the projects I have been working on, it was always the opposite. Backend work was considered “a real deal” that takes long time, while front end was “just put some buttons and animations on top of it, how long can it take, a week?”. While in reality it was a client side portal with shitload front end logic and the api layer might just be proxying some data to and from an external system. Not saying they didn’t do good job; but it was unfair that they could get 2-3 weeks on whatever they needed, while fe was always rushed.