What happened to the Vue.js docs? Years ago the v2 docs were amazing, simple yet clear and provided detailed information for every API. I picked up v3 after a few years of only using React and the docs are a mess. Guides are not in a logical order, and the API reference is missing a lot of information and forces you to dig through type declarations in the code to figure things out.

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.

I’ve been doing web development and mostly focusing on the frontend side of things professionally for almost 10 years. Still, I have to put up with some backend developer who did a couple of years of frontend development who now thinks he knows it all. Everytime someone reports a UX problem or asks for a feature that has some complexity and needs more thought to have a good enough solution, he steps out of his lane with “suggestions” on how to get it done with solutions that are half baked and don’t consider things like accessibility, responsiveness, or even semantics. Still, he is the hero and we’re the bad guys when we call him out for only providing crappy solutions and presenting them as complete solutions.

Been applying for jobs lately and despite the years of experience and using the latest toys I’ve been finding it harder than ever to even get a positive response to my CV. One thing I’ve been noticing is that companies seem to now not care so much about frontend skills and more about complex algorithms when the role is ui focused, or to have a demand for dev ops experience. Are we really getting back to the days of thinking that jack of all trades can be experts in everything?

I was a midweight dev acting as a lead dev on the frontend development of a project. I had already built most of it, it was all vanilla JavaScript, had no jQuery, the code was simple, fast, and small. Then I went on holiday and the company put a senior lead on the project to carry out remaining work while I was away.

When I came back, there was a bug in the age gate page and I started to investigate. I then noticed that the asshole added jQuery to the code just to select the country and date of birth input fields. That idiot, a senior lead dev earning more than twice what I earned, didn’t know how to select some elements on a page! I nearly lost my temper when I saw the added bloat.

When you get a freelance dev who thinks he is a superstar dev and he is trying to prove he knows his stuff by throwing his 2 cents at everything and shits all over every architecture and code style decision of the project, even though he is not even familiar with the framework used by the project...

Not exactly a co-worker, but one of the devs from the client's team spent a few months working in our office next to us. He would always take a nap at lunch time and snore loudly, and eat an apple afterwards and it seemed to be impossible for him to chew with his mouth closed.

Whenever he had a cold and his nose got blocked he would still force himself to breathe through his nose, so it sounded something like a mix of darth vader and someone drowning.

He also lacked any notion of personal space, and would always sneak behind us to ask questions and then put his laptop right on top of our keyboards or in front of our screens and start talking while we still had headphones on.

React is overrated! There! I said it!

I seriously don't get why so many frontend developers are defaulting to React to build even the simplest of pages

We all have that guy in the team who everyone loves because he is such a laugh, but doesn't do shit and we have to work extra to be able to barely meet the deadline

Started a new job today. Now to get used to all the new coding standards and ways of working...
At least I received a welcome pack full of booze to help me get through it :)

I had a job interview today. Things got a bit awkward when the guy doing the interview (a head of tech) brings into the interview one of their midweight devs and I became the interviewer rather than the interviewee.

Handed in my resignation yesterday. The wolves are already waiting to pounce...

The project started as a series of individual prototypes. The client the wanted a beta app for a few selected clients, and someone had the great idea of just merging the prototypes into a single app. The attitude of the devs was always "whatever, this will be rebuilt for public release"

Over one year later, and after many different developers touched the project, the client wants it to go live, there was never a rebuild, and there won't be one until a few months after it goes live, and the project is buggier than it ever was.

A rebuild would have been quicker and safer than fixing the huge backlog of bugs, still the client won't accept a rebuild.

A few people already quit over this project and I think I will be the next one to hand in my resignation.

The analytics guy just sent me updated tracking specs for a web site.

There are two sheets in the file: "Custom Events LATEST" and "Custom Events updated". This is already confusing enough.
One of them has comments like "I'd like this to be amended", but the event specs described are the same as the ones implemented.

I asked him for clarification, turns out he wants the ones marked in black to be updated, the ones that don't have any label saying they don't need to be updated.

This is also a guy who for at least 2 years has been making columns in spreadsheets wider not by just widening them, or merging multiple cells, but by just letting text overflow into other cells.

I do wonder how some people manage to keep a job.

I have wanted to be a web designer, studied multimedia design, and have always done some code of my own because I couldn't pay anyone to code my projects. After finishing my degree I was a unemployed and couldn't even get an internship. One day a friend asked me to code a project for his agency because he couldn't find anyone on such short notice. I did it in a weekend and got some good money for it. That's when I realised there was a chance I could be a dev instead of a designer. Started to learn more, moved to London, and never even wished I went back to design.

Worst Jira ticket I've ever seen:
Title: "It looks f#?$ed"
Description: ""

This gem was opened by the project producer. When asked about it, it was just a mismatch in text margins.

Lovely Summer day outside (you don't get many of those in London), and the office I work at doesn't even have windows.

Isn't it great when you get urgent tasks, but the documentation required for it can't be found or doesn't even exist, and the devs that worked on the project before are no longer in the company? And then the producer gives you some document that is completely unrelated?

When the code is so bad that fixing one thing breaks 10 other things because the code was made to work with broken code.

A dev joins the project. I help him set up, and he has everything up and running. I give him a task to fix a CSS issue, I even tell him what needs to be done. Almost 4 hours later I begin to wonder what's taking him so long and what is he up to. He finally sends me a pull request with just one line of code changed, and leaves for the day, over 45 mins earlier than supposed to.

A dev in the team just found out about JavaScript promises. Now he is putting them everywhere but never handling errors, so it's impossible to tell where the app is actually failing because the error points to the Babel polyfill and the stack trace is not long enough.

When the library you're using doesn't follow semver and introduces breaking changes with a path version... (I'm looking at you, ParseServer!)

Recruiters on LinkedIn will be like: "I just came across your profile and ...". Scrolls up the message history and there is the same message a few times with a different job.

I know recruiters have to send out tons of emails and using templates makes it a lot easier, but at least make and effort to make it look like you aren't just reusing the same message over and over.

When you think the code from companies like Google and Facebook is flawless, but then you look at the source code of Parse 1.5.0 and find an if statement with the condition 'browser' === 'browser'

The project tech lead asks me to add some Docker configuration files sent by the client to a project. He gives me a zip file and I unzip it and add the files to Git. Job done.
Later he checks the commit and starts bitching because I unzipped the file and it should have been added as a zip. After much debate trying to explain to him that Docker wouldn't open the zip file to search for the Dockerfile he just says "Can you just do it? I double checked with the client!". I give up after giving him all the arguments why he is wrong and do it.
The next day the client checks the commit and comments bitching that I included the zip file and not the contents of it.