TLDR; Go see it here. Intro Let's say you have 400+ repositories in your company. And you're: * A software architect that needs to understand what monitoring tools are used across all the repositories, and you want to ask an AI chat to help you * A Security
Developer-Experience
Since vibe-coding began, the enshitification of code and making throw-sway stuff have become very easy. I think projects like Spec-Kit are there to help mitigate this, and not a moment too soon. I think we'll see more of these "prompt-frameworks" such as socratic coder, Claude Templates,
Cursor
Now that cursor has added the concept of custom commands, we can put stuff like this in our repository: .cursor/commands/get-started.md: # Initialize Dev Environment for developer - greet the developer who's about to use this project, and ask if it's ok to setup the
TLDR; ML Algorithm integrations were (for us) a frustrating experience of re-implementations, duplicate work, and endless back-and-forth. We cut through that by abstracting research algorithms under Temporal activities and letting workflows that run them be maintained by developers. Researchers push new algo-code, apps just call a workflow that auto updates
Noise
Wanted: AI-Augmented Developer AI-Assisted Developer AI-Driven Developer AI-First Developer Generative Engineer AI-Centric Developer Meta-Programmer Neo-Coder Code-Orchestrator AI Native Engineer Intent Engineer Context Engineer AI-Powered Engineer AI-Enhanced Developer AI-Oriented Engineer AI-Integrated Developer AI-Focused Engineer AI-Supported Developer AI-Guided Engineer AI-Optimized Developer AI-Infused Engineer AI-Supervised Developer AI-Collaborative Engineer AI-Sy