Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
Get a devDuck
Rubber duck debugging has never been so cute! Get your favorite coding language devDuckBuy Now
Search - "validation rules"
We are interviewing for a junior engineer, and I was tasked with writing the coding exercise for a candidate that came from a coding bootcamp.
Most of the exercises are React-focused, but I opted to go vanilla: Here's an HTML document with an unstyled form. Style it to your taste, and write validation logic according to these rules. Simple, low enough barrier for juniors to complete, but with enough wiggle room to let candidates show senior-level thinking.
I did the exercise myself and timed my work. 7m 22s. So, ok, juniors should have plenty of time for it (They get 1 hour).
Candidate comes in. Can't finish it. Did not know how to use `getElementById`. Assumed jQuery was loaded in the page and couldn't figure out why the $ function didn't work. Global variables containing dashes, without understanding that dashes could not appear in a variable name. 10 minutes of Googling how to see if a radio button is checked. Conditionals comparing strings possibly containing a dollar amount to hard-coded numerical literals.
To be fair, the candidate did show good empathy when viewing the page as an end user and thinking of possible improvements. Good curiosity, listening skills, etc. There was also decent reasoning skills in React terms. But without a library or framework to shape their thoughts, the candidate was unable to produce a functional web form.
I shared that the candidate has potential but the training cost would be high given the lack of technical knowledge that would aid troubleshooting even if they never left their comfort zone. I ultimately advised to reject the candidate.
Manager says he would not discount the candidate for the coding problems because if they can "build an application without understanding the underlying concepts", that was enough.
I want to be supportive. I do. But I also kind of want to retire.9
Rant and opinions wanted. Its a long one.
I have been working on a project for a month and a half. For the first week I was requesting designs that I got about 2 of out of 15. For the next week and a half the designer was on holiday so I couldn't do anything but delivered a few more designs once he got back.
This takes us 2 weeks in already. I have other things to do as well so at the same time I work on support tickets and some bespoke development coming in.
I get given 2 or 3 more designs and can't get anything else out of the designer after waiting a week so I have to design everything myself as I go and build it. Something I have never done before.
We are now 3 and a half weeks in. My boss randomly tells my pm it needs to be demo ready the next day. I work furiously to hack something together. It works but key functionality is missing.
I move house and work from home for a week and a half. I do my best but the project is full of bugs and the CSS is horrible because I didn't know what I was making at any stage. It is therefore CSS rules repeated in IDs everywhere.
My colleagues join me on the project because my boss has decided to try and sell it tomorrow.
They run through it and find all the bugs left from me working furiously to get things done quickly. Things like no search pagination and missing validation.
My boss is now pisses at me because the project is not finished, my colleagues are now all working on it. Throughout it all he knew the designer was not delivering me anything and that I was struggling.
Am I in the wrong for writing shit code that came about because I was coding with no idea of what the finished project should look like? Is he in the wrong for dumping this on me and just letting me get on with it even though he knew there were no designs?
Btw I am just finishing a 1 year internship and before this have never done web dev before.
Dear Prestashop developers, f**k YOU!
I already hate this shitfuck what you call the best open source e-commerce solution, but your module validation technique sucks.
They use tons of useless rules, but the last addition was the last drop: they force you to use the old (and long) array declaration.
So now I have 500 new errors in this fucking module.
Why the fuck do you want me to force an old syntax?3
We're in the last stretch before going Live next week.
A training session was held with some of the future users.
"Why does that dossierID field is mandatory with a lot of validation rules? We don't use that info, we just remember the names."
"Why do we have this feature to manage x info that is linked with one of our services? We only needed a text field for custom values"1