Search This Blog

Sunday, July 12, 2026

Use Claude Code effectively


Use these power phrases to transform your work!

1) "Launch sub-agents" : Used to trigger parallel task execution, allowing multiple agents to handle independent tasks simultaneously rather than running them sequentially.

2) "Write me an implementation spec": Used to force the AI to create a detailed plan before building, which prevents incorrect assumptions and reduces the chances of having to redo work.

3) "Interview me": Used to shift the burden of questioning to Claude. The model will ask you the necessary questions to clarify the project, ensuring you haven't missed critical details.

4) "Verify before you build": Used to establish feedback loops. This involves updating your Claude.md file and using appropriate tools to ensure the AI can validate its output against your requirements before completion.

5) "Based on this conversation, build me a skill": Used to package repetitive processes into reusable "skills" that include a "gotchas" section to avoid repeating previous mistakes.

6) "Automate this": The most dangerous phrase. advises caution here, recommending you first perform a "taste test" (does the task require human judgment?) and an "80/20 analysis" to decide if a task is actually suitable for automation or if it should merely be augmented.

Saturday, July 11, 2026

Karpathy's Method to effectively use Claude Code

Karpathy's Method to effectively use Claude Code



1) Build Spec

Prompt: Interview me to find the real goal of this project. Bias toward small, compartmentalized specs. Make me verify key decisions explicitly so nothing is missed.


2) Verify loop 

Install -  codex plugin for claude code

Prompt: Before you start, define the precise criteria for a great result, use a past example as the format to match, and have a second Al check the final output.


3) Set the Environment

Prompt: Check my CLAUDE.md, my knowledge base, my skills, and my guardrails. For each of the top 5 gaps, name the file, the problem, and the exact fix — and flag which risky actions need a hook so I can't bypass them.


Protip: First, set the statusline

/statusline model context effort size 5 hour limit weekly limit


Source: https://www.youtube.com/watch?v=7zZy1QTvokM



Wednesday, July 8, 2026

New roles in AI - Boris Cherny blog post

Boris Cherny blog post



As engineering, product, design, DS, etc. melt into a new kind of role, I was reflecting on what roles might look like in the future. For example, when I look at the Claude Code team I see what I think is five archetypes:


1. Prototyper: comes up with brand new ideas; churns out many ideas, most of which don't ship

2. Builder: quickly turns a prototype/idea into production-grade product/infra

3. Sweeper: cleans up the UI, simplifies the code and system, unships, optimizes performance

4. Grower: takes a product that has been built and iterates on it to improve Product-Market Fit

5. Maintainer: owns a mature system to make it secure, reliable, fast, and efficient as it scales


Many people span across 2 roles, and sometimes 3 roles. I also notice that these roles are not really tied to job function -- eg. across Anthropic, some designers match category 1, some 2, some 3; same for engineers, PM, DS.


A healthy team needs a mix of these, depending on the product:


- A product that is new and pre-PMF needs people that are strong at 1+2+3

- A product that is growing and has found PMF needs 2+3+4 and some 5

- A product that has strong PMF needs 3+4+5 and some 2


Maybe product roles of the future will look more like this, and less like the domain-specific roles of today?

Wednesday, August 28, 2024

LLMaaS, LLMOps and Enterprise AI Platform!

In this blog, I will describe LLMaaS and LLMOps and the building block of the Enterprise AI Platform! 



LLMaaS represents the idea of providing access to powerful LLM services through an internet/intranet. It's similar to other "as-a-service" models (like SaaS, PaaS, etc.), where users can access and utilize LLMs without needing to manage the underlying infrastructure or complex development.

LLMOps focuses on the operational aspects of managing and deploying LLMs in production environments. It's essentially the application of DevOps principles to the lifecycle of LLMs

In the above block diagram, I have depicted comprehensive architecture for an enterprise-grade AI platform, designed to support various stages of development and deployment of AI models, especially focusing on Large Language Models (LLMs). It's broken down into several layers, starting with infrastructure and going up to the application level:

1. Infrastructure: This layer provides the foundation for the platform, encompassing physical resources like:  Compute: Servers for running workloads, including model training, inference, and other tasks. Storage: Storage systems for datasets, model checkpoints, and other essential data.  Network: Networking infrastructure connecting various components and enabling communication.  GPU: Specialized hardware (e.g., GPUs from NVIDIA) for accelerating AI model training and inference.

2. Private Cloud/Virtualization: This layer provides a virtualized environment that leverages virtualization technologies such as VMware, Nutanix, or Oracle's VirtualBox. It enables flexible resource allocation and isolation, making it easier to manage and scale the platform.

3. Private AI Platform: This layer represents the core of the AI platform, encompassing the following components: GPU Virtualization (Ex. Nvidia Enterprise AI or VMware BitFusion): This layer further enhances GPU utilization by providing a virtualized environment for accessing GPUs. It enables resource sharing, efficient utilization, and isolation for different AI workloads. VM (Virtual Machine): Virtual machines can be used for running specific workloads or specific components that require a dedicated environment. Kubernetes: A container orchestration system that manages and scales containerized workloads, enabling the deployment and management of microservices that make up the AI platform. Container: Containers are used to package and run applications and their dependencies in a consistent and isolated manner.

4. MLOps Platforms: These are platforms specifically designed for managing the machine learning lifecycle. They provide tools and services for: Run:ai: A platform for managing and scaling GPU resources, ensuring efficient utilization and performance during model training. Kubeflow: A platform built on Kubernetes that provides tools and infrastructure for managing the machine learning pipeline, including model training, deployment, and monitoring. DOMINO: A platform that provides collaborative tools for data scientists and machine learning engineers to manage and share their work, including data, code, and models.

5. Developer Tools and Catalog: This layer provides a set of tools and resources specifically designed for AI developers: Huggingface: A popular repository and platform for sharing pre-trained models, datasets, and code for natural language processing (NLP), enabling developers to leverage existing resources and accelerate their work. PyTorch: A widely used deep learning framework that provides tools and libraries for building and training AI models. RAY: A library and framework for building distributed applications, enabling scalable training and inference of AI models. Rasa: A framework for building conversational AI chatbots, providing tools for creating and deploying chatbots that interact with users naturally. VAC: A platform for managing and deploying AI models and applications, providing tools for monitoring and managing the lifecycle of models.

6. Experimentation Platform: This layer focuses on providing tools and infrastructure for experimenting with AI models: API Gateway: Provides a secure and managed way for developers to access the platform's services, ensuring controlled access and authentication. Micro Services: The platform is structured as a collection of independent, modular services that communicate through APIs, enabling flexibility, scalability, and isolation of functionalities. Kafka: A messaging system used for real-time data streaming and communication between different components of the platform. Redis: An in-memory data store used for caching frequently accessed data to improve performance. MongoDB, MySQL: Databases for storing metadata, experiment data, and other platform-related information. Monitors: Tools for monitoring the platform's health, performance, and other key metrics, providing insights into the overall system behavior.

7. App and Data Services: This layer represents the applications and services that leverage the AI platform's capabilities for end users. They interact with the applications through various interfaces, benefiting from the platform's capabilities.

The diagram highlights the modular and interconnected nature of a modern AI platform, showcasing how different components work together to support the entire AI development lifecycle. The platform's design emphasizes scalability, flexibility, and developer experience, enabling efficient experimentation, training, and deployment of AI models, especially large language models, for various applications.

Tuesday, February 13, 2024

GCP Overview

Similarly to the AWS summary, here is the GCP summary file

Update on 17 Oct 2024 

Cleared back to back 3 GCP certifications, one every month


1) Google Certified Professional Cloud Database Engineer (Oct-2024)
2) Google Certified Professional Machine Learning Engineer (May-2024)
3) Google Certified Professional Cloud Architect (Apr-2024)
4) Google Certified Associate Cloud Engineer (Mar-2024)

Check out my official badges on Credly!


Also, note that Google Cloud gives a free hoodie if you pass professional certification!


By winter (Dec-2024), I will collect a few more (Data and DevOps) to stay warm! :-)