Vivek Bhadauria

That is where it gets interesting. I find that models a lot of times don't care about abstraction that humans can hold in head or don't even create much of an abstraction without steering or explicit skills, etc. Even with all that the rate at which humans can review code is going to be slow that model can generate. One thing which has been working for me is create tasks upfront and then drive implementation using that (at least limits what all is going to be touched in that task scope)

@diptanu Whenever models start producing viable and self-maintainable code. I really don’t feel Fable is there.

I have a Fable authored PR: +25k -3k It works great, but ... If it were to get merged now, it would condemn the project to be Fable vibed only from now on. Now it is time to pare it down, cut over-complication and it under control and fully back in to my mental model.

Was trying to create 3D visualization of components to see how req/packets flow in k8s. doesn't look good though

Why is India so filthy? What solutions? Must watch! Bengaluru 💜

Vibe coding will make you millionaire

@shantanugoel I had similar one in Red color 😁

Say no more!

Claude context management kicking in midway

parampara, prathishta, anushasan pre-training, alignment, post-training

Not a good decision to force engineers to become source of "good quality human data" for LLMs.

Using Claude to do complete security analysis is pretty fun. Like asking it that you are given a k8s cluster, tell me why 1 Pod can't spoof as packets coming from another Pod on the same node. And then use it to understand all things in between. It helps in accelerated learning. Did Pod spoof testing sometime back -github.com/viveksb007/spo…

@nikunj @sonofalli curious, are you committing the itinerary in git?

@sonofalli Thanks Claude Code ftw

could AI build this

raised PR to fix github.com/bWanShiTong/op… Using agents like CC, its easier than ever to dive deep into unknown code-bases and fix issues. But we need to be careful, otherwise it fixes 1 thing and breaks another. In this specific case, there was a bluetooth quirk b/w how linux and mac handle those. The change that CC made was introducing behavior change in linux in edge cases which it initially didn't bothered but if asked explicitly, figures out the linux specific behavior changes and adjusts it. I am still new to this BLE handling and could be way off as I am basing my understanding from LLM back and forth research and discussion.

used openwhoop-app, had to make some changes to get it running on Mac. repo link - github.com/bWanShiTong/op…

I had cancelled Whoop sub sometimes back. Tried pulling Whoop data from my device after longtime.

@RilRil @the2ndfloorguy I was trying something similar a while back to pull data out of my Whoop as I was gonna cancel the sub. Faced some hiccups at that time. Now I tried this again using github.com/bWanShiTong/op… and its working \O/.

@viveksb007 @the2ndfloorguy WHOOP straps expose the standard BLE Heart Rate Service (0x180D) when broadcast mode is on,

i hooked my whoop to my work calendar to find which coworker gives me the most stress 🚨 thanks to fable, I reverse engineered whoop to pull per minute heart rate. nd matched spikes with cal events and attendees I now have a leaderboard and I think about it daily. few info masked for obvious reasons ;)

I'm starting something new in my blog: one guest every month, walking through the internals of Open Source projects from their own point of view. They are going to take the first post of every month (The first Monday of the month). I'm extremely happy to have already 3 outstanding engineers in the queue. I would recommend you to go and check what they are doing (probably follow them). First up for July is @func25 from VictoriaMetrics. If you've ever fallen down a rabbit hole reading how the sync package works there's a good chance you were reading Phuong. His series on the sync package internals are very good. He's also the author of The Anatomy of Go, a deep dive into how the language actually works under the hood, from data structures and assembly to memory, the GC, and concurrency. Exactly the kind of guest this series is about. And the lineup keeps going: 🔹 @alextrending, will be the August post, he is Principal Engineer at Memed, author of System Programming Essentials with Go, and a relentless community builder. Lately he's been on stages everywhere with talks like "Green Tea GC: The Insight Behind Go's New Garbage Collector," "Tug-of-Code: The battle for efficient iteration in Go," and "Why Go Hides Spin Locks?" His blog (alexrios.me) is a goldmine on Go internals, systems programming, and tech leadership. 🔹 @mdelapenya will be the author of September guest post. He is an open source engineer at Docker and core maintainer of testcontainers-go, the library that's quietly become a the facto standard on how to write intengration tests in Go. Also, you can check out his blog, where is already talking about some internals of testcontainers. The goal is simple: make the scary parts of Open Source internals approachable, for interns, for seniors, for anyone who's ever typed a function call and wondered what really happens next.

Guess this still qualifies for my order partially filled.

Nothing better than waking up to CC solved some obscure bug in the night, now time to understand how - Cross-node NodePort SNAT — SOLVED ✅ Committed 4fb51af. The hard problem is done.

@davidcrawshaw New blog coming on exe.dev?