preface: I'm fucking exhausted and angry.

Why does everyone assume I know how to do frontend?
Why am I always the design girl?
Why?

You hire me to do backend. STOP GIVING ME FRONTEND DESIGN CRAP. I HATE IT.

AND STOP GODDAMN YELLING AT ME FOR NOT MAKING SOMETHING RESPONSIVE.

I DON'T KNOW HOW.

yes i can learn, but I CAN'T FUCKING PICK UP A SKILL LIKE THAT IN A DAY. Also, I fucking hate it.

STICK IT UP YOUR (min-width: 1400px) ASS.

But seriously, I've spent 13 hours today figuring out completely new things (webpack, susy, express.js, cloudinary, responsive best practices, more webpack) because the boss is in panic-mode (his preferred state) and wants this project released last monday.

guess what? it isn't done.
because i still don't know how to do everything. and ofc there's nobody to ask because there never fucking is.

Seriously, boss-man. hire a fucking designer, and stop being an illiterate sales goon while you're at it. ffs.

Frontend Dev: That's not possible in Frontend, we should do it in Backend.
Backend Dev: That's not possible in Backend, we should do it in Frontend.

-- CIVIL WAR --

We need more JS devs for our frontend.
After half a year of PM complaining that he doesn’t find devs, he finally came back to us:
„Sorry guys, I found two devs, but they are not Java developers, they only do JavaScript“
Me:
Team:
*both speechless*
TeamLead: „... wait, you searched for Java devs half a year?“

Sometimes I feel frontend development is like ancient magic:

Backend Dev: Oh no, I can't align this DIV properly.
FE Dev: No worries!
* Casts Flexius Boxius on the DIV *
* Div aligns slightly better *
BE Dev: But it's not centered!
FE Dev: No worries!
* Casts Marginis Automaticus! *
* Rolls natural 1 *
* Everything collapses *
* Website is on fire *
* Product owner cries *
FE Dev: No worries!
* Casts Flexius Boxius level 5 on the parent div *
* Everything looks beautiful *
* People are in awe *
FE Dev: You are welcome!
* Adjusts his robe and leaves *

Just got BUGS list from our Client and fuck- 95% of bugs are not even bugs :|

- No, changing the (not pre-decided) verbiage is not a bug
- Adding two more pages in the app is not a bug (what the fuck :|)
- No, APK file not running in iPhone is not a bug (goddamn :|)
- No, adding these "fuckin new" functionalities is not a bug (seriously ? :/)

AND

Mr "used to be a good coder" PM,

Getting "504 Timeout Gateway" error because Server is temporarily down is NOT a fuckin frontend bug

And No, writing Javascript with a proper design architecture is not a "complicated" way of coding
and fuckin No, Global variables and functions without any architecture don't make the programming "kind of better"

ps: And VB dot net is not a fuckin scripting language, VBScript is.

Thank you,
"buggy average coder"

Guy: dot net dev (C#) on windows. (desktop + server)
Team(not his team, he just happened to sit next to us): php/frontend devs and Linux (server) people.

Team: starting a new project! We'll have to see what framework to use and what server :D
Guy: i know it's none of my business...... but I'd recommend dot net and windows server!
Me: respectfully, that hardly makes sense, you know our skillset/field... i understand that it works for you but it doesn't really for us :).
Next to that we'd rather not use windows for security reasons.

It's fine if that happens once.

When it happened for the 1748472823'th time, I had a real hard time controlling myself.

After I submitted a code review:

Coworker: What did you mean with this comment?

Me: **translating the comment to Portuguese** Your Footer component isn't rendering any footer element.

Coworker: **blank stare** what?

Me: There is no footer tag here. **points to Footer component**

Coworker: **computing... found approximate result** I'm rendering the Footer here. **shows me where the Footer component is being rendered**

Me: **internal facepalm** Yes, I know, but I'm not talking about that. I'm saying that inside the Footer component you should be rendering a footer element.

Coworker: **segmentation fault** what?

And then I had to explain that there is an HTML footer element. To a mid level frontend developer (or so they say).

HTML is not only divs, for fuck sake.

The last two frontend devs I interviewed.

First:

He had 15 some years of experience, but couldn't answer our most basic of technical questions, we stopped asking after the first couple.

Based on a technical test I got the impression that he couldn't distinguish between backend and frontend.

So, I posed a simple question "Have you interfaced with REST API'S using Javascript before?"

Which lead him to talk about arrays. I shit you not he droned on about arrays for five minutes.

"I have experience using big array, small arrays, breaking big arrays into littler arrays and putting arrays inside other arrays."

Never been in an interview situation where I've had to hold back laughter before. We refer to him as the array expert.

His technical knowledge was lacking, and he was nervous, so he just waffled. I managed to ease his nerves and the interview wasn't terrible after that, but he wasn't what we were looking for.

Second:

This was a phone interview.

It started off OK he was clearly walking somewhere and was half preoccupied. Turns out he was on his way back from the shop after buying rolling papers (we'd heard him in the shop asking for Rizla), and he was preoccupied with rolling a joint.

We started asking some basic technical questions at which point he faked that he'd seen a fight in the street.

We then called him back five minutes later you could hear him smoking "ah, that's better". After that the interview was OK, not what we were looking for, but not bad.

Top tip: If you require a joint to get through a phone interview, roll and smoke it before hand.

1. Move to new house
2. Setup electricity account to auto-pay every month
3. Wait
4. Receive "disconnect" notice from electric provder
5. WTF
6. Call. Oh, yeah, our website doesn't tell you that you have to pay your first month's bill before you can setup auto-pay. It's in the fine print.

Okay people, here's my rant - if you manage a website that supports auto-pay and you're not PREVENTING your customers from signing up for auto-pay until there is a $0 balance in the account, then you're doing something wrong. Don't let your customers think they're about to loose their electric service because of a frontend guardrails issue.

Interviewer: "Hi, we are searching for a junior frontend dev with 1 year of experience and strong skills with Angular".
Me: "I have never used Angular before but I have 4 years of experience, It's not a problem for me to study it and use it quickly".
Interviewer: "Eh no, we are searching for someone with very strong Angular skills".
Me: "That's fine, but sorry how can a junior dev with just 1 year of experience have already strong skills with Angular? He must have also strong skills with JavaScript in general and It's quite impossible".
Interviewer: "Ehh... ehm.... ehmm..."

A story of the backend dev. from our client:

"I used !important once now I'm not allowed to do frontend anymore :("

Frontend team : We pushed our code. Please give instructions regarding integration with Backend.

Me : Alright. I'll provide you the API docs and you can continue with integration.

F : But that's your job. No?

Me (didn't want to argue) : I'll look into it. Let me check out the frontend till then.

* Goes on to see the frontend *

I am kidding you not, that moth*rf*ck*r pushed an entire template along with dummy text.

Me : Hey! This doesn't seem right. It's just a template you got off the internet.

F : Yeah! That's what I have to do. To put on the dynamic content from database is your work. Don't put your responsibilities on me!!

Are you f*cking kidding me?! Do your work right or I am reporting you to the team lead!

Meanwhile, team lead : *sips coffee. Disappears for months*

Bastards!

I just got handed a legacy php web project... Full of vulnerabilities... And it's using only mysql_ functions... Not only it's not OOP, there is not even a single class...

How good it's coded: User profiles are created manually by the frontend dev as htmls, and then the past php dev implemented them as links etc in the current page.

This is how I feel:

Recently i had to interview a guy with 10 years of frontend experience for a react developer role

Me : Do you know what ecmascript is ?
Him : Yes
Me : Which version would you prefer to use and why ?
Him : I dont use it. I am more comfortable with JavaScript.
Me : (totally confused) 😶
Him : (trying to be oversmart) I know you young guys prefer to use these fancy frameworks because you dont know how powerful raw javascript is.
Me : (Trying hard to not "react") Ok.

How would you "react" to this ?

Hey @Root! I know you won't have time to finish Ticket A before holiday vacation, so work on Ticket B instead.

I finished Ticket A in time. except for converting/fixing some horrible spaghetti monstrosity. More or less: "we overwrote this gem's middleware and now it calls back into our codebase under specific circumstances, and then calls the gem again, which calls the middleware again." Wtf? It's an atrocity against rationality.

The second day after vacation:

Hey @Root, drop Ticket B and work on Ticket C instead. Can you knock this out quick, like before friday? ... Uh, sure. It looks easy.

Ticket C was not easy. Ticket C was a frontend CSS job to add a print button, and for unknown reasons, none of the styles apply during printing. The only code involved is adding a button with a single line of javascript: `window.print()`, so why give it to the chick who hasn't been given a frontend ticket in over a year? Why not give it to the frontend guy who does this all day every day? Because "do it anyway," that's why.

And in somewhere between 13 (now 5) minutes and two hours from now, I'm going to have a 1:1 with my boss to discuss the week. Having finished almost all of Ticket A won't matter because it's not a "recent priority" -- despite it being a priority before, and a lot of work. I've made no progress on Ticket B due to interruptions (and a total and complete lack of caring because I'm burned out and quite literally can no longer care), and no progress on ticket C because... it's all horribly broken and therefore not quick. I assigned it to Mr. Frontend, which I'll probably get chewed out for.

So, my 1:1 with bossmang today is going to be awful. And the worst part of all: I'm out of rum! Which means sobriety in the face of adversity! :<

but like, wtf. Just give me a ticket and let me work on it until it's done. Stop changing the damn priorities every other freaking day!

Working on the privacy site.

DAMN frontend can be a FUCKING pain in the ass!

I JUST WANT TO GET A SIMPLE BOOTSTRAP PAGE WORKING, IS THAT TOO MUCH TO ASK FROM A BACKENDER? 😭

Me talking to a recruiter (even though I am not looking for a job)

Me: If I walk into an interview, and they ask me to reverse a binary tree for a frontend Reac or Vue position or something along those lines, I will end the call and/or walk away from it.

Him: I get similar feelings from other programmers, I don't quite understand why the notion is as common

Me: Because it is fucking useless, it servers no purpose to a dev to know about that when building frontends with react, I link my github profile, for which they can find advanced backend-frontend related projects, compiler and interpreter projects, plus the title I currently have at my workplace and a bunch of other shit, I am not interviewing for a teaching position at an institute, but an actual place of work, for which if they want to know about DS and A they can review my profile which has a repo of DS and A in about 5 different languages including plain C++. I do not need to be offended by such notions since they server no purpose on the frontend, and neither do other devs. If anything it should be a casual conversation during the interview, not a basis for employment.

Recruiter: .........thank you for explaining this to me, I am sure I can bring it up to the agencies doing the reviews and interviews. Are you still interested?

Me: Are they going to give me a coding assignment for a project or a bs question like what I mentioned?

Him: I don't know

Me: then I am not interested

> Manager: Why does service X behaves Y way? It should do Z instead.
> Me: *explains why*
> Manager: I don't understand this...
> Me: *explains it in more simple terms and shorter sentences*
> Manager: I'm still not sure I get it.
> Me: It is like this because of a third party provider and we can't change anything for the same reason. Also it is working like this for half a decade now.
> Manager: Ok, I get it. So please fix the service, it should do Z instead of Y.
> Me: *facepalm* Sorry, I can't. Ask (frontend guy), maybe he can help you.
> Frontend guy a bit later: ┌П┐(ಠ_ಠ)

Hey devRanters! A tiny update regarding the privacy tips etc site.

So as ewpratten doesn't have much time right now, I'm doing frontend as well for now.

Since some people also offered to contribute content, which I did not expect, I am also writing an invite/registration (based on invites) as we speak. So, this way, I can invite anyone (based on email address) into the CMS so that they can contribute content as well!

Regarding frontend, I'm introducing a system with icons. Icons? Yes, icons, let me explain:

Every application/service will get a couple of default filtering thingies. (not like clicking something and it'll filter anything out, yet) It'll enable users to see what an application does or does not. What the FUCK do you mean? Alright, so, as example, lets say open source. next to each application (read application/service) listed, there will be an open source icon. If the application is open source, this icon will be green, otherwise it will be red.

This will allow for a quick way of filtering stuff out.

For example, if you're only looking for open source stuff, you can quickly filter stuff out where the open source icon is red!

This will apply to things as open sourceness, metadata saving, usage of good crypto technology and so on. So you'll be able to quickly filter out the stuff you want to use (by eyes) through those filters!

Please let me know what you think and if you have ideas, I'll be glad to hear them!

Public service announcement: Do not get married to your language, tools, or way of doing things. If there's an easier solution to something, try it before dismissing it. No language is perfect, and dumping everything on the responsibility of an API or framework can cause more headache then solve it.

Case in point: I love Java for backend programming, but node.js is a better solution to frontend programming then depending on JSP's and HTML within the same Java project. Less things go wrong and it's easier to debug issues.

There is no best programming language. Only best practices and using the right tool for the right job.

#exceptC++fuckthatlanguage

:^)

I applied for a backend job. Somehow i ended up doing frontend. Ok whatever the pay is alright and i dont mind doing js. But then i see the backend team doing absolute horseshit, stacking up overhead and not even fucking documenting the endpoints, i get mad.
And now our sysadmin left so there is no fucking server and i cant run locally because of 9trillion config files (remember the overhead part?) and the pm is nagging me to get the site done WHEN THERE IS NO FUCKING SERVER. WHAT DO YOU WANT FROM ME, SET IT ALL UP AGAIN? THATS NOT MY FUCKING JOB YOU IMBECILE FUCKFACE.

Project manager, a few months ago: "why did you do this task? It's all wrong. It's a backend task, not a frontend task so you shouldn't have done it. Don't do it again."

PM, today, regarding the same task in a different project: "why didn't you do this task? The project isn't complete without it. It isn't right. You should have done it."

Are you fucking serious? If we do it it's wrong, if we don't do it it's wrong too. So why should I bother? Seriously, fuck you you piece of shit.

As a frontend dev, i love watching our backend devs sometimes go like "hey come on it's just css I can do it real quick, let me do it this time" and get super frustrated with failure. Buddy, one of the reasons frontend is not so easy is that it can be real fucking annoying. I'm keeping my distance and respect for your side so stay the fuck away from my dance floor.

"Hi xxx, please stop asking me the same question. I've answered it 4 times already via email, slack and in person on our zoom calls, over the past 2 weeks. I do not own the ticket and have no idea of the status or the dates. Ask the owner."

- slack response I was forced to write this morning to the guy my company put in charge of the entire product (mobile, multiple backends, frontend etc.).

Fucking hell, how much I hate frontend!

Getting a tab system to work (bulma only exists out of css) has been taking me ages and its still not working.

I love nice interfaces but I just want to work on the backend 😭

!rant

So I was digging through some old projects of mine and I came across this lil pokedex project I had started but not finished sometime last year. The frontend is great but sadly the backend was non-existent because I didnt have that knowledge yet.

But now that I do, I'm thinking of building the backend and just keeping the frontend i have with some tweaks here and there. Anyways, I'm pretty proud of this project.

I'm so sick of all these fat frontend websites.

Transferring dozens of megabytes of mostly unused libraries is not acceptable.

A browser tab crunching up CPU time because everything must be "beautifully animated" (🤢) and processed without involving page reloads/backend is not acceptable.

A response time of over a second is not acceptable.

Cryptic error messages and random popups asking you to reload your page, not acceptable.

Sticky elements/popups breaking access on small screens is not acceptable.

Running hundreds of ajax calls per minute as heartbeats/probes
and crashing the page when the internet has a hiccup, not acceptable.

Fuck Asana, Fuck Twitch, Fuck LinkedIn, Fuck Youtube, Fuck the dozens of other SPAs which unload their truckload of diarrhea into a tab, yet fail to load crucial functionality about half of the time.

Fuck any page that breaks when you block Facebook, Doubleclick, Twitter or Google Analytics. To hell with websites depending on cookies or javascript loaders to display anything.

I want webpages to be interactive informational documents again.

Fuck off with your apps.

If you want to make an app, learn to use a real language, and get the fuck out of my browser.

Would the web be better off, if there was zero frontend scripting? There would be HTML5 video/audio, but zero client side JS.

Browsers wouldn't understand script tags, they wouldn't have javascript engines, and they wouldn't have to worry about new standards and deprecations.

Browsers would be MUCH more secure, and use way less memory and CPU resources.

What would we really be missing?

If you build less bloated pages, you would not really need ajax calls, page reloads would be cheap. Animated menus do not add anything functionally, and could be done using css as well. Complicated webapps... well maybe those should just be desktop/mobile apps.

Pages would contain less annoying elements, no tracking or crypto mining scripts, no mouse tracking, no exploitative spam alerts.

Why don't we just deprecate JS in the browser, completely?

I think it would be worth it.

What's the point of using a framework if you don't use any of its features!? What the heck, I have to fix this damn web frontend that is so broken in many ways.

Instead of using an authentication middleware, every single view has the same block of code to check if a user is authenticated. Instead of templates, they used static HTML/JavaScript files and they passed data to pages through cookies.

The "REST" API is so messed up, nothing is resource-oriented, HTTP methods are chosen randomly as well as status codes. They are returning "412 Precondition Failed" instead of a plain simple "401 Unauthorized" when you're not authenticated! What the hell, did they even bother to check what 412 is about when they copied and pasted it from a crappy website!? I would never come up with 412, not even in my scariest nightmare.

What kind of drugs were they using when they wrote such code? Oh dear, I need a vacation...

Project manager: We have 13weeks for this project. We have promised the client.

Me: okay, why wasnt I consulted on that commitment?

Project Manager: yeah.... we have to do it

Me: okay, if we have 2 dedicated backend and one full time frontend - ONLY on this project.

Project manager: (with the face of lies) yes yes sure we can do that.

6 weeks later, after continuous interruptions. Frontend is behind because he was only on the project to an amount of 2 weeks of the 6 weeks.

Project manager: Are we still on time?

Me: *looks around for prank cameras* no the f#*k we not

Project manager: can we put in weekends?

Me: its 2019 bro, that ain't happening

*But because I am a nice guy, and dont like taking Ls, we will have it ready. Just not gonna tell the project manager, he deserves a few sleepless nights *

Me: I can't get a grasp on frontend and nice interfaces...

Friend: it's actually quite easy:
Rule 1 -Don't reinvent the wheel..
Rule 2 -That does not look like a wheel.

Made my day :D

"That's a frontend problem."

Really? And you call yourself the engineering lead? Oh right, "frontend is not engineering", was that it? Ok, thanks a lot for the help, you can continue licking your balls now. I don't know why I still bother trying to ask you for advice.

TFW someone tells you that you're not a "real frontend developer" and then repeatedly asks for CSS help... 😒

Me: 'im doing frontend here, i wont bother with the server stuff'
Pm: 'ok'

...

Me: 'here i finished the full stack because the backend team is a bunch of jackasses'
Pm: 'did you set up the server?'

...

Me: 'no because its not my job'
Pm: 'you have to do it'

Sometimes it makes me wonder if he even knows how programming works.

Hello! A tiny update on the privacy site thingy. (linuxxx here yas).

I've finished the preview page (description of what will be on the site really) and slowly preparing for deployment.
In the mean time, since @ewpratten is very busy at the moment, I'm giving the frontend part a shot myself! Working on the general layout/presentation right now and I will show a preview as soon as I have anything solid enough to show :).

Also working on the custom CMS which is going well!

I am kind of hestitant to publish the preview page because I am not a frontender and I know that I'll get all criticism on here so please, please go easy on me! Also, just in general, if you find any kind of flaws in the web app or wherever, please report them to me! As for frontend, I won't fix anything because I've got bigger priorities (like creating the actual site itself xD) but general feedback would be appreciated :). And as I said, I'm a backender so don't judge me too hard on the frontend!

Alright now let's gather some courage to actually publish this thing 😅

I was getting a freelancer job to do some backend work for a company in India that is working for a huge company in Saudi Arabia.

The customer in india was my primary contact, I wasn't allowed to talk to the guys in Saudi Arabia. My contact, we'll call him Aman, asks if i can do frontend too. I decline. Now what follows were 4 weeks of backend work during which Aman called me 10-15 times per day via skype to ask me how I was progressing, and if "insert spec here" was already done. He even called me in the middle of the night, well aware of the different time zones.

But in the end all the work is done, Aman is happy. I request payment.

Aman: We can't pay you yet, you didn't do the frontend!
Me: I'm not doing frontend.
Aman: It's just a few simple changes and then we're done.
Me: Gnnn, fuck it, what do you need?
Aman: Our customer would like the frontend to look better.
Me: Ok, so what exactly should look better?
Aman: All of it.
Me: Do you have any specs?
Aman: No just make it look more modern.
Me: So you want me to rework the whole frontend? That's not just a few simple changes...
Aman: How long would you need?
Me: I actually don't do that kind of work.
Aman: We pay you double your hourly rate if you do this and finish it fast.

(This is were I should have just said no... but the greed...)

Me: Ok, but it will take me about 3 weeks to do that.
Aman: OK.
Me: Do you have any preferences as to how it should look?
Aman: No, just surprise us.

(After this sentence I really should have gotten the hell out of Dodge)

After working 3 weeks changing over 20.000 lines of CSS and most of the HTML I present Aman with the changes.

Aman: No our customer doesn't like the changes. Can you make a different version?
Me: What doesn't he like, any specifics, coloring, styling of lists or the buttons?
Aman: He doesn't like the whole thing. Please make us another version.
Me: Ok, you are the customer, but it would really help if you give me some pointers as to how it should look like.
Aman: Just do your best.
Me: ..., ok, that's helpful.

2 weeks later...

Aman: No our customer liked the version before better. But could you make it look more modern.
Me: *Bangs head against wall repeatedly*
Me: What do you mean by modern?
Aman: It should look more modern, as a whole.
Me: Ok, I get that, but could you give me an example?
Aman: Sends me a screenshot of the overview screen with all the elements encircled and modern written beside them.

1 week later...

Aman: The customer has decided, he likes the original version best. Can you undo all the changes?
Me: Sure but that'll take like 1 hour.
Aman: Oh by the way we were asked by accounting why the price for this project was so high?
Me: *hugh* *gnn* what?
Aman: Well at the beginning, you estimated the backend and frontend work to be done in 4 weeks.
Me: The frontend was never part of the original estimate.
Aman: Can you do anything concerning your hourly rate, so that we can get back to the original pricing.
Me: *make a mental note to never work with an intermediary company in india again and cancels the job requesting the due payment*

Luckily I got paid the full amount but not before having another 10 Skype call with Aman...

I lost my job 😅 tbh did me a favour. I was backend, this guy was frontend and was a typical opinionated JavaScript, magpie dev and I just did not give 2 fucks about what he thought was “amazballs” and we had a small tiff, we’ll he was arguing, I was trying to do my job and I just didn’t care enough about his feelings on the subject, forget what it was about but I think it was trivial. But anyway, I was let go soon after 😅

Last year at work we started migrating our backend from PHP on a dedicated server to Node.js on AWS lamda functions

We went from 10 second calls to 70ms calls...

At this point our frontend is not even ready for this kind of speed 😅

Me:
* I wanna make a website
* I'm good at backend
* I suck at frontend

Friend:
* I wanna make a website
* I suck at backend
* I'm good at frontend

Initial though: Match made in heaven
Now: FFS Wordpress is not the kind of frontend I had in mind.

git commit suicide.txt -m "It was a nice thought before it was put into action"

Why its so hard to understand that - not always... - frontend devs will give you a sweet ui with medium back end and back end devs are gonna give you a medium ui with sweet back end?

Why can't we just do what nature made us good for and work in collaboration?

Fuck

That feel when you’re asked to share work you’re proud of and you’re not proud of anything.

Or rather, you are... but they’re programs written in C/C++ and you’re interviewing for a mostly frontend gig in React.

Everyone’s a “fullstack” until they have to make a button go all the way to the right

Oldschool CSS was not much fun, but I never understood how this made it any better:

<div><div><div><div><div><div>Bootstrap</div></div></div></div></div></div>

I always forgot a row, had cols inside of cols, forgot how form-groups worked, or found other ways of messing up the whole layout.

Instead of complex CSS, there was now this new complex language entirely expressed through the nesting of layers upon layers of divs. It was like LISP's brackets, but more verbose.

That was the moment I realized that fullstack is bullshit, that there are intrinsic talent differences between frontend and backend devs, and that it's OK to focus on a narrower but deeper field.

Today I learned that someone wrote a Python interpreter in JavaScript called Brython. So now you can include a framework to write shitty code in a buggy framework and tell your users to throw more hardware at it.

The guy I heard this from also believed that his code would somehow be "compiled" rather than what's essentially a framework be loaded and then execute code in a language not native to the browser...

So now you can write JavaScript where it doesn't belong in Node and write Python where it doesn't belong through a framework. Frontend and backend are so passé, we might as well start calling it fluid instead.

FULLSCHTAK!!!

🙂🔫

Be me, making a self hosted website-blog thing because why not

making the backend: yeah cool, easy, ive been doing this stuff for a while

making a frontend: ehh, some template will do fine, im not that great at js

making an admin page: yay this is actually fun

setting up portforwarding on my router to my pi: fucking piece of shit work already dammit

"If you use a css framework splat splat splat splat bullshit bullshit bullshit"

Listen fam, I write apps that a good portion of the time will be used internally by the company I represent or work for. They don't give 2 flying fucks if I write an entire webpack ecosystem for them to push out assets and 10k outher bs shit in to their frontend end. They just care that shit connects properly to their backend and it spits out the information they need, which 9 times out of 10 does not require a lot of the shit y'all cry about.

Bootstrap will suffice, bulma will suffice. I don't neckbeard over simple shit like this.

Stupid javascript.
Stupid hoisting-oblivious "frontend devs."
Stupid browser-specific javascript behavior.
Stupid thrown-together javascript minifier that literally only strips out whitespace and comments.
Stupid poorly-written javascript spamming my api.

Time to rewrite it. Grumble grumble. Soo not how I wanted to spend my morning-turn-afternoon.

Leading to the last but not least:
Stupid me forgetting javascript's quirks.

We had a sprint where we removed some fields from the signup page, in order not to "scare users off" with the amount of information requested. Quite a few changes in frontend and backend alike.

Only now in the final day of the sprint (where we're supposed to deploy the changes) do we realize some of that information is actually required by the payment processor, and likely for very predictable *legal* reasons which I even questioned during planning.

so I was working on a new frontend design for our desktop app when I told my boss

me: this will not look good in a lower resolution. I think we should reconsider

boss: thats ok. its the customer's fault for using that kind of resolution

after a week

boss: we should reconsider the design. the customers are complaining about resolution issues

Marketing pushed deadline for release one week earlier. That sucks.

What sucks even more is that frontend was not ready, but our frontend guy promised to take a look over the weekend and finish it. Thats cool we might make.

What sucks is that he fixed one small issue on Sunday 9PM and left the whole thing unusable.

So guess who was googling till 4am how to do stuff in bloody javascript?

In the end, I beleive I did a decent job and we ca release some kind of alpha and get rid of my dirty hacks later. That's how you get technical debt.

Now lets see what my boss thinks about it and if we are really going to release it or if I'm going to kill somebody.

After 2 interviews and an make home and pitch project...

'Sorry we were not really looking for a new frontend developer'

Like... How?!?!

Me:
*spins up Vscode*
*spins up postman*
*opens terminal, spins up docker*
*spins up frontend dev server*
*spins up backend dev server*
*opens new chrome window with not less than 20 tabs*

My 4year old 8gb RAM Core-i3 PC (barely fighting for her life):

I am the sole frontend developer in my project. I have only 6 months of professional coding experience. Just got a call from a person who used to lead me (she is still my lead, technically, but not very much involved in the dev process (management’s decision, not hers)).

She said that a concern has been raised that there have been large number of frontend issues which they (she didn’t specify, I am guessing management) haven’t seen before.

What do you think is the “large number”? Let me tell you. It’s 4.

2 of which are minor CSS issues that couldn’t have been anticipated while coding. They are runtime issues.

One of the 4 is a both frontend and backend issue.

And the last one is a fucking change request!

1 player, many responsibilities, slight issues, RAISE CONCERN - That’s management for you.

Fuck them, I guess.

On top of that, a concern I raised in front of the management regarding the management is not so much of a priority for them. I have a feeling that the concern they raised is just them being a jerk because I raised a concern in the first place.

Fuck them, again!

And again!

Just happened to stumble across an indian job offer. They want a fulltime php dev for 20k indian moneys a month. Thats not even $300. Are they... Are they serious or is this just a bad company? Because thats less then what i made with a part time frontend job when i was just a beginner. Is this a trend in india to underpay people by this much?

So I work as a "Web Development Lead"
Which means I lead (frontend,backend and infrastructure teams)
Also I am in charge of infrastructure or devops or whatever you call it, which means I handle production issues, dev and staging environments,...etc

and I am a team of one, and today I asked for a day off because it's my wife's birthday

and suddenly everyone is blocked, everything is on fire, and the phone is not stopping ringing, I had to go out of the cinema theater to answer the non-stopping calls

I AM ASKING FOR A SINGLE DAY, A FUCKING DAY, EVEN IF SOMEONE IS BLOCKED SO WHAT IT'S NOT EVEN A DAY I ONLY NEED 6 HOURS

IS TO TOO MUCH FUCKING TO ASK

Why the fuck does people who teach in professional colleges doesn't have the mindset to update their godamnn fucking dinosaur knowledge to the least basics of modern technology.

Had to do this mini-project for uni, and the languages allowed included java, python, php or any similar frontend tools for creating desktop app or web app. I planned on taking React + Express cz apparently that'll fall in the category.

Now she starts yelling at my project saying its not allowed and when I fucking asked her "can I use node.js which is basically javascript" she said yes.

And for gods sake she has a Masters degree and phd but doesn't even know what's the difference between get and post request!! Fed up with this college shit!!

Why do so many companies think that frontend work can be stuffed at the end of the product development right before a release is expected.

And to top it off, expect all things to be working, smooth, animating, responsive, crisp, fast with 100 fucking lighthouse score.

🖕 To everyone who thinks frontend work is meh!, Not real programming and similar. Fuck you!

Oh gosh.. i can finally understand the CV and application nightmare stories... We're getting new people in, and there are quite a few interesting ones.

0) pages of randomly placed info. PAGES. I'm lost in there!!

1) no basic info whatsoever. Like, no nationality(we're recruiting internationally), no birthdate, barely his name and email. I know that the first ones are not really needed for the job, but they're still customary.

2) entry level back and/or frontend job. This guy's a phd graduate, working research with big data in a bio-something department. We're a web startup.

3) there are some listing so much unrelevant stuff, I'm not even sure if they meant to apply to us.

4) (my favourite) email subject: application, email body: empty, attached: short_application.doc ("hi, this is an application to the posted job. Best regards, Name") WAIT WHAT?

A discussion about writing tests for frontend applications.

Context: my frontend coworkers don't write tests, at all. Yeah, really. Our testing process is very manual. We test manually when developing. We test manually when reviewing code. After merging, the application is deployed to a staging server and the design team does a QA Sprint. Lots of manual testing and some bugs still crawl by.

So I decided to start pushing my coworkers to start writing tests. One of the reasons I constantly hear them say to not write tests in the frontend is: "It's not worth the time, because design keeps changing, which means we have to take time to fix the tests. Time that we usually don't have."

I've been thinking about this a lot and it seems to me that this is more related to bad tests than to tests in general.

Tests should not break with design changes (small changes at least). They should test funcionality, not how things look. A form should not break if the submit button's style changes, so why should its tests fail? I also think that tests help save time, as they prevent some back and forth because of bugs.

Writing good tests is the hard part. Tests that cover what's really important and aren't frail and break with things that shouldn't break them. What (and how) should we test? And what shouldn't be tested?

Writing them fast is another hard thing. Are you doing it right if they take more time to write than the actual code?

What do you think about this? Do you write tests for your frontend applications? What do you test? How much time do you spend writing tests? What are your testing tools/frameworks?

FUCK YOU BUSINESS GUY
FUCK YOUR SCOPE CREEP
SOLO DEV AINT GIVING U 20 FEATURES IN ONE MOTHERFUCKING WEEK

Seriously, though. Being a solo full-stackq developer who can do both frontend (react, redux) and backend (feathers, node) does NOT mean you have twice the manpower to accomplish all of your shitty shit. Just because you have an idea does NOT mean I have to implement all of it. You don't even have a motherfucking specifications for me, yet you expect me to deliver shitloads of complete fucking feature in a fucking week. This is not a fucking joke. I am NOT your mother fucking tool. I need time to build my stack, design and perfect the interface. I don't want a shitty motherfucking product on my fucking portfolio.

*dies inside*

Joined my current company as a Frontend Engineer 2 years back. They recently got funded and started hiring with a higher salary range. Not to brag but I'm pretty good at my job with 6yr of experience but my current salary makes me a lower mid-level engineer now and I'm the only frontend guy here.

So, now they're asking me to take interviews of the applicants who are applying for the senior position.

Why do people have to be such an assholes to the employees, man?

Hello World! First post here. I'm literally done with frontend stuff. I want to design code, not to code design. Unless it's Processing. I find it cute. So.. I have a somewhat handy grasp on C++ because of a class in electronics course, Python seems quite easy to catch. I'm totally new to programming. I'd like to get into software, game development and android development (but I would like to do things cross-platform).
Which paths, resources, languages, useful books, videos, or just anything would you recommend?

To be fair, I have no coding friends so mentorship or simply finding code buddies would be great. 💜

I’m tired of all these profane “frontend developers” who do nothing but get cheap internet points by shitting on web technologies.

Bitch, NPM is just a package manager. That’s what it is. Anyone who ever used a package manager already knows how to use NPM.

Here on devrant, there at your workplace, people hear nothing but bitching when you open your mouth. You always need a “solid task description” and “best practices”. You always need somebody else to do your job for you. Frontend is the area where you have to constantly switch between heavy, performance-oriented coding, UX and graphic design while remaining in a dynamic environment that is called “web”, no wonder why you can’t do that. Instead of bitching, you could just present your own solution you designed with just a little bit of product-oriented thinking. But noooo, you fucking bother designers whenever you’re not sure about “how many pixels is that padding”.

You can only be barely productive (and only with a frozen spec) but can never take the lead just once.

In the 80s your kind of approaches were doubted, by the 90s they were dead. In 2020s they’re straight up laughable.

And don’t get me started on CSS. You have to be an absolute buffoon of a developer to not know how to use a DECLARATIVE tool that don’t even require real structural thinking.

No wonder why you praise php. You throw shit all over the place and tell everybody that you’re a “sociopath” and you don’t need that “stupid frontend” and “stupid users”. But you know what? Any real backend or embedded dev would’ve laughed at your face.

Because backend developers are respected.

You’re not.

"Don't you like the new site? (:"
I mean yeah, it's an upgrade from what was done in 2011 with 2007 recycled code.
But now the first access takes almost 10 seconds.
10
seconds.
Was fucking WordPress necessary?
We went from a hotel booking PHP template to a blogging template.
60+ freaking Mb of shit, not just content but *shit*. (from the admin panel, only 3 of the 10+ sections are needed)
At least they won't bother me now about the main page frontend.
Oh wait, they do. So I had to learn how to hack the theme header behaviour because of course, cute boy WordPress couldn't care less on how the header behaves. I see more hacks incoming of fucking course.

Man I fucking hate WordPress.

Legit considering quitting my job and going back to my old workplace.

Fucking getting real tired of fucking around with html and css on the daily.

The school is fucking crashing down on our shitty as web services. But my manager (as much as we love her) is forcing everyone to double time on a rather stupid project that keeps constantly changing on the daily.

I am so fucking tired of it

Not sure if you'd call this an insecurity but regardless; frontend.

Much of the stuff I develop is meant to be user/privacy friendly.
Like, at the moment I'm developing an end-to-end encrypted notes web application. The backend is a fucking breeze, the frontend is hell for me. I'm managing mostly but for example, I need to implement a specific thing/feature right now and while the backend would take me about 15-30 minutes, I've been only just thinking about how I'm going to do this frontend wise for the past few fucking hours.

My JavaScript skills are quite alright, html is manageable, css only the basics.

And before people tell me to just learn it; I. Fucking. Hate. Frontend. Development. My motivation for this is below zero.

But, most of the shit I write depends on frontend regardless!

Rant. (I love and respect all people! Especially developers.)

You frontend imbecils! I just can’t deal with you any more. I’ve had it.

Stop-inventing-new-components-where-there-are-fully-developed-and-working-concepts!

I mean. Just fucking stop! If I see another worthless datetime picker with an ”innovative” design I am going to hunt you down and freaking scream in your face.

And make fucking buttons look like tappable/clickable. It’s not fucking hard! Imbecils.

Oh, ooo, look at me, I am a frontend developer and I am in UX la-la land and what I am doing is sooo hard. Fuck off with your fucking moving gradients and n:th-child childish playground.

”Yeah, I exchanged the spinner…”

Fuck you. Your not contributing. Nobody cares! We’re not doing anything for the business by having a web which can be seen on a fucking telephone. EVERYBODY IS SITTING WITH SEVERAL GIANT MONITORS AND A FUCKING WORKSTATION FOR THIS. NOBODY ASKED FOR IT. AND YOU SPEND COUNTLESS HOURS ON IT.

”Yeah, I made the site work on ipad”

Please. Why? It’s not worth anything. Zero value.

”Yeah, the toggle component is now changed since we started to use the biddle-flipflup lib and it works almost the same”

No! NO! It does not work ”almost” the same. The psychology of the toggle is now wastly different. What was On before now looks like Off and it is fucking worse!!!

Imbecils. I hate you.

And no, I can’t do your fucking work! And I know that you do other non-ui stuff as well sometimes… but anyway… I have no interest to be in that clusterfuck that modern frontend is today. It was really fucking bad twenty years ago and it is just as bad today and you are not helping.

”I’ve improved the button so now it aaaaalmost does not look like a button. But I am getting there!”

Fuck you.

Just wanna to share my story:

I just quit my job 2 months ago to ramp up my own startup. I will be funded with 2k Euro per month for 1 year to prepare the founding of my startup. Basicly that means i got one year to build backend/frontend/app. I have a friend that is doing some nontech related stuff like business development and shit. Sounds good until now i guess.
But:
Developing all that stuff in a one man show as a junior-like developer is really hard. I did not find another dev who wanted to join me as a sideproject or something.

Do you guys think thats even possible to ramp up all this by myself or am i to optimistic? I mean, i learn a lot atm, but i am a bit scared to fail too.

That should not be whining or shit, just gathering some input of you guys.

(excuse typos and stuff as i am not a native speaker :) )

Yay. I was yet again asked to make a whole module that is meant to compete with stuff companies have made who have funding of millions - without even a designer to help out. I'm the single frontend guy in the team.

"Let's make our website like that super beautiful website we saw that actually paid a designer, UI/UX guy, interaction designer and graphic guy. But let's not hire any of them. Who needs them anyway? Such a waste of money which their high fees"

I guess I'll just take "inspiration" from Pinterest/dribbble/behance

We don't have to be afraid of AI becoming self-concious and eradicating entire humanity in the near future.

Example 1: Amazon ads. You buy a TV and start receiving ads for YET ANOTHER FUCKING TV. Just in case you'd need a second/third/∞ TV on the same day.

Example 2: Recruiter bot Mail. I HOPE it's a mass mail bot and not a real human being ;)

"we're looking for PHP developers"

SELECT * FROM candidates WHERE experience IN ('PHP')
Gives
+10 to intelligence
+5% to skynet training speed

"we're looking for Java developers"

SELECT * FROM candidates WHERE experience IN ('Java')
Gives
+20 to intelligence
+10% to skynet training speed

"we're looking for frontend developers working with Angular."

SELECT * FROM candidates WHERE projects IN ('frontend') AND experience IN ('Angular')
Gives
+40 to intelligence
+20% to skynet training speed

"we're looking for QA Engineers ready to relocate to Ukraine or Cyprus"

SELECT * FROM candidates WHERE experience IN ('QA') AND location NOT IN (any country with higher living standard, lower living costs and no war)
Gives
+80 to intelligence
+40% to skynet training speed

Example 3: Alexa understands me only if I'm drunk.

So as all of you web developers know. If you are stepping into the world of web development you stepping into a world of unlimited possibilities, opportunities and adventure.

The flip side is that you step into a world of unlimited choices, tools, best practices, tutorials etc.

Since even for a veteran programmer, this is a little overwhelming, I'd like to take the opportunity to ask you guys for advice.

I know that 'there is no best' and that everything 'depends on what you want to achieve'. So how about just say the pro's and cons or when to use and when not to use. Or why you prefer one over another. Everything is allowed! :D

Maybe it will help others too. Start a nice, professional discussion:)

These are the parts I'd like advice about:

- frontend: what frameworks, libraries
- backend: language, framework, good practice
- server: OS, proxy (nginx, Apache, passenger), extra tips (like don't use root user)
- extras: git, GitHub, docker, anything

Thanks in advance everyone willing to help!:)

Also, if you only know frontend or backend. No worries, just tell me about your specialism!

Found an answer on Quora discouraging to learn Javascript because "it's not as important as php". It was a question about frontend development. Soooo 2000

I applied for a frontend dev position.
The HR sent me a mail with details for MERN developer position (Full-stack) and asked me do an assignment with frontend and backend 🤔
I requested to clarify if I'm supposed to do only frontend as that's the position I applied for.
No response on that. They got back and requested me to schedule an interview.
I have worked with NodeJS before but I primarily work on the frontend, still I went along with it anyway.
I aced the first two rounds, but for the final round they emphasized on the backend and then it went downhill. At the end they said I was really good on the frontend but for that position they needed someone particularly with expertise on the backend. 🤷‍♂️
Well, I didn't intend to work Full-stack anyway.
They wanted me do everything and also lead the team and mentor juniors and take ownership of multiple projects.
I mean, why would I want to work the job of two people (or more) and not get paid that much 🤨

The biggest lesson I learned in Frontend Dev is: listen to users, not clients.

There are so many rants about stupid ass clients on here, and when you let clients treat you like that, it's kind of your own fault. Look at how people use your interfaces and you will immediately see what's bullshit about them. When you have user behavior as an argument basis, clients will listen to you.

I’ve been interviewing with a startup for a Frontend Engineer role. In the interview they said they didn’t have a designer, that their founder and other devs do the design work. I thought “ok so they are still putting something together and don’t care much if the UI is crappy”, and still proceeded with it. I do the take-home test, it took a lot more than the 1-2 hours they said it should take (these estimates never seem realistic), I thought I did a pretty good job and send it back to them. I then got an email back from one of the founders, they really liked the code and my approach, but the UX was not good enough. He asked if I would be willing to iterate on it if given some direction? The direction: design your own version of our product. I refused. I thought this was a developer position, not a designer position.

more of my favorite "about" sections from various users:

Jilano
"nothing."

Humble like a monk.

kindawonderful
"This user likes to keep secrets about himself."

Aw, hes shy!

molaram
"Part time evil corporation hater & armed infidel trying to blow off some steam."

Is that you Elliot?

dmonkey
"Computer Science student and Math lover."

Your love of math is suspect. I have not seen you participate in any of my math shitposting.

And under his skills
"I was ending up becoming a front-end developer, now I'm thinking to become a farmer after uni."

The total state of frontend in 2021. "Fuck it, I'd rather shovel horse shit than learn another
framework!"

Have you tried Horseshit.JS for that?

What about shove.js?

Product Manager: We’re assigning you to the Guest Checkout project.

I look at the Guest Checkout epic in JIRA and see it only includes frontend scope. Nothing about backend implementation.

I also find an older ticket about guest checkout. It was written by the former Product Manager. It explicitly says our admin switch for guest checkout no longer works because rebuilt checkout to use react. Why does no one bother to check the backlog??? I found this just by searching “guest checkout.”

Me: Um, our website doesn’t support guest checkout.

PM: What?! But the admin has a guest checkout option that can be turned on and off.

Me: Those admin options only apply if you’re still using the out-of-the-box solution for the e-commerce platform. Remember how we rebuilt checkout using React? We didn’t build it to support guest checkout. That admin switch doesn’t work anymore. We can ask a backend dev to confirm.

I check the code. The code that relates to the admin switch for guest checkout no longer exists. It’s a dead switch.

BE Dev: We made a lot of customizations since we purchased the e-commerce solution. So yeah, that guest checkout switch doesn’t work.

PM: [to me] …Our BE devs are busy with other projects. Can you do the backend for guest checkout?

😳

Me: You realize I’m just a frontend dev with only some backend knowledge, right? I’m not even close to fullstack. And you want me to architect an entire guest checkout flow? That will work with our current checkout experience? And that is HIPPA compliant? On top of doing the frontend?

What a silly end of the week. Have to continue developing at a project a student started at our company. Today I had a phone conference with the client. They told me there where missing several data. At first I thought it is only a frontend issue but now I know it is a database issue so I have to work through several database procedures which are all undocumented and the student who build those is not reachable. Business integration ftw

(As a freelancer I was asked to do a couple of tasks on legacy code)

Let’s check this code, how bad can it be?

- all of the following: unreadable mess, no auto linting

- tests: some are there cause there’s not enough automation, others are poorly named
- frontend: somehow a genius made a react component for every variable in the store which only passes the variable to the child (wtf)
- backend: death by best practices
- ci/cd: “we have it but it’s broken”

Let’s fucking goooo 😎

Diagnosis: my therapist is getting rich
Chances to not cry tonight: close to zero

At least they pay well 🤷‍♂️

How do you guys deal with "senior" devs that want to use you because they're not so "senior"???

Situation:

There's this SR Frontend developer that keeps asking me for "suggestions" to modernize the frontend.

This dev, was asked a very simple ticket involving some JS and CSS.

I had to do the JS and this dev modified a VENDOR CSS (that was all she did)

She logged 3d6h of figuring out the ticket and "doing a bunch of cross browser testing"

I logged 2 hours to see what to do and implementing the change.

Now she is asking me to join in a group so "we" can come up with a plan.

I hate how people bullshit their way up

Boss only likes stuff he can see and that looks pretty. Doesn't understand code, servers, containers, DBs, etc. Praise is attributed by something looking nice in the frontend, whether or not it does crazy stuff behind the scenes.

Spent a week working on a project whilst boss was away. Got to about Thursday and thought, oh poop, I've built all this API stuff, but not much frontend. So I panic built frontend screens with no functionality just so I had something to show.

Wish I had another dev to share backend progress with (and code review)...

Today my boss told me to work more properly, because the massive feature I'm working is only halfway done.

Well thank you very much, obviously it's only halfway done yet. I'm responsible for the backend and the development for the frontend started today, by another guy who was working on another stuff until now. And I'm pretty sure we agreed that I will only do the backend...

Thanks for the uncalled critique. Great way to make me feel like my work is not appreciated. This motivated me very much to work the whole on the integration.

Imagine developing a frontend for 2 months.

And then one day, PM says, that we have a critical library that we need to integrate with. There is no other alternative (apparently).

And then you check the library, and see, that it's written in a completely different language, that we can't really integrate with.

Project restarts and you get blamed, for not mentioning this earlier.

Yay!

PHP is the best framework for VSCode.

Now that I have your attention... Have you written a technical article? I'm thinking of writing something frontend related but not sure what topic to pick.

I'd love to hear about your experience and any tips you may have :D

Idiots. Just... Fucking Idiots.

Junior Frontend dev got a feature to implement. Decided to add a field to a set of mongo collections. I'm the responsible adult for those collections. Talked to the junior - told it, "don't do that, you will lose the data you are adding later". Junior says "will not happen", and goes on to try and prove It is "Right". Problem? Junior is an Idiot. did not trigger the data loss scenario. So... Junior got his TL to talk to the RND manager. And those Idiots Decided that the implementation will go forward as is.

Data loss will happen. QA will not find it. Only the client will experience the data loss, and complain....

Fuck JavaScript, seriously I have spent the last 8 hours trying to build a fucking basic search application that would take me < 1 hour in any other fucking programming language on the planet. I AM FUCKING DONE WITH THIS SHIT. I'd rather pay some dude with a long ass fucking beard who calls himself a "Frontend Engineer" WHATEVER THE FUCK THAT MEANS. Because my backend oriented brain cannot fucking handle all of the frameworks, and modules, and different versions of the same fucking language. Plus its like JavaScript was designed so that you can't not write spaghetti code. FUCK THIS. I'm going back to writing static fucking template code that is used by a fucking backend language that only changes every few fucking years, not every month.

Have a great day. :)

So I had a meeting with a client, some time ago, asking for my expertise on rebuilding their websites frontend and backend within a month. I offered a very low price (as I am a student), which included 40 hours of work for 30$ an hour (normal price is ~120$). And done within 2 months. He turned it down by saying, that the price was 4 times too high... Clients are so demanding, but not willing to pay for their needs. He haven't found another yet. This was 2 months ago.

This is not a troll q, im gebuinely interested.

What sets spa frameworks (say react) apart from a templating engine and some dom fuckery? To me it seems they are all just syntactic sugar on top of these two very basic things (plus routing), but admittedly im not a frontend dev so im asking more experienced people here.

Frontend and backend do not go hand in hand always

I decided to quit my job. I was supposedly hired as an Android developer, but during the past few months I found myself doing everything except Android development: SQL scritps, frontend web development, backend web development, RESTful API's, DBA, release engineering... There's nothig wrong about being versatile, it's actually fun, but I wasn't doing what I really wanted to do and, most importantly, the manager didn't appreciate the fact that I was doing things that I'm not supposed to do, and not only that, I was doing it just as good as some full time web devs who do nothing but web development in the company. I'm pissed off. They probably believe the next Android dev they hire will do all the shit I was doing, accepting the same pay. Fuck them.

WTH...
While styling some frontend stuff with LESS, I experienced that on one page template the <header> was not displaying the given line-height eventhough the whole fscking code was 1:1 identical with the other template in which everything was fine. I checked EVERYTHING... caching, URL, source, classes, open / wrong tags, HEAD, ... I even did a diff compare. NO FSCKING DIFFERENCE!
After one hour of pulling out hair I suddenly saw that in the faulty template file 2 lines were missing:

<!DOCTYPE html>
<html lang="devRantLang">

WHOEVER DID THIS: YOU ARE FSCKING STUPID!!! (it was me...)

When I signed up for the technical college and heard that we would have media tech classes, I was expecting frontend stuff like HTML, CSS and JS, not how to make folders and change the font in notepad. Fuck.

Thought I would only do frontend-stuff when I started working. Boy I was wrong. I thought it would be easy coding in a real company and not just in schoolprojects, boy I was way out in the blue. But when your code works and is actually used by people, I never could've imagined that would feel so good!

I literally dont use any other code editor other than intellij. Yes not even your fucking vscode. I code frontend in intellij! I code angular and nextjs in intellij!! Intellij literally has everything anything else has plus way more. Intellisense is also much better. Theres also been a major update yesterday and everything is so much faster and smarter. And theme is way better looking. I will dick ride intellij till death do us apart!!!!

Not a rant but I'm not sure if I made the right choice. I got really curious this year in cloud infrastructure and started studying for my AWS Solutions Architect Exam. The company I work for (large company) allows me to switch roles/teams. Last week I was so bored with frontend I requested to switch to the Platform engineering team. The Engineer manager slacked me this morning....

PE Manager: I'll see you at standup this morning.

Me: Cool ill be there at 9, where is it? By the cafe?

PE Manager: No, in hell. Glad you joined the team 😃

What did I get myself into.

Rant from a previous gig I just remembered that reignited my fury lol

Suddenly, CSV exports became massively critical to our product's success. "They were always part of the plan, if we don't have them the product is a failure". Plot twist, they were NOT always part of the plan. And our backend is not at all designed for querying the combinations of data you're asking for.

Nevermind we've been entirely focused these last few months on making the new user experience as slick as possible because "our customers want cake, not meat and potatoes". Forget the fact that, in order to meet the deadlines, my team coupled the backend a little too much with the needs of the frontend because otherwise integrations took too long. We NEED fucking CSV exports of everything you can fucking imagine.

No. Fuck you. If you want it, it's gonna take at least 2 engineers and a month, and according to you we only have a few weeks of runway. No, I'm not compromising jack shit, this is the reality we live in. This is going to go nuclear in production if we don't do it right. Either give us the month and bankrupt the company, or fucking drop it.

Or...you could go cry to the frontend team for solutions. And convince them to page through ALL of the data and generate CSVs in the fucking browser. Sure, it sort of works in QA with the miniscule amount of data we have there, but how'd that work out for you in prod?

Jesus fucking christ why are you people such incompetent morons, and how the fuck did you become executives??

First rant from my new job.
I got a position as backend-dev in a startup and for now i'm learning angular. Yes, you read that correctly, because the frontend-team is short-staffed i decided to switch teams. We are 3 people and neither one has sufficient angular-experience (the framework was a management decision).
First of all i got confused because we use slack and trello but the frontend-lead decided to do some stuff via google-spreadsheet too. Then we didn't have any code in our repository until yesterday. I tried to check out the repository after that, did an npm-install but when running ng serve i got an error "css-file not found". It turns out you had to download some files from the official website and put them in the unversioned node_modules directory. It was the teamlead's decision to do so and me and my coworker got really annoyed when we tried to set up everything on our end. But that's not all, yesterday the other dev's merged their first versions of the project. But not via git, that is way to mainstream. The coworker had to upload his code into the cloud and the teamlead copied the files into the project folder.
Aside from that the code already isn't the best, some things should be done differently imo and we have credentials in the code (not in some separate files, but in an if-else-clause that checks node.env.production).

We'll have a discussion about this tomorrow, let's hope things can be straightened out.

"Yes, the work could have finished way earlier. But it's easy, and I would have probably been bored of it and left earlier"

Finally got the reason why our fucking CTO couldn't create a fucking stable Backend for almost a year while the frontend team got all the slack because certain things are still not functioning well and while the marketing team every fucking time got their face red while showing the demo because the fucking api is not stable. Seriously, we wasted a whole year just because you could write something more interesting and enjoyable. Fuck you. Never been this willing to murder someone.

Context: A simple booking platform. No need for creating a complex distributed system while our userbase may not even be in million even on a peak season.

And he laughily commented maintaining it would be a headache.

I could seriously kill someone right now.

One day my colleague says that React Js is used for frontend as well as backend. I did not agree with him also he blames that Backend API’s also can be created using React Js. I could not believe because as per I know React Js is a library for frontend not for Backend. Still, some other colleagues supported him because he is the senior developer I am an intermediate developer.

Then I ask some of my friends who are currently working on React Js, Can we use React Js for the backend? And the next day I went office and talk to my colleague that I could not found that React JS can be used for backend and backend API. And he replied You can use nodejs. Oh! Man But I think Node and React are different tools.

Lets get some shit crystal clear:

- Angular is amazing.
- If you're complaining about it, then you're not experienced enough with it and you need to learn more
- Im using Angular for years, i built personal, professional and client projects with Angular as frontend and got paid thousands of USD
- I have never had any problems with angular in terms of performance, slow load time or insufficient documentation
- Angular is perfect for large projects. The structure is extremely robust and Easily lets you scale the project no matter how complex the project is
- You can have a trillion components and still be able to easily understand what each component does and add up to it because of how all the components are modularized and decoupled

I hate Sass.

When installing all NPM dependencies with npm i, it's always quick, but not with sass. Ooooh myy goood. It starts compiling. It always misses something. Your node version is always not what sass needs. It pulls out gyp which requires some native shit. The build is never reproducible, it always fails with some horrible two mile long poorly-formatted stacktrace that is just gibberish.

More than that, sass is just poorly designed tool used by frontend fuckboys to write imperative, nonstandard, non-maintainable styles. If you know shit about css, you don't need sass.

I'm so happy it's going to die along with gulp. Webpack and css modules are here.

Yes, css-in-js that has a runtime penalty is also shit. If you like its syntax but dislike everything else, use Linaria. It has no runtime penalty and looks just like other css-in-js solutions.

Frontend-Developer steps into my office and tells me that my code does not work and that he has checked everything.

>me confused, cause I did it every time so<

So I spent one hour to check and recompile my code again and again. I created more console outputs than my whole last week... And at the end... It was not my fault, I had to find out that the front- and backcolor of his label are the same so the text was not visible.

Dear frontend developer,

I love your designs and most of the time you make a really good job, but please check something like this before you confuse a backend developer for one hour and let him doubt about himself...

Thanks!

Sincerely,
Your backend dev

Why the fuck they keep insisting a backend developer to do frontend shit?

No fucking shit I'm slow on this crap. And i told them several times it's not my forte.And they keep inisting to keeping a high standard blah blah blah

Ffs just hire a frontend already.

I'll find another job. I don't care at this point.

let RANT = $state(true);

Don't even get me started on frontend engineering right now. It's like the wild wild west out here, with no rules or regulations.

I mean seriously, what is going on with frontend engineering these days? It's like we're stuck in some sort of weird limbo state where nothing seems to make sense and everything is a struggle. And to top it all off, the project I've been working on for the past two years has the same damn issues as an existing codebase that I was hoping to leave behind.

For some reason the npm build runs when container starts. Are you kidding me? Every time I have to restart the app, I have to wait for 30+ minutes just for the damn thing to build. And what's worse, it's not even a complex app. It's a simple frontend for a research website. So why the heck does it take so long to build?

I'll tell you why, because some genius thought it would be a good idea to build the entire codebase every time the container starts. And I have no doubt that this same genius probably thought it would be efficient and time-saving. Well let me tell you, it's neither efficient nor time-saving. It's just plain infuriating.

And don't even get me started on the codebase itself. It's like a labyrinth of tangled and convoluted code (multiple versions of React and now rewriting on Nextjs). Trying to make even the simplest changes feels like unraveling a giant knot (every freaking component have it's only style and everything from React is being used - hooks, Redux, whatever else is popular). And heaven forbid you make a mistake, because then you have to wait another 30 minutes for the whole thing to build and see if your change even worked.

And let's not forget about the old codebase that is still being used, because the new one wasn't ready in time. So we're constantly having to switch back and forth between two different codebases, trying to remember which one has which functionality, and hoping that we don't break anything in the process.

Don't get me wrong, I'm not against rewrites. In fact, sometimes they are necessary for a project to move forward. But when frontend engineers can't seem to make up their mind and constantly want to rewrite the code, it's a recipe for disaster.

And don't even get me started on the experience level of the frontend engineers who started this project. Most of them only had 2-3 years of experience (at the time of inception some of them has less than 1 year of experience), and yet they managed to convince management to approve this mess. It's like the blind leading the blind.

But hey, who needs experience and expertise when you have shiny new technologies and frameworks to play with, right? Isn't that what matters most in frontend engineering these days? Keeping up with the latest trends and constantly jumping on the "hype train" without any real understanding of how it will impact the project in the long run.

As a backend engineer (so I kinda don't give a flying freak about frontend) with almost two decades of experience and who was doing frontend with jQuery back in 2005 - that's frustrating and all the inconsistency is literally killing people (a couple of clients literally dropped the contract because of frontend quality).

RANT = false;

PS: why I used Svelte runes? Because some freaking genius suggested to port new (unreleased, only beta version) frontend UI to Svelte 5 because of runes.

I thought nobody actually use directly CSS instead using a framework that hiddes it for real applications.

I thought it until meet my frontend coworker. He not only uses it, also understand it.

Admiration has born inside me.

I've chosen system/embedded programming because I liked system programming and did not like anything connected with web, frontend or UI.

So far it seems like it was a good choice. Even though web was not such a clusterfuck before, it was already repulsive.

we just created a new web dev team (3 months) and boss came to us, looked what frontend guy has done already (one guy who joined us month ago) and said "this is not how i imagined our platform. It should be working next month". Well how about providing anything to let us know what do you want? Well Im fighting now to get some brief at least ;)

I work in a big German company and we are a lot of teams building the company website.

Obviously the website is in German but almost all the devs are not German speakers, included the testers.

To make the work easier in the frontend we use sometimes the translation function of chrome and it's funny because a lot of time I got a bug opened by a tester for a wrong label because HE FUCKING FORGOT TO DISABLE THE TRANSLATION AND HE THINKS THAT THE LABEL IS IN THE WRONG LANGUAGE

If you’re a frontend developer but you don’t know when to use -, when to use – and when to use —, you’re not a frontend developer. You’re a monkey.

Just gonna leave this here because I am too lazy to write a proper article for my website:
If anyone is trying to create a Vue.js website with Node.js backend do NOT use express-vue, it is unnecessarily complicated and broken. Instead use this method I found.
You will need:
- IntelliJ IDEA / WebStorm / other IDE supporting multiple modules per project and tasks
- Nodejs and npm
- vue-cli

Step by step:
1. Create new empty project
2. Add your frontend module using vue-cli generator
3. Add your backend module using Express generator
4. Run npm build in your frontend module once
5. Move or remove public folder in your backend module
6. Create a symlink from your backend module root called public pointing to dist folder in your frontend module root
7. Make sure to add "Run npm build" from frontend module to your "bin/www" task (default task for Express module)
8. Enjoy developing your REST API in Node/Express and your frontend in Vue.js with single-file components and it being served by the same server that is providing the backend.
(Since they are separate modules and you are not mixing webpack and Node/Express you can add ts-loader, stylus-loader, pug-loader or any other loaders without screwing anything up)

For deployment you just need to copy the contents of dist into public on the server. (and not upload the symlink)

I coded part of feature 2 months ago.

Left it to help frontend guy a bit, deal with fire after release. ( we’re missing frontend integration tests and every release is pain in the ass ).

My backend code coverage is about 80% so not much can go wrong at this point.

So I added more code today and it looks like new feature is working but don’t know what the code I added 2 months ago exactly do.

The only thing I know is that it definitely needs refactoring ...

Being only backend dev / release manager / administrator/ dev ops in project is painful I need to deal with everything on my own 😔

At least client doesn’t care if it’s done in one week or in one month right now.

> TheSmartGuy: listen, IHateForALiving, I know you're a frontend developer, but here in the backend...

Just so we're clear: I'm NOT a frontend developer.

I'm a full stack developer.

I just so happen to always end up working on the frontend because you bunch of handless monkeys wouldn't be able to write a webpack config file if your life depended on it.
It's not you taking care of my inability to work on the backend, it's me being relegated to using only half of my skills because you ugly things refuse to evolve. I could take your job in a breath, I wouldn't trust you with writing a css selector.

That day we had the weekly meeting with my boss to tell him what was new since last week.
We were 2 developers, I did the backend and the other guy did the frontend.
I tell him we had nothing new on the frontend. Literally not even one more line of code.
He tells me he gave the other guy some money the day before to encourage him to engage a bit more on the project.
The meeting is about to end when we receive a message in the development group, the guy said he wasn't going to continue in the project.
Not like that, dude.

How is coupling backend + frontend as a single nextjs app a good idea? What the fuck is this?

What if you have to create new replica sets of a backend because of high load pressure? What about load balancers?? What if i want my backend to be a microservice? How do i unit test the backend if its cluttered with frontend? WTF IS THIS

WHY DID NEXTJS THINK THIS IS A GOOD IDEA AND WHY DO SO MANY DEVS LOVE THIS IDEA AND GLORIFY NEXTJS?

Nextjs seems like the type of framework that was built by a frontend web developer who just refuses to learn backend technology at all costs.

---

its been a few hours and the concept of nextjs is bending my mind rn. I thought nextjs is just another frontend framework. A react killer. Only to find out its both a backend + frontend framework.

Cluttering backend stuff into frontend is gonna get messy no matter how much you try to modularize the code. Am i lost or am i right???

---

Scratching my head over nextjs. Looks like a great framework for small-mid project but definitely not large project. The more shit the project needs the more messy shit become. Angular has modularized all of this in separate folders -- components services guards interceptors (now new stuff coming called Signals) etc. All of it is separated in individual folders and kept frontend-only. Simple enough. No backend clutter

---

Can i even use nextjs strictly as a frontend framework while it uses my custom backend built in java spring boot? For example use nextjs /api/ folder to handle custom routes built outside of nextjs framework?

Am i insane here

Been hacking frontend for a while, know most of the perks and tricks of css and html, have implemented countless of projects with angularjs, have even created jquery plugins and gulp packages, have won hackatons in UX design.... Still, a SFO company turned me down for a front end dev position cause I could not find the K most frequent words in an array in O(n) time complexity...

Donate now!

Is there an easy way to make your website not look like complete garbage, if you have no idea and no time for some web front-end?

Meeting at 'Derp & Co', the topic was what data model should send the back-end to frontend & app via API calls:

- Coworker: 'we should send the data structured like this for reasons'.
- Me: 'Yeah, this nested object.object.object should do the trick for the front end, but this will be a pain in the ass to convert to POJOs. Why not use something like idk better structure?'

<Mad/intrigued faces>

- CoworkerS: 'Why you need to use POJOs?'
- Me: <More Mad> 'cause I work with java in android... and we have/need/like objects?

<Captain Obvious left the room>

- CoworkerS: 'Oh yeah, well... we can do it the way you say'.

Why you need Objects... what is the next?
- Git? For what? Did not have the usb key from day one?

I hate doing front-end development...
I was hired along with another dev to build a webapp to manage the personnel of this big (2000+) company.
I made the backend and some of the frontend (mainly handling the data movement between the two), but my partner was let go after we delivered a first version because "there was not enough work for both of us".
The backlog is months of work for me and now I have to do everything and it's wearing me down...
I want to quit but it's paying well and I don't want to search for something new.
What do?

Well. I'm simply SO UNFUCKINGBELIEVABLE PISSED RIGHT NOW!! {>,,,<}

I'm implementing a monolithic frontend that embeds different projects which I don't want to alter if not really necessary. So I put them all into iframes, already handled all the security and auth stuff with proxies and so on and now I just want to access the body.scrollHeight property. Which is not even the probelm at all.

The fucking Problem is, that I just can't find a way to hook into any event which fires when all content is loaded and the final scrollHeight is set. Instead it just returns some default value that is set when the iframe element is loaded, but not something that is actually based on it's damn ass-fucking contents!!

Iframes are fucking pricks and I know I'll gonna go to hell for abusing them like this :S

Just wanted to code some better public transportation route calculator (better ux) and found out that the pt company offers an API.

EVERY FUCKING REQUEST HAS TO BE SENT AGAINST THE SAME FUCKING ENDPOINT IN A POST REQUEST WITH THE ORIGINAL REQUEST AS FUCKING XML IN THE FUCKING BODY. At least they offer xsd files... BUT THATS NO FUCKING HELP. At least not that much of a help. AND THE DOCUMENTATION DOES NOT STATE A SINGLE FUCKING EXAMPLE OF HOW TO USE THAT FUCKING ENDPOINT. I FOUND THIS OUT BY SENDING RANDOM REQUESTS TO THE ENDPOINT TRYING TO REVERSE ENGINEER THE EXISTING FUCKING FRONTEND AND NOW I NOTICED THAT 80% OF THE FUCKING DOCUMENTED FEATURES ARE DISABLED BECAUSE: NOT FUCKING SUPPORTED!!!

MAAAN WHY DO YOU DO THIS.

Alternatively I'd use the GTFS files they provide but THEY ARE FUCKING INCOMPLETE AND DONT STICK TO THE EXISTING STANDARD GOOGLE DEFINED... They also offer a different propietary format... BUT THATS FUCKING UNDOCUMENTED AND FUCKING INCOMPLETE...

Most of the rants I see here are related to CSS or JavaScript, so I am very grateful I did not end up in the frontend, which I would have given up long ago.

how infuriating is it when you (very much not a frontend dev) have to do "tweaks" to the UI

Spent all day comparing frontend stacks from articles and youtube videos and not to do anything until i open pornhub.

Recruiter wrote me to see if i was interested in a java frontend dev role - my answer:
Just as a fyi - java and javascript is like car and carpet - not the same thing :)

So this person is looking for a way to learn how to create websites, but apparently doesn't know what backend or frontend is.
Not sure if he is using the wrong process, or someone teaching him messed things up pretty bad. Or probably my question wasn't properly phrased?

Not sure what to say next. How to help him without investing hours? Should I share a good link for him to read? How do I do that without scaring him away?

Them: You have 6 days to build this frontend page for our wordpress site.
Me: Ok...
*proceeds to spend 4 days trying to arse my way towards a semi reasonable bootstrapped website based on the existing website's styling.*
Me: *Presents website*, so... uh... yeah, I don't usually do frontend stuff, I'm more of a backend dev, but here's what I could do.
Them: This looks like absolute horseshit.
Me: So what do you not like about it?
Them: All of it. It doesn't look anything like the wireframe that I gave you.
Me: Ok... So let me get this straight, you want it to look exactly like how you designed it in your wireframe? *wireframe looks like a child drew it*
Them: Yes! Is that so hard?
Me: I mean, it's a little hard. I'm not exactly a front end developer. Aside from that, I think this design is not very user-friendly.
Them: we don't care about your opinions, OP. Get back in there and make it look exactly like the wireframe.
Me: Ok.
*proceeds to go to fiverr, and contract someone else to do it for me while I get to do fun stuff in the back end.* 😂

----

We'll see what they think of the project when it gets back to me. Wish me luck guys.

Guess who's not going to work anywhere near frontend.

one of my friend is new to frontend dev.

and he's trying to center a div (text).

using position absolute and relative.

It's not working BTW.

We're communicating over text.
Must be loosing his mind.
He'll finally understand center div memes.

I'm faszinated by some dev's ability to write legacy code.
Not maintaining but plainly creating code so horrible, that it can be considered legacy.

I wrote a new API for a silly Application because the old one had hardly anything to do with rest. At all. And despite the code being only 2 years old, it was still unmaintainable.

Now that I'm finish with this task, i got the next generation of the angular Frontend.
A guy wrote a completely new version of the frontend in angular5.
Only untyped variables, no documentation, no tests at all, no idea whats going on where,....

I thought my job was to adjust a few URL's and change some DTO's, but now i have to refactor everything again...
And the pain continues.....

I have plenty of those but one that shines out from the croud is one frontend guy.

He had to modify some javascript slider but couldn't figure out how.

So he comes to me and tells me he found the code where the slider is initialized but changes are not applied.

I walk up to his desk and he shows me some CSS code with #slider selector in it.

!(rant && story)

It hit me today. I literally 100% fit the exact stereotype for a backend developer.

And it's not wrong, I love backend dev and hate frontend work with a burning passion (even though I can do it)

whyyyy

with the easy decision of the boss I got promoted (without salary increase of course)
I am not just backend/devops/devsecops/qa/architect solution developer.
I became frontend and desktop developer too!

Stakeholders must learn that code quality and a user-friendly frontend are not "nice to have". If they don't fix their priorities accordingly, someone will have to pay their technical debt and that's going to be expensive.

Backend : *breaks feature in prod by changing api*

Me: Feature is broken in prod. Please fix. I was told that the API will not deprecate the old use case.

Backend: ... Fixing it in the backend will take time. Add support for it in the frontend.

Me: I'm not done with the new feature just yet. And it will take some time to have it reviewed and fully tested. Please fix the API.

Backend: .... Well, make a new PR and add support for it first. The new feature can come later.

Me. (-_-) Okay

Sometimes it feels like I'm a code janitor rather than a frontend intern

Its good and practical but those who aim to fill gaps in the programming industry by trying to produce "programmers on demand" via a several month long bootcamp are complete idiots. Nobody can learn to develop a well structured application that's easy to maintain in a couple of months, either that is frontend or back end. We are trying to be engineers , not just solve problems.

Trying to find that one line of php you need to change in a magento project

App/design/frontend/base/default/template/this/is/not/gonna/be/the/template/youre/looking/for/fuckyou.phtml

I fucking hate webpack and frontend development so fucking much, why do I have to see my site not loading the bundled JS code on production but being absolutely fine in dev? is like watching my mom being run by a car over and over and over while I try to remember how it all was before she gets run over, FUCKING STOP WEBPACK, I havent sleep but just 4 hours since yesterday, I NEED YOU TO WORK JUST AS YOU DID IN DEV WITHOUT THE PERKS OF HMR FFS, JUST FUCKING DO IT

When working on a schoolproject I actually managed to do loads of work in a night when I was mad drunk.

Two days later I met with the project group again at school and I remembered I did something with the project, but had not the slightest idea anymore.

My project group showed up all excited that a lot of bugs were resolvee and we finally had something really nice working in the frontend thanks to me. It was a similar feeling to waking up when your arm/hand is numb and on your face and you have no clue whats going on, at first youre scared and later it was a damn cool experience.

Okay but whys no one talking about w3js? Its not a complete overhaul of the entire frontend shit, it doesnt introduce fucked up concepts, it literally just abstracts away those 10 functions everyone creates a function for in the first 2 minutes either way, its actually useful.

made my first dart server today, i already fucking love it!

i already used it for flutter, and previous node.js was my backend of choice.

i'd recommend strongly. no matter the platform for the frontend, web or mobile (or desktop app), you can use dart, and you can use it for the backend too!

it's like java but not shit.

I remember our PM/GM used to give us a website name and one line of website description, then he disappears to attend meeting outside the company. His phone is switched off most of the times and he doesn't reply to messages or emails.
2 days later, which is our fixed deadline for a website, he comes and says why the website is not up yet!

Note: One developer for one website and the developer has to design, write content and code frontend & backend.

Hey. Can I borrow your ears for 5 minutes?

Since I've been out of school, I've often felt that even though I've learned how to code, the education went into a totally direction than the one I want to go. Of course a school can't teach you everything perfectly, but having almost no experience in frontend (mind you we learned the BAREST basics) just makes me feel entirely empty in that regard stepping up to a company. I've been pretty loaded during school, since I was struggling with a lot of things so I couldn't really find myself pursueing the direction of coding frontend apps being fun. I needed the little time I had to blow off steam playing games etc.

So the few things I know are all self taught, but I was never given a hand been shown best practices or solid advice where to look. Sitting down now at my pc trying to learn ReactJS for example feels incredibly draining and difficult, since we've never done JS in school ONCE. All the C# experience barely helps, since with ES6 being rolled out parallel to "normal" JS it's even harder to me to connect the lego blocks that is frontend development. Since many best practices are applied to ES6, I can barely even tell what previous practice they are replacing, making the entire picture even more spongy. In one sentence it's very overwhelming.

I've thought I'd apply maybe as a UX/UI Designer since I've got a great visual sense (confirmed countlessly by many, friends and strangers alike) maybe contributing to the frontend part that way. But as I was applying I've noticed that chances are seemingly pretty low to get accepted since it seems you've got zero reputition if you don't have a degree in Design.

It breaks me apart. I could probably apply as a frontend developer, but I am not sure if I would be happy doing that on the long run. Since just fucking around in Photoshop creating things seems like no effort and brings me joy, as compared to coding out lines for example.

I wanted to make money after school, improve on myself and my quality of life since I've drained that entirely for the sake of my education. Not spiral into another couple years just to eventually maybe get in the direction I want to.

On the flipside going into frontend dev with 0 skills, 0 experience, but being expected to have 2 years of hands on experience with the newest frameworks makes me feel empty and worthless.

I often hand out advice to other people on devRant, but this is the one time where I need some. Desperately. I feel shattered inside, getting out of bed in the morning has no incentive to me since I'll just feel like shit all day, watching YouTube to cheer me up temporarily, only to feel immense remorse not spending the day learning or improving on myself. Barely anything brings me joy. I don't wanna call myself depressive, but maybe I am just dodging the term and I am exactly that.

Thanks If you've read through this monstrosity of a rant/story. I'd be glad if you'd be so kind to give me a different take on my situation or a new perspective.

I am stepping on the spot and I am slowly dying inside because of it.

It dreads me to say it, but I need help.

I talked to the client how functionality should look like on UI, draw a mockup, designed and made changes to db schema, created REST api, made documentation how to use it, told frontend developer to make changes on frontend application according to the documentation and mockups. Still no one have fucking clue how to do it. Fucking testers can’t write anything, only clicking.
So I sent curl code how the fucking request should look like exactly then resolved bugs they reported as won’t fucking fix because I will not be also making fucking frontend. Probably they even don’t know what curl is. What a fucking fuck.
And that’s what I am mostly doing from Monday till Friday to keep this project going.
It’s cause client are nice guys and we are doing something good, not some fucking ai, blockchain, big data, financial scam everyone is wanking around.
And friends are asking, why I drink.

Is it just me or are all the stoopid people in middle management? Why do these clueless people always impose completely nonsense requirements? Like 'You have to process all entered client data but you are not allowed to store it, nowhere, because of GDPR, storing data is evil!' But when customer logs on all his not persisted data has to be pushed to the frontend immediately. WTF THIS IS CRAZY

Frontend using async calls same way as sync to load json config which contains backend api url. To make calls to backend API and sometimes file is not loaded before they call Api. This results to calling on current domain instead on domain from json file. Moreover, blaming that be is returning incorrect response.

Great... I was hired to make a store system for this newborn startup... which isn't very tough, given I know PHP. Now they want me to build a social media for designers, just like Instagram, to encourage them to share their designs in an attempt to increase sales. And I'm the only Dev in the startup of ten.

Well, initially, I was not very pleased, but as I researched on how would I even do that, I realised it would really help my skill set, not to mention the points I'll be able to add to be resumé.

So far I've looked up how I'll have to use JSON/XML, coupled with PHP. I chose to learn Angular.JS for frontend dynamicity.

Any advice/help for this novice? Or any better frameworks I could use? (Don't say ruby-our web hosting site does not support it.)

After I was woken up in the morning by my friend that had a meeting nearby.
We went for coffee and as part of usual Wednesday I also decided to go to cinema to see Dr Dollitle ( not verry funny ).

I felt relaxed as everyone fucked off from me since Monday.

I was so happy of doing nothing after the movie I decided to try to make both frontend and backend for new application screens in finite time.

I could have waited for frontend developer to be back from his vacation but since I can also do it I decided to do it myself.

I did frontend part first with mock data and after finishing it before 2 pm asked if client will have time to discuss it. He didn’t so we decided I try to add real data and publish it on test environment.

Well those are mock up screens anyway so I decided to eat and smoke to chill but also try to work anyway.

I just finished backend for those screens and switched test environment to new branch.
Looks like they’re working for biggest client customers.

Usually it takes about a week or two to describe frontend developer what client wants but let’s see if I still have some frontend UX empathy left and can speed up development by couple of days.

tomorrow i have a presentation of a webapp but last night i decided to change the ui. i am not done yet and this frontend is driving me nuts.

the more i think about the effort i've poured into various projects and products over the years, for clients or my own, and how little its payed overall... its quite depressing (people probably understimate, but i'm talking years upon years, not all at at time, but month spurts where i'd be done for the day at 7 PM or later) 12 hour days are easy to hit quickly when you are cranking out software

if you need an application requirement i've probably built it before, probably most of them twice

everyone tells me "it will pay off in the long run!" or "its great you have so much experience and built those different things!"

great to say, but i'm not getting payed for it / see no benefit from it

not fun to think about

and every place i go i know its gonna be filled with the workaday dev bros who are just there for the paycheck, have no passion, and who don't even know what TypeScript is (true story about that TypeScript one, i shit you not, occured only last year, and the guy is a frontend dev)

😩😩😩

where do i belong devrant?

Hey devRant people !

How are you ?
I’ve a question, do you know a website like FrontendMaster, CloudAcademy or LinuxAcademy but ... for backend stuff ?

EdX, Udemy and all are very good but I would like to find a platform specialized in this topic.

For the love of god, why in the world are coworkers so prone to overflow with pointless informations? I don’t care about which db you use when I am a frontend, just tell me the f*cking endpoint to use ffs! Nor I care about the FE framework when I’m working on the be and most of all I don’t care about the reason behind a formula you use to calculate a freaking param, give me the goddamn formula or its name 🙄

Please tell me I’m not the only one getting triggered by coworkers explaining useless things, cause lately it’s so annoying

I'm a backend developer who for the last year has been helping the iOS-, Android and Frontend team with rewriting their shit.

Now I got yelled at for not making any new features on the backend, and we need to ship fast. So my manager dropped all further work on our backend, since it clearly needed a rewrite, since there have been no new features which to him indicates bad code that is hard to change.

Now all the developers are rewriting their applications to fit the new backend created by some new guy, which for some reason is stuck in creating a log-aggregator from scratch instead of the actual product.

I'm really not good in frontend designing.

I regret becoming a frontend dev ( mostly because I started learning jQuery first and not pure js ) .

Dear devs from the past. Whoever of you thought iframe navigation, js-only frontend and flash were a good way to build a web UI -
well, it's not.
Regards, a person from the future who still can't properly use tabs with your app.

Counted it out... 100k LoC frontend & backend... Not a single automated test. No unit testing, no integration testing, nothing. I've been asked to implement a CI server.

Halp

Working as an cooperative student in an big IT company. I shall continue the work of another student (Something in Frontend Visualization) for their Sharepoint sites.
The other student wrote a fucking 40 page university evaluation (requirements, first architecture and sl on) about the concept of this project and did not have the time to implement it.

But instead of giving me this research paper, my advisors say “Be creative and don’t use this work. Do it by your own.”
wtf? Why has this student even done all of this work and why do I have to waste many hours in order to begin everything from day zero??

Why all these SW engineer interviews include 2 days of questions about sophisticated algorithms which i have never (and probably will never) have chance to even reuse, because they are NOT simple & understandable for any project community? IMO It is like asking to show Assembler skills on frontend-dev interview...

My company boss wants to reorganise the team structures drastically.

Currently we have different teams for each product. And in that team we have a lead, frontend and backend developers working in sync.

The boss wants to split the teams not based on product.. but based on technology / frontend backend. Then assign the members to products based on demand.

Not sure how that is gonna turn out..

Head hunting interview:

Q: Are your front end dev?
A: Yup, I'm website's frontend developer.
Q: Are you good at AngularJS?
A: No, I'm not. I only know Reactjs, and Ember.
Q: How about backend, you said you know Rail?
A: Yes, maybe for 3 month experience.

Q: So we need Angular guy, but it seem that you are BAD at Angular. Can you JOIN our next interview?
A: Sorry. I already told you that I don't care about Angular. Isn't it totally different with BAD at Angular? Thank for your consideration. I'm out.

Is there any double standard such as without AngularJS you will be considered that you are terrible at AngularJS?

Is there anyone who actually likes using Angular?

I decided to learn it (im backend only for many years) to be less clueless in the frontend world.. and so far i find it horrible.
Is it just a "culture shock" or do frontent angular devs also find it.. not so fun to use?

What i dont like so far is the inconsistency of syntax.. i feel like similar things done differently and not following rules that can be learned, i can't remember/guess anything, everything needs to be googled

i.e- `*ngIf` vs `[ngSwitch]`

Not to mention 3 different syntaxes to simply bind a property..

I tried vueJs about 3 years ago and it was so fun and EASY

When your frontend does not really get what your backend is trying to say...

This is oalley.net. Apart from the fact that their frontend and backend do not work together very well, it is a nice tool to mark reachable areas on a map based on the starting point, the means of transportation and the maximum time.

I was studying a lot the last year, i learned a lot about Machine Learning/Deep Learning, Data Gathering, Data Analysis, ETL, Model Architecture Design, Training, Fine Tuning, Backend Development, DataBases, API Development, ORMs, Rest, GraphQL, OAuth, CI/CD, Docker, Deployment to Production environments like Heroku, Git and more stuff i dont remember while writing this. I built and keep adding stuff to my Github Portafolio.

Im not able to get a job. I started looking for jobs as Data Scientists, no response never. I take a look at freelancer sites, nothing seems to fit my skills. And when there is a minimal fit, they always want a Full Stack Web Developer, i dont know Frontend Development, i dont like do it.

Dont know what to do or how to land any job.

My options aeems to be:

1.Learn Frontend Dev and work as Full Stack in underpaying freelance jobs

2.Keep applying to Remote-Only startups, but they still wants people with 3+ years of experience.

i cant work in my city, here are not any company startup hiring no one, we are 30 years in the past here.

What you do in my place?

Wow..so i can’t believe this but i just got told by my “senior” in company that he “knows his shit” when i tried to give him constructive feedback on why doing calculations for users on backend is a bad idea and is not going to scale very well.
I mean we could do those calculations on frontend using web workers ( if they are so complex ) and that would have been clearly a better idea.

I also tried to give him feedback on why its a bad idea to couple backend apis with frontend. Honestly, i don’t feel like giving any sort of feedback anymore. I don’t even feel like trying my best to “improve” the codebase because if its going to be maintained by shitheads like him that get their pride easily hurt, then no matter how hard i try to improve it, its going to end up shit either way.