🗣️ Post 1: Unit Tests for LLMs?

As posted by: simantakDabhade  |  🔥 Points: 4

🔗 https://news.ycombinator.com/item?id=45412543

💬 Summary

is theres any package that helps do like vitest style like quick sanity checks on the output of an llm that I can automate to see if I have regressed on smthin while changing my prompt.

For example this agent for a realtor kept offering virtual viewings (even though that isnt a thing) instead of doing a handoff, (modified prompt for this) so a package where I can write a test so that, hey for this input, do not mention this or never mention those things. Or for certain inputs, always call this tool.

Started engineering my own little utility for this, but before I dove deep and built my own package, wanted to see if something like this alr exists or if im heading down the wrong path here!

p.s. not sure if this should be called evals, kinda overlapping but yeah what should this even be called?

🗣️ Post 2: Navigation as Infrastructure, Not Prompt Engineering

As posted by: rashidae  |  🔥 Points: 3

🔗 https://rashidazarang.com/c/navigation-layer

💬 Summary

← Go back Navigation Layer You know why decisions stall. It’s not that you lack information. You have the goal. You might even have a plan. But when you sit down to actually work, you freeze. What’s the smallest thing I can do right now that moves this forward? Most people think this is a personal problem. It’s not. It’s a systems problem. And it has a solution. The GPS Insight Think about driving before GPS existed. You’d print directions from MapQuest. Turn left on Oak Street. Go 2.3 miles. Turn right at the Shell station. The directions assumed perfect execution. One wrong turn and you were lost, pulling over to refold a paper map. GPS changed everything, but not...

🗣️ Post 3: Big Time Burnout

As posted by: coneonthefloor  |  🔥 Points: 3

🔗 https://news.ycombinator.com/item?id=45412815

💬 Summary

I am totally burnt out.

I am a “software engineer” I am great at making things and solving problems with code. I love to code. I am an expert in my domain.

But I am employed to sit in meetings. Where my voice doesn’t matter. I am one dev to 6 middle managers with various lofty titles. They do not respect me. I am the bottom wrung of the ladder. But I am also the only member of the team who delivers anything. Without me the “developer” the product doesn’t exist. They hate me for this. So they lock me down. My computer is near unusable in its locked down monitored state. I have to ask permission to do the simplest things. They don’t want me thinking or being productive. Now they have me writing “prompts” so a robot can make me redundant. My confidence is zero, my skillset unappreciated.

It’s time to start again, find a new way to provide for my family.

The software engineering career that I loved has burnt out.

🗣️ Post 4: Prompt Engineering Is Requirements Engineering

As posted by: milkglass  |  🔥 Points: 2

🔗 https://www.oreilly.com/radar/prompt-engineering-is-requirements-engineering/

💬 Summary

In the rush to get the most from AI tools, prompt engineering—the practice of writing clear, structured inputs that guide an AI tool’s output—has taken center stage. But for software engineers, the skill isn’t new. We’ve been doing a version of it for decades, just under a different name. The challenges we face when writing AI prompts are the same ones software teams have been grappling with for generations. Talking about prompt engineering today is really just continuing a much older conversation about how developers spell out what they need built, under what conditions, with what assumptions, and how to communicate that to the team. The software crisis was the name given to this problem starting in the late 1960s,...

🎯 Final Takeaways

These discussions reveal how developers think about emerging AI trends, tool usage, and practical innovation. Take inspiration from these community insights to level up your own development or prompt workflows.