The incredible thing to me about this is the original blog post is explaining decades-old startup bro “wisdom” like it’s brand new.

Plenty of ink has been spilled to describe how AI is a challenge for junior developers, especially those trying to land a job. Now that I’ve seen junior people work with AI for a bit, I have a more hopeful take: Impact is less bounded by how many years of accumulated knowledge in frameworks and libraries you’ve gathered.

I’m seeing engineers who are comparatively new fly past people who are probably better coders and have been around much longer. Hunger beats tenure.

Then the things he recommends that junior engineers do all sound like they’re right out of a 2012 startup handbook.

Pick a radical idea: Come up with a few ideas that would, if successful, dramatically improve the chances that your organization achieves those goals. Be ambitious!

Build it over a weekend: I have seen small groups and solo engineers fly past the usual process of writing product requirements documents (PRDs), getting buy-in, and lobbying for time with designers or product managers by building a working prototype.

Yeah, hashtag disrupt, right guys? You just gotta be hungry, bro. Move fast and break things was Facebook’s motto.

History doesn’t repeat but it rhymes!