> What's wrong with building simple web applications that get things done and don't require build tools, secondary (or tertiary) languages or meta-languages (like SCSS, ERB, JSX, Jade, etc)?
Successful projects have a tendency to stop being simple as time goes by. Users start asking for more features, scaling issues crop up, etc, etc.
I wonder if something is getting lost in translation. With no particular order:
Hearing the word ideation would cause an allergic in people who are sensitive against Americanisms.
British are also notorius for their indirect way of expressing their thoughts and feelings. Instead of saying they do not believe in your idea or your ability to execute it, they'd prefer to use compensation as a get out.
Multiple layers of creolization is the most likely explanation of common grammatic features and distinct vocabularies.
There's a language called Gagauz, spoken in Moldova. It has a Turkic vocabulary and Indo-European grammar. It was, in its infancy, likely to be a Romanian substrate, Cuman superstrate creole.
An Proto Altaic substrate with various superstrates must have played out quite a few times.
I wouldn't be surprised if most of those states have laws for unfair dismissal as well. Companies develop an internal process to cover their backs for such eventualities. Running that process to the end is the costly bit.
I suspect, genarating components from designs is a pain point for narrow subsection of companies which use React. I also suspect those which have this problem are not in a place to pay. Startups with limited runways, agencies with shoestring budgets are not the most lucrative.
Or just remove the pedals and tape one of the cranks to the chain stay so they don't spin and catch the trousers. Did this with my daughter's bike and it held up fine for the month she pootled on it until she was ready to pedal.
I switch between toe clips(for commuting) and cleats(for longer rides) at least once a month. Why would you need to handle the chain? Pedals are attached to cranks.
That would still tell me something about the candidate. That they don't double check their assumptions is not a great sign.
For the record I always encourage candidates to start with the simplest solution and tell them we can then chat about improvements after we get the basics right.
I would not call adding two binary numbers algorithmic.
Having candidates write code is always a good filter. You'd be surprised by the amount of people who can't write a nested loop with a decade of experience under their belt.