Pattern
My colleague, Harel Coman, wrote about a new AI-driven code review pattern he's been implementing lately called Red Queen Code Review. I like this idea. If I had to put it in a sentence: Every Code Review "issue" must change either your code, or the AI
Developer-Experience
I don't know when or how I'll use all of these, but I love the scripts listed here. Some that caught my eye: boop (an alias, not a shell script) makes a happy sound if the previous command succeeded and a sad sound otherwise. I do
Conferences
I've been slowly getting back into public speaking, as I've been "in the trenches" for the past few years (working on my own startup was a huge journey). Anyway here's what I'm planned to speak about in 2025: * Nov 25
News
OK. This is Big. If you don't know who Andrej Karpathy is, please get to know him and all of his amazing writing and projects. 💡If you're a hands-on developer, I recommend Karpathy's "Technical Track" set of youtube videos where he basically
Cursor
My extremely talented colleague, Harel Coman, wrote a new blog post about how he uses AI augmented coding with Cursor as a frontend tech lead. He ended up developing his own method which works well for him, and documenting it. We've seen amazing results with quality code in
Noise
AI agentic coding has enabled so many possibilities now. Every domain I ever bought and never used is now sitting there, closer than ever, waiting for me to start that project "this time for real". Every little coding indulgence I can think of when working on a feature
MLOps
TLDR; see main image of this post, and this is the structure: AI Stack │ ├── Day-to-Day Chat │ ├── Development Centric │ ├── AI Coding Tools │ └── Background Coding Agents │ ├── Research Centric │ ├── AI Studio (Research) │ └── Model Training, Eval & Lifecycle │ ├── Production Facing │ ├── AI Gateways │ ├── AI Guardrails │ ├── Prompt Mgmt & Monitoring │ └── Agentic Frameworks │ └── Model Serving ├── Self-Hosted └── Managed
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