Claude Code creator:
"Since Opus 4.5, i uninstalled my IDE. I don't edit a single line of code by hand.
100% my code is written by Claude."
in 1-hour Y Combinator podcast, Boris Cherny reveals his daily Claude Code setup.
Claude Code + loops + dynamic workflow
Worth more than a $500 vibe-coding course.
Masa-masa itu udah berakhir. Masa-masa itu namanya ZIRP.
Dapat gelontoran gaji dan duit segitu ya karena orang kaya ga mau beli bond US, jadi mending berjudi dengan invest ke tempat yg beresiko.
Ya, bisa gaji segitu ya karena demand talentanya gede krn harus churn fitur cepat.
Syahrul P. Utomo retweeted
Anthropic just paid millions to hire Andrej Karpathy.
He gave you the same knowledge for $0 the same week.
Co-founder of OpenAI. Former head of AI at Tesla. The man who coined vibe coding.
No recruitment fee. No exclusive access. Just a link and 29 minutes.
LLMs are ghosts not animals.
Vibe coding is dead.
Software 3.0 is here.
Watch it.
Then read this.
Because Karpathy tells you what Software 3.0 is.
This shows you how to build one - a software factory with Claude Code that ships features while you sleep.
The full build guide is below.
Syahrul P. Utomo retweeted
Life update! Beberapa bulan lalu gw kena layoff di Belanda 🥲 namanya juga kehidupan
Siapa tau ceritanya bisa bermanfaat buat org lain!
Syahrul P. Utomo retweeted
Tahun 2017-2018, waktu net worth masih sekitar $2 juta mostly saham, daku lagi bikin persiapan buat pulang ke Indonesia. Sebagai orang yang udah kerja sejak 2009 dan nerima gaji, aku ga nyaman dengan konsep "kumpulin duit yang banyak, terus tarik 4% per tahun"
Sehingga aku nyari mentor keuangan. Mentorku ini very big in property. Beliau bilang aku perlu investasi di properti soalnya aku butuh cashflow buat ngerasa nyaman. Kami melakukan analisa dan karena aku nyarinya cashflow bukan growth dari harga properti, maka kami memutuskan lebih baik investasi di properti di US
Fast forward to 2020, aku punya 25 properti dan cashflow sekitar $20k/bulan dari properti. Tapi somehow ngerasa lebih miskin
Ada aja rumah yang rusak tiap hari, keluar duit
Pekarangan perlu dipotong rumputnya, salju perlu dibersihin, keluar duit
Tenant ga mau bayar sewa padahal rumah udah dirawat, keluar duit
Tenant melihara anjing, anjing ngerusak karpet, ganti karpet, keluar duit
Tenant ngerusak pemanas, nyolong AC, keluar duit
Akhirnya 2023 aku jual hampir semua propertiku, tinggal sisa dikit buat gaya2an aja
Investasi properti itu ga bagus kalo kita ga bisa menggunakan semua keuntungan dari properti: cashflow, value appreciation, tax benefit, debt leverage
Sewa rumah itu yieldnya cuma 2-4% dari harga beli/bangun rumah
Sewa kos2an yieldnya cuma 4-8%
Sewa unit apartemen paling bagus 15%, karena dipakai untuk adegan dewasa
Dari pembelajaran selama 5 tahun ini aku belajar 2 hal besar:
1. "kumpulin duit yang banyak, terus tarik 4% per tahun" itu mindset yang lebih bener. Lebih banyak cara ngumpulin duit banyak + narik 4% daripada investasi dengan cashflow yang bagus yang kebal inflasi
2. Yang perlu dibenerin itu mindset kita. Kalo kita ga nyaman dengan the world operate, dan kita ga punya power to change the world, we change our mindset
So yes, please set one large financial goal and take steps to get there. Figure out your financial freedom number, then figure out how to get that number
Jangan mikir "aku mau pensiun dengan income 100juta/bulan"
Pikir "aku perlu punya duit berapa biar punya income 100juta/bulan"
As you mature (age 30) you realize that leverage is not hustling 24/7 but rather setting one large personal goal and one large financial goal and taking steps every day towards achieving them
You also learn that all it takes is 3-5 hours a day in the right direction 365 days a year
The rest is performative BS which in turn will have you missing out on spending time with your family and friends
There is no permanent underclass for those who refuse to partake in the rat race
As Sam Walton the founder of Walmart famously said: "I was asked what I thought about the recession. I thought about it and decided not to take part"
Forge your own path, and you’ll be happier for it
Syahrul P. Utomo retweeted
Disuruh bayarin listrik rumah sama ortu. Yaudah saya bikin dashboard di Grafana supaya gampang kelihatan kalo ada pemakaian listrik yang boros.
Sumber datanya dari Home Assistant, di-ingest ke Prometheus, lalu disajikan dalam bentuk dashboard di Grafana.
Mungkin berikutnya mau setup alert, supaya kalo ada perangkat yang konsumsi dayanya terlalu boros bakal kirim notifikasi ke WA / Telegram.
Syahrul P. Utomo retweeted
DevOps Project Ideas
• Dockerize a backend app (multi-stage builds)
• Build a CI pipeline (test + lint + build + push image)
• Setup CD to deploy automatically on a VPS
• Configure Nginx reverse proxy + SSL (Let's Encrypt)
• Create a full Docker Compose stack (app + db + redis)
• Setup centralized logging (Loki + Promtail + Grafana)
• Setup monitoring + alerting (Prometheus + Alertmanager)
• Build a basic Kubernetes deployment + service
• Add readiness/liveness probes properly
• Setup Ingress + TLS in Kubernetes
• Implement secrets management (K8s secrets / Vault basics)
• Build a blue-green deployment pipeline
• Setup autoscaling (HPA) with load testing
• Write Terraform to provision cloud infrastructure
• Setup backup + restore automation for databases
Backend Development Project Ideas
• Authentication API
• CRUD API For Users
• Blog Backend
• URL Shortener
• Pagination and Search API
• File Upload API
• Rate Limiter API
• Muti User chat Application
• Multi role user System
• O Auth2 Login API
• Job Queue System
• Recommendation System
• Video Steaming Service
• High Performance API With Caching
• Distributed File Storage System
Syahrul P. Utomo retweeted
Backend in 2026: Learn these 9 skills or get left behind 🥶🔥
1) REST + gRPC APIs
2) Modern Auth (Passkeys > JWT)
3) SQL + NoSQL mastery
4) Redis caching patterns
5) Kafka-level event systems
6) Async & reactive code
7) Microservices + service mesh
8) OWASP + zero trust
9) OpenTelemetry observability
Backend Development Project Ideas
• Authentication API
• CRUD API For Users
• Blog Backend
• URL Shortener
• Pagination and Search API
• File Upload API
• Rate Limiter API
• Muti User chat Application
• Multi role user System
• O Auth2 Login API
• Job Queue System
• Recommendation System
• Video Steaming Service
• High Performance API With Caching
• Distributed File Storage System
Syahrul P. Utomo retweeted
As an Engineer you should know the following concepts
Idempotency → Prevents duplicate payments
Pagination → Keeps your DB from dying
Versioning → Lets you evolve APIs without breaking clients
Rate limiting → Protects your service from abuse
Error codes → Helps clients handle failures correctly
Caching → Reduces load by 90%
JWT security → Prevents leaking sensitive data
N+1 queries → The difference between 10ms and 10s response time
Docs → Stops the `how does this API work?` Slack messages
Consistency → Choose the right tradeoff for your use case
Syahrul P. Utomo retweeted
Don’t overthink backend.
• Learn HTTP → how the web talks
• Learn Databases → how data lives
• Learn Caching → how apps get fast
• Learn Auth → how users stay safe
• Learn APIs → how systems connect
• Learn Background Jobs → how work happens async
• Learn Logging & Monitoring → how to debug production
• Learn Testing & CI/CD → how to ship confidently
You don’t need every framework.
Just master the fundamentals that power every backend. ⚙️
Syahrul P. Utomo retweeted
Top 15 Design Patterns You Should Know:
1. Singleton
2. Factory Method
3. Abstract Factory
4. Builder
5. Adapter
6. Facade
7. Decorator
8. Composite
9. Proxy
10. Iterator
11. Observer
12. Strategy
13. Command
14. State
15. Template Method
♻️ Repost to help others in your network
Syahrul P. Utomo retweeted
🚨🎥 This clear foul by Bernardo Silva on Bruno Fernandes wasn’t even checked by @FA_PGMOL.
So what’s the point of VAR if incidents like this aren’t reviewed or punished, @premierleague?! 🤦♂️
#MUFC
Syahrul P. Utomo retweeted
As a Backend Engineer in 2026 aiming for Staff, please learn:
1. One language deeply (Go/Rust/Java)
Not “I can write APIs”, but runtime model, memory, concurrency, profiling, GC behavior (if any), and how to read stack traces like a native.
2. Data modeling and storage fundamentals
Relational modeling, constraints, isolation levels, indexes, query plans, locks, deadlocks, migrations, backup/restore, partitioning. Most “scaling” problems are schema + query shape problems.
3. Distributed systems basics that actually show up in prod
Consistency vs availability, timeouts, retries, idempotency, backpressure, message ordering, leader election, clock skew, eventual consistency, and what happens during partial failures.
4. API design and contracts
Versioning, pagination, filtering, error models, idempotency keys, rate limits, backwards compatibility, and how to avoid breaking mobile clients for months.
5. Performance and capacity engineering
Latency budgets (p50/p95/p99), tail latency causes, load testing, queueing theory intuition, connection pools, CPU vs IO bound, and capacity planning with real numbers.
6. Reliability engineering
SLOs/SLIs, incident response, postmortems, alerting that does not spam, error budgets, graceful degradation, feature flags, circuit breakers, bulkheads.
7. Observability like a pro
Structured logs, metrics, tracing, correlation ids, RED/USE metrics, sampling strategies, and how to debug “it is slow sometimes” without just guessing.
8. Security fundamentals
AuthN/AuthZ, least privilege, secrets management, token expiry, OWASP basics, SSRF, injection, secure defaults, audit logs, threat modeling for your own services.
9. Messaging and async systems
Kafka/Rabbit/SQS semantics, at-least-once vs exactly-once (and why “exactly once” is mostly a marketing term), consumer groups, retries, DLQs, replay, dedupe.
10. Caching with correctness
Cache invalidation strategies, TTLs, stampede protection, read-through/write-through, negative caching, and when caching makes bugs harder than latency.
11. Infrastructure literacy
Linux basics, networking (DNS, TCP, TLS), containers, k8s concepts, autoscaling, deployment strategies (blue/green, canary), and what your cloud bill is really paying for.
12. System design, but with tradeoffs
Designing is picking pain. Learn to write down constraints, failure modes, data growth, and operational cost. Staff is judged on tradeoffs, not diagrams.
13. Codebase leadership
Design docs, RFCs, review quality, mentorship, aligning teams, reducing complexity, owning a subsystem end-to-end, making boring systems that do not wake people at 2am.
14. Pick ONE domain to go deep
Payments, search, streaming, identity, infra, data platform, etc. Staff engineers are “the person for a hard area”, not generic API writers.
Stop hopping stacks every month. Pick a lane, build proof of reliability, and become the person people call when prod is on fire. That is Staff.
This Post is from an account that no longer exists. Learn more
Backend Development Project Ideas
Beginner Level
• Authentication API
• CRUD API For Users
• Blog Backend
• URL Shortener
Intermediate Level
• Pagination and Search API
• File Upload API
• Rate Limiter API
• Muti User chat Application
Advanced Level
• Multi role user System
• O Auth2 Login API
• Job Queue System
• Recommendation System
Expert Level
• Video Steaming Service
• High Performance API With Caching
• Distributed File Storage System
Backend Development Project Ideas
Beginner Level
• Authentication API
• CRUD API For Users
• Blog Backend
• URL Shortener
Intermediate Level
• Pagination and Search API
• File Upload API
• Rate Limiter API
• Muti User chat Application
Advanced Level
• Multi role user System
• O Auth2 Login API
• Job Queue System
• Recommendation System
Expert Level
• Video Steaming Service
• High Performance API With Caching
• Distributed File Storage System
Syahrul P. Utomo retweeted
AWS isn’t hard — you’ve just been learning it backwards.
Start with these first:
• EC2 → run apps
• S3 → store files
• IAM → control access
• Lambda → run code
• RDS → databases
• VPC → networking
• CloudWatch → monitoring
Learn these.
Build 2–3 projects.
Connect the dots.
That’s when AWS finally clicks.

































