Kimberly West

Used to be an obvious call, hire a junior dev, let them grow into it over time, review their code, build them up.
Now with AI handling a lot of basic implementation well, curious if that math still holds.

Is anyone still bringing on interns or junior developers for entry level coding work, or has AI quietly replaced that hiring category for a lot of teams already.

Genuinely trying to understand if this is still a real starting point for someone entering the field, or if that entry point has basically disappeared.

I ve ended up with hundreds of saved links that I keep telling myself I ll come back to. Now it s getting harder to find anything useful and I don t really want another paid bookmarking tool just to organize them. Do you have a simple system or any built-in browser features that help you automatically clean up old bookmarks?

I keep coming back to this idea: vibe code is basically instant legacy code.

Not because AI-generated code is necessarily bad, but because it often puts us in a familiar situation: the system works, yet no one fully understands how it works. That makes me wonder whether some of the most useful techniques for vibe coding are actually techniques we already use for legacy systems. For example:

• Snapshot / approval tests: capture the current output and require explicit approval when it changes.

• Characterization tests: describe what the system actually does today, regardless of what it was originally intended to do.

• Golden master tests: run known inputs through the system and compare the results with a trusted baseline.

• Contract test: protect the boundaries between components, services, APIs, events, and data stores.

• Differential testing: compare two implementations and detect where their behavior diverges.

• Test carving: observe a larger execution and extract smaller, focused regression tests from it.