In the past couple of months, our company has started taking AI seriously. Leadership now expects us to achieve 2x or even 3x the sprint output compared to before, thanks to AI tooling.

But here's where it's getting messy: in the UI, code quality is starting to deteriorate fast. With so much being generated or heavily assisted by AI, we’re seeing a lot of monkey-patching everywhere. Inconsistent styles and patterns. Things showing up in code reviews that would have been hard no’s before, but now they're getting merged because everyone is trying to move fast. A lack of ownership or cohesion in the architecture like it's being stitched together rather than engineered.

As a team, we’ve silently agreed not to be too strict right now, probably out of not to slow things down or being seen as blockers but I’m concerned that we’re building up serious tech debt and chaos for the future.

Anyone else dealing with this or know how to handle it?

It has been 10 years since ES6 has come out. I am ready to talk about JS topics, React, talk about performance , my experience with projects. But they still focus on some niche tricky JS behaviors that is addressed by ES6 and onwards. I know that there are lot of legacy systems that are clusterfucks of JS bugs. But can we stop pretending that I need to know every tricky dumbass behavior that exists at the back of my head!? If you are a frontend interviewer, Please ask more relevant questions and save us from this pain. Thank you.

A bit of rant but I have six years experience as a frontend dev but I was caught off-guard by the guy at Bluebird. I had experience with entire stack he mentioned e.g. Typescript, AWS, Github Actions, Unit Testing / Jest, ReactJS. However, he immediately launched into asking technical questions;

ie. What is the difference between CSS Flexbox and CSS Grid? (I worked with most Flexbox but I couldn't remember difference between the two off the top of my head)

What is your favourite feature of Typescript? (mentioned I could create my own types and interfaces - but I don't have a *favourite* feature)

What is Suspense? Ugh, I actually used this in a past role - but I forgot the asynchronous loading of components in React was named that recently.

Anyways, is anyone frustrated about these tech tests? Its like they just ignore everything else like how I managed a team, etc. and my overall projects I worked in the past. It's plain discrimination too since I reason better by writing code and having to verbally explain some esoteric trivia about Typescript.