My tech stack: Python, React, Django/Flask, AWS.

Joined November 2025
CRM & SaaS Full Stack Engineer retweeted
12 AI frameworks to know ⬇️ 1️⃣ LangGraph 2️⃣ CrewAI 3️⃣ Microsoft Agent Framework 4️⃣ Haystack 5️⃣ FAISS 6️⃣ vLLM 7️⃣ Ollama 8️⃣ ChromaDB 9️⃣ Pinecone / Qdrant / Weaviate 🔟 XGBoost 1️⃣1️⃣ LlamaIndex 1️⃣2️⃣ Hugging Face Agents • RAG • LLMs • Vector Search • ML #AI #Engineer #RAG #LLM
2
38
145
4,126
CRM & SaaS Full Stack Engineer retweeted
10 OpenCode skill repos worth saving:  1.⁠ ⁠Superpowers ⁠ github.com/obra/superpowers ⁠  2.⁠ ⁠Ponytail ⁠ github.com/DietrichGebert/po… ⁠  3.⁠ ⁠UI/UX Pro Max ⁠ github.com/nextlevelbuilder/… ⁠  4.⁠ ⁠Graphify ⁠ github.com/Graphify-Labs/gra… ⁠  5.⁠ ⁠Caveman ⁠ github.com/JuliusBrussee/cav… ⁠  6.⁠ ⁠Addy Osmani Skills ⁠ github.com/addyosmani/agent-… ⁠  7.⁠ ⁠Understand Anything ⁠ github.com/Egonex-AI/Underst… ⁠  8.⁠ ⁠Awesome Claude Skills ⁠ github.com/ComposioHQ/awesom… ⁠  9.⁠ ⁠Archify ⁠ github.com/tt-a1i/archify ⁠ 10.⁠ ⁠Impeccable ⁠ github.com/pbakaus/impeccabl… ⁠ if you’re building with OpenCode, these are worth keeping in your stack.
10
43
6
248
66,935
CRM & SaaS Full Stack Engineer retweeted
this is pure f*cking treasure 20 GitHub projects to help it understand a real codebase, use real tools, catch bad changes, and show you what happened UNDERSTAND THE WORK 01 Beads ▸ github.com/gastownhall/beads 02 Repomix ▸ github.com/yamadashy/repomix 03 Serena ▸ github.com/oraios/serena 04 ast-grep ▸ github.com/ast-grep/ast-grep 05 claude-mem ▸ github.com/thedotmack/claude… CONNECT TO REAL SYSTEMS 06 ToolHive ▸ github.com/stacklok/toolhive 07 MCP Inspector ▸ github.com/modelcontextproto… 08 Steel Browser ▸ github.com/steel-dev/steel-b… 09 Midscene ▸ github.com/web-infra-dev/mid… 10 Bruno ▸ github.com/usebruno/bruno CHECK THE CHANGE 11 Trivy ▸ github.com/aquasecurity/triv… 12 Gitleaks ▸ github.com/gitleaks/gitleaks 13 OpenSSF Scorecard practices ▸ github.com/ossf/scorecard 14 Checkov ▸ github.com/bridgecrewio/chec… 15 SWE-bench ▸ github.com/swe-bench/SWE-ben… SHIP AND LEARN 16 Dagger ▸ github.com/dagger/dagger 17 GitButler ▸ github.com/gitbutlerapp/gitb… 18 Git Town ▸ github.com/git-town/git-town 19 OpenLLMetry ▸ github.com/traceloop/openllm… 20 LangWatch ▸ github.com/langwatch/langwat… the loop: capture the task → map the code → use the right tools → test the actual interface → scan the change → run the pipeline → inspect the trace → improve the next attempt save this, then build a second brain for your business⭣
24
33
183
15,483
CRM & SaaS Full Stack Engineer retweeted
JEV MADE YOU WANT AN AI AGENT. THESE 3 GITHUB REPOS HELP YOU RUN IT, GIVE IT ANDROID TASKS, AND TEST ITS LIMITS 1/ DSH Desktop - 29.3K⭐ → github.com/anywhere-labs/dsh… Run and manage AI agents from a desktop app, with plugins and phone access. 2/ Artemis - 10.5K⭐ → github.com/google/artemis Describe a task in plain language. It navigates Android apps, completes the workflow, and captures the result. 3/ ARC Task Gen - 11.1K⭐ → github.com/pathwaycom/arc-ta… Generates new puzzles to test whether AI can solve problems it has never seen before. Run an agent. Give it a task. See what it can actually do
12
29
178
16,341
CRM & SaaS Full Stack Engineer retweeted
JEV + OPUS 5.5 IS INSANE FOR BUILDING A COMPANY BRAIN I pulled the whole architecture out of the TypeSafe and Anthropic docs and packed it into a 14-page PDF the 10 steps: 1. meet the pair > Opus 5.5 thinks, Jev decides, your code holds the branch 2. stop asking a text generator for a yes or no > Jev returns a typed answer with a calibrated probability in 0.44s for $0.00035 3. ask everything at once > Choice, Score and Noul run in parallel, so the fourth question costs almost nothing 4. branch on the number > 0.999 goes straight into the if statement. ~99% of turns end right here 5. stop routing blind > Opus 5.5 to Sonnet and back costs 5.84 against 3.32 for staying on 5.5 6. keep one context warm > cache reads at $0.20 per Mtok are 20x cheaper than a fresh load 7. escalate the hard part > the toughest 1% goes to Opus 5.5 with 1M context and 66.4% on Terminal-Bench 4.0 8. score every chunk on every query > keep whole, summarize or drop. the context gets rebuilt each turn 9. gate the actual command > every bash call gets classified before it runs, inside your own code 10. judge 100% of runs > $3.50 a day for 10,000 traces, and it matched the human label on all 500 decisions the result: a while loop that paid a frontier model for every tiny call turns into a brain that spends a fraction of a cent to notice and pays properly only when it has to think the person who brings this into their team walks into the budget meeting with the AI bill cut and the output up the PDF maps the company brain. the loop side of it - how Jev takes a Claude bill from $765 to $3 a month - is in the article below ↓
20
80
4
703
103,877
CRM & SaaS Full Stack Engineer retweeted
YOU DON’T NEED 10 AI MODELS. YOU NEED TO UNDERSTAND THE AI STACK. ChatGPT, Claude, Gemini, Llama... They’re just the models. The real power comes from everything connected around them: Model → Context → Memory → Tools → APIs → Agents → Actions Give an AI model access to your database. Add web search. Add memory. Add tools. Now it can do more than generate text. It can research. It can decide. It can call APIs. It can execute tasks. That’s the shift happening in AI. We’re moving from: “Ask AI a question” to: “Give AI a system to work inside.”
JEV: THE AI MODEL THAT DOESN’T NEED TO GENERATE TEXT. Most AI generates text token by token. Jev takes a different approach. No text-first generation. A completely different way to build AI.
36
45
1
184
19,211
CRM & SaaS Full Stack Engineer retweeted
Replying to @techNmak
context policy is product design
1
2
366
CRM & SaaS Full Stack Engineer retweeted
See the impressive collection of @OReillyMedia Machine Learning / AI / Data Science books at: amzn.to/3icyoqJ
1
60
397
19,828
CRM & SaaS Full Stack Engineer retweeted
TypeScript tip: pattern-match string unions at the type level with template literal types. #TypeScript
1
2
110
6,207
CRM & SaaS Full Stack Engineer retweeted
System Design Interview Question: You have 500M products. Search needs to respond in <100ms. What would you use?
29
13
159
18,794
CRM & SaaS Full Stack Engineer retweeted
80% of System Design Interviews Test the Same 20% of the concepts. Here is what you need to master. 1. Scalable Data Storage • Relational vs. NoSQL: Know when to use SQL vs. NoSQL databases. • Partitioning: Vertical and horizontal partitioning (sharding). Understand trade-offs. • Indexing: Covering indexes, primary vs. secondary indexes. • Consistency Models: Strong, eventual, causal. 2. Caching • Client-side vs. Server-side Cache: Understand where caching should happen. • Caching Strategies: Write-through, write-back, write-around. • Distributed Cache: Redis, Memcached. • Cache Eviction Policies: LRU, LFU, etc. 3. Load Balancing • Horizontal Scaling: Why and how to horizontally scale services. • Load Balancing Techniques: Round-robin, consistent hashing. • Reverse Proxy: Understand how to use Nginx, HAProxy. 4. Asynchronous Processing • Message Brokers: Kafka, RabbitMQ. When to use queues vs. streams. • Event-Driven Architecture: Benefits of decoupling and event sourcing. • Task Queues: For delayed jobs or retries. 5. Database Read and Write Scaling • Read Scaling: Master replication, read replicas. • Write Scaling: Challenges with partitioning for writes, leader-election. • CAP Theorem: Consistency, Availability, or Partition tolerance may be compromised. 6. Distributed Systems Concepts • Consensus Algorithms: Paxos, Raft. • Conflict Resolution: Last Write Wins, CRDTs, vector clocks for data reconciliation. 𝟳. Reliability and Failover • Redundancy: Active-passive vs. active-active configurations. • Health Checks. • Retries and Circuit Breakers: How to protect systems from cascading failures. 𝟴. CDNs (Content Delivery Networks) • Static Content Delivery: Why use a CDN, how does it work? • Caching at the Edge: How CDNs improve latency for end users. 9. API Design and Rate Management • REST vs. GraphQL: Difference and practical use-cases for each. • Pagination and Filtering: Strategies for efficiently fetching data. • API Versioning: Best practices for evolving APIs. • Throttle Requests: Why rate limiting is essential, algorithms like token bucket, leaky bucket. 10. Search Systems • Indexing: Building and maintaining indexes for fast search. • Full-Text Search Engines: ElasticSearch, Azure AI Search. • Ranking and Relevance: Basic understanding of how scoring works. 11. Monitoring, Observability and Security • Metrics Collection: Prometheus, Grafana. • Distributed Tracing: OpenTelemetry, Sentry. • Centralized Logging. • Authentication and Authorization: OAuth, JWT. • Encryption: Data in transit vs. data at rest. If you master these 11 areas, you'll be ready for most system design interviews thrown at you. Add more if you can 👇
24
123
886
40,820
CRM & SaaS Full Stack Engineer retweeted
Most backend interviews don’t fail on Kafka. they fail on “what happens when this cache is wrong.” BookMark it 🔖
🤖 Made with AI
1
15
86
2,031
CRM & SaaS Full Stack Engineer retweeted
Introducing Zod 4.5 and its flagship feature: SCHEMA COMPILATION Just z.compile() any schema and get back a new precompiled schema that's 3-9x faster
68
116
12
2,150
123,267
CRM & SaaS Full Stack Engineer retweeted
Why Axum? Tokio's HTTP framework: typed handlers and extractors. • Rust + Axum • Next.js • PostgreSQL + SQLx • Gemini • Docker • @rustrover @JetBrains Full video: youtu.be/53onIhscyks
7
14
1
153
16,327
CRM & SaaS Full Stack Engineer retweeted
There are 4 types of memory you must understand if you want to build AI agents: 1. Internal knowledge: baked into the LLM weights. 2. Context window: what the LLM sees during the current inference. 3. Short-term memory: recent interactions, active state, and retrieved information held in memory (RAM) during the active session. 4. Long-term memory: persistent information stored outside the agent. The closer memory is to the LLM, the easier it is to use. The further you move from the LLM, the more infrastructure you need to retrieve the right information and bring it back into context.
20
78
342
10,710
CRM & SaaS Full Stack Engineer retweeted
Hono is a web framework built on Web Standards that runs the same code across any JavaScript runtime, from Cloudflare Workers to Node.js. - Ultrafast RegExpRouter avoids linear loops. - `hono/tiny` preset is under 12kB with zero dependencies. - Built-in, custom, and third-party middleware included. - First-class TypeScript support with clean APIs. Explore it here: osp.fyi/hono
5
24
1
231
17,929
CRM & SaaS Full Stack Engineer retweeted
The ALU and the Register File youtu.be/L5MMUT_HaNE The relationship can be shown more clearly as following picture. The registers provide values. The ALU processes them. The result can then be written back into a register. This creates one of the fundamental data paths inside a CPU. The CPU repeatedly moves data through structures like this while executing instructions.
5
19
506
CRM & SaaS Full Stack Engineer retweeted
Kafka OR RabbitMQ Which one would you choose for millions of events per day
61
49
1
349
19,316
CRM & SaaS Full Stack Engineer retweeted
Just launched today pgbot.dev 🤖🐘 Postgres intelligence for agents & apps. Free. Open source. Written in Go. Nobody wants to stare at PostgreSQL dashboards all day. So I built a bot that does it for you. → finds what’s wrong → explains what changed → tells you what to fix first Metrics are data. pgbot gives you answers pgbot can: +PostgreSQL health monitoring +Query performance analysis +Slow query and regression detection +Locks and blocking query insights +Table and index analytics +Vacuum and autovacuum visibility +Database growth tracking +AI root-cause analysis +AI-powered recommendations +Direct connection or agent-based private access xitter.cf/alxshp/status/20872236…
Launched today pgrun.dev metrics 📈 What PostgreSQL metrics should you monitor in production? → CPU + load → Memory → Disk usage + I/O → Network traffic → Active / total connections → Cache hit ratio → Query throughput → Deadlocks → Database size → Commits vs rollbacks We shipped all of this in @pgrun_dev 1h → 30d history. Postgres + system health in one view. xitter.cf/alxshp/status/20847096…
29
69
6
659
100,526
CRM & SaaS Full Stack Engineer retweeted
¿cómo migrás un monolito a microservicios sin reescribir todo el sistema? una estrategia muy usada es el Strangler Pattern. en lugar de reemplazar toda la aplicación, migrás una funcionalidad por vez. por ejemplo, las notificaciones. 1) hoy las notificaciones se procesan dentro del monolito. 2) creás un microservicio que se encargue de esa funcionalidad. 3) a partir de ese momento, el envío de notificaciones pasa a estar a cargo del nuevo servicio, mientras el resto de la aplicación sigue funcionando en el monolito. 4) cuando comprobás que todo funciona correctamente, eliminás esa funcionalidad del monolito y repetís el proceso con otra. ¿cómo suele implementarse esto? una opción muy común es poner un API Gateway o un Reverse Proxy delante de la aplicación. ese componente recibe las requests y decide a qué sistema enviarlas: al monolito o al nuevo servicio. de esa forma, el sistema viejo y el nuevo pueden convivir durante toda la migración.
2
51
1
437
17,549