Joy Jones

Joy Jones

Diversity, Inclusion &Belonging@LikedIn
#101572090 followers7 following
>10,000All time
20 KP

About

I'm passionate about creating workplaces where people feel respected, included and genuinely valued. In my work with Diversity, Inclusion & Belonging at LinkedIn, I focus on helping build a culture where different perspectives are welcomed, people can bring their authentic selves to work and everyone has a fair opportunity to grow. For me, inclusion isn't just a workplace initiative, it's about creating meaningful belonging and turning diversity into a real strength for people and organizations.

Badges

Tastemaker
Tastemaker

Forums

•

17h ago

Every one-line prompt ships with a spec you didn't write

Something I wish I'd understood earlier about working with coding agents: there is no such thing as dispatching without a spec. There's only choosing who writes it.

When you send an agent a one-liner like "fix the login timeout", the unstated parts don't stay undecided. The model fills every blank with defaults from its training data the average project, the average convention, the average meaning of that sentence across every repo it has seen. Where your codebase matches the average, those fill-ins are invisible because they happen to be right. Where it doesn't, you get a diff that answers a question you never asked.

An intern who hits ambiguity tends to come ask. An agent mostly picks, and rarely flags the pick a constraint that never made it into the context might as well not exist.

So we stopped asking "spec or no spec" and started asking two questions before every dispatch. How long would a wrong guess stay invisible? And how far is this task from the average project the model trained on? Fast feedback plus mainstream shape: one line, go. Slow feedback plus weird shape: write the contract, and budget the writing as part of the build.

View more