Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
kevbost27143y@g-m-f I hadn't planned on telling them so early. I came to an agreement with my new employer that I'd finish out the year and start in Feb. But both front-enders leaving was going to leave a pretty massive hole in the development team.
kevbost27143yI just discovered that the html I'm working on now has a <ul> where each <li> has an ID.
And that ul has been copy/pasted 8 times.
Jesus... I'm a junior backend dev but even to me this sounds terrible. it feels like common sense should have prevented this.
diavel4683y@kevbost , I feel you bro! I'm a junior front-end dev who got assigned to another junior front-end devs project after he left.
It was a disaster of epic proportions. No helper classes, bootstrap CSS classes overridden, most everything inline and the worst is that the same styles were written multiple times in multiple other CSS files.
Luckily, we are scraping that and moving to a new front-end for the product.
techog11463yI code reviewed a project with senior developers that did this on another team. It’s so important to have frequent code reviews and someone that enforces best practices. Maintenance nightmare waiting to happen.