kavishcan

Just Start Building | | Currently trying to be better day by day.

[kavishcan @kavishcan]

Effort matters more

[Greg Brockman @gdb]

self improvement prompt for codex

[spidey @lochan_twt]

"Claude usage limit reached. Your limit will reset at 3:30 PM"

[Theo - t3.gg @theo]

SaaS (Slop as a Service)

[Tobias Schmidt @tpschmidt_]

AWS just announced Claude Platform on AWS.
No Bedrock required!!

You get Anthropic's native Claude experience directly in your AWS account!
- IAM handles access
- Billing is consolidated
- CloudTrail logs everything alongside your other services

[kavishcan @kavishcan]

If you don’t understand it, don’t push it, simple as that.

[Bleap @BleapApp]

giveaway time!

win a Claude Max 5x subscription

to enter
> follow @BleapApp
> rt and like this post

winner will be selected in 24 hours

(btw, you get 20% cashback when using a Bleap card for your claude subscription anyway)

[Andrew Brown @andrewbrown]

@freeCodeCamp Claude doesn't know Claude Code itself as much as you might think, and there were so many times things did not work as expected and I was using my old school ways to pull us through it to the end.

The human still knows best.

[Immanuel @immanuel_vibe]

Prepping for a DevOps / SRE interview?
Don't sleep on this free q&a hub
👉 https://t.co/SRBCxtjFk3

Its like a compact roadmap of what you actually need before interview day hits you

Everything's grouped by real tech areas:
- Ansible, AWS, Docker, GitHub Actions, GitLab CI/CD, Kubernetes, Linux, networking, Terraform, PostgreSQL - and more

That's the whole point
You study by stack, not by random trivia that goes nowhere.

Here's how to actually get the most out of it:
1. Run topic drills, pick one area - say Kubernetes. List the core internals. Then walk through real stuff like readiness vs liveness probes, or ingress vs service mesh. Why would you pick one over the other? Think it through

2. Turn questions into cheatsheets. Write your own notes. Real-world tradeoffs - canary vs blue/green, circuit breakers, retries, timeouts. In your own words, not copy-paste

3. Mix basics with system thinking. For networking, don't just memorize ports. Trace a request through a 3-tier app and ask yourself - where can this actually break?

4. Connect concepts to reliability goals. Map IAM, VPCs, autoscaling to SLOs and error budgets. The goal is explaining why decisions get made, not just what they are

5. Practice talking through outages. Pick a "service is down" scenario. Walk through metrics -> logs -> traces -> recovery. That's literally what SRE interviews are testing for

No fluff, no filler

#interview_questions #devops #sre #cloud #kubernetes #k8s #terraform #linux #interview #aws

[Shu @shuding]

Miss the old days of open source. Code carried a piece of its maker. Software made with <3.

[spidey @lochan_twt]

when you realise you’re only 1 Claude tweet away from unemployment

[kavishcan @kavishcan]

The future of AI agents is exciting — but uncertain. Will they empower us or replace us? One thing's clear: the world won't look the same. Buckle up. 🌐

[kavishcan @kavishcan]

Always write/have architectural decision records!!!! (Non negotiable)

[Simon Willison @simonw]

I've published the first two chapters of a new guide to Agentic Engineering Patterns - coding practices and patterns to help get the best results out of coding agents like Claude Code and OpenAI Codex https://t.co/XIskcgeBFE

[Piyush Sachdeva - Building CannerAI 🚀 @techie_piyush]

Unpopular opinion: If you are just starting out with 0 users, you dont need you dont need Kubernetes, you dont need Docker, you dont even need a self managed VM. You just need a VPS or a web hosting service like vercel and you should be good for many thousand users.

[Midas @midascabal]

"AI is a bubble"

[Y Combinator @ycombinator]

A very special guest on this episode of the Lightcone! @bcherny, the creator of Claude Code, sits down to share the incredible journey of developing one of the most transformative coding tools of the AI era.

00:00 Intro
01:45 The most surprising moment in the rise of Claude Code
02:38 How Boris came up with the idea for Claude Code
05:38 The elegant simplicity of terminals
07:09 The first use cases
09:00 What’s in Boris’ https://t.co/OAtnXdxccP?
11:29 How do you decide the terminal’s verbosity?
15:44 Beginner’s mindset is key as the models improve
18:56 Hyper specialists vs hyper generalists
21:51 The vision for Claude teams
23:48 Subagents
25:12 A world without plan mode?
28:38 Tips for founders to build for the future
30:07 How much life does the terminal still have?
30:57 Advice for dev tool founders
32:11 Claude Code and TypeScript parallels
35:34 Designing for the terminal was hard
37:36 Other advice for builders
40:31 Productivity per engineer
41:36 Why Boris chose to join Anthropic
44:46 How coding will change
46:22 Outro

[Boris Cherny @bcherny]

Sonnet 4.6 is now live in Claude Code. It's cheaper than Opus 4.6 and nears Opus-level intelligence, and devs in early testing often preferred it to Opus 4.5. Now the default for Pro and Team plans.

[kavishcan @kavishcan]

@techyoutbe SD-Visual-Guide

[Tech Fusionist @techyoutbe]

🚨 24-HOUR SYSTEM DESIGN GIVEAWAY 🚨

System Design feels scary…
Until you see it explained visually.

For the next 24 hours ONLY, I’m giving away

🎁 FREE copies of
“System Design: A Visual Guide – From Zero to Confidence” 🎁

No heavy theory.
No boring walls of text.
Just clear visuals + real-world analogies that actually make sense.

To get:
1️⃣ Like ❤️ this post
2️⃣ Comment “SD-Guide” or "SD-Visual-Guide"
3️⃣ Repost 🔁 to share with your friends
4⃣ Follow @techyoutbe (to get DM)

Don’t overthink system design.
Start seeing it. 🚀

[Shu @shuding]

We’ve added 12 new rules to the React Best Practices skill. To install or update it via https://t.co/t1sGqu1d8j, run:

npx skills add vercel-labs/agent-skills --skill vercel-react-best-practices