Excellent Opportunity to learn how @JioHotstar scales up 📈 in this 1st edition of ScaleUP, I will be presenting how we do Data@WC scale in 8-bit style 🕹️

So many people give over-emphasis to knowledge. It can easily be attained, especially in today's world. In my experience, I always prefer Agency >> Skill >> Stack familiarity If the candidate has high agency, they will be able to acquire any skill and learn any tech stack.

Simplest way is to think of it like ProgramOfThought module but applied to prompts as well

Hyrum's Law: with a sufficient number of users of an API, it does not matter what you promise in the contract: all observable behaviors of your system will be depended on by somebody. Making Postgres connections faster broke implicit rate limiters!

We at @tursodatabase have just done something unheard of in the startup world: we hired a person in prison. Not an ex-con: he is actually serving time right now. If you follow us you may remember when we announced our full rewrite of SQLite in Rust, Project Limbo. It got a tremendous amount of attention, but by far, my favorite story was that of @PThorpe92: Preston is currently incarcerated for things he regret doing a decade ago. A model reformed inmate, Preston was given the beautiful opportunity by the Maine Department of Corrections to access the internet. He then found our project, and since it's not like there are many entertainment options competing for his attention in prison, he decided to pour his heart and soul into helping us rewrite SQLite. I immediately fell in love with his story. Reading his old blogs, his Github profile. I prayed we would be able to hire him as soon as he was out, and make him a part of our team. But thankfully, things have happened in such way, that we were able to do it *even before* he was released. He's now given an opportunity to make a dent in the world, from prison. Preston claims he is immensely thankful for this opportunity. It is certainly not an opportunity that comes often, and I understand him. But when I read his story in his personal blog, where he mentioned how he clearly saw his life going downhill, had this sudden epiphany, saw clearly that he could do differently, and then started being showered with blessings, I saw the unmistakable markings of how our Lord Jesus Christ, the Lamb of God, operates in the world. I was an obnoxious Richard Dawkins-style atheist for more than two decades. I am not an experiential person, and I came to a change through the rational evaluation of the historical context of His resurrection. I am not the kind of person that feels the hand of God in my life, but over the years I learned to recognize his patchwork through those sudden, unexpected changes, where everything suddenly "just works". And because of that, I am the one who's thankful. The Lord decided to operate such a drastic change in Preston's life. Clearly He has a great plan for him. I am immensely thankful for the opportunity to play a small part in that story. God, in his infinite power, doesn't need me to do any of that, and yet he gave me the opportunity to act. I feel thankful and blessed. I am also very thankful to @LabsUnlocked , and entity helping people like Preston find a better life once they're out. If you feel inspired by their mission, you should reach out and help. And if you want to hear from Preston in his own words, read the article he just published on the Turso blog: turso.tech/blog/working-on-d…

Can someone recommend a good UUID? I've searched a lot and a8098c1a-f86e-11da-bd1a-00112444be1e seems pretty random. Want to make sure no one else has used it before!

Wake up babe, LLama 4 just dropped with 10M context window. Now I can finally fit all the tailwind css class names in it

I guess it's time to move to Wayland bugs.kde.org/show_bug.cgi?id…

BREAKING: LinkedIn to change its iconic celebratory images

Now that text in GenAI has finally been solved by OpenAI o4, when will the correct number of fingers be solved?

Are you a transformer? Because attention is all you need!

I continue to experiment with Go versus Rust, reimplementing the same functionality in both languages to compare & really understand both tools from a realistic, unbiased view I can understand why there are lots of loud anti-Rust people, because I too remember how annoying it was at first not understanding any of it and thinking "why would anyone ever overcomplicate to this degree when a simpler language can do the same just fine". Constant errors, the compiler always screaming at you, wtf is an Arc<Mutex<>>, wtf is a Clone trait...? It's easy to hate, because anyone supporting this difficult madness has to be a dumb ego-coder, right? After all "an idiot admires complexity, a genius admires simplicity" Well I'm really thankful that I stuck with the annoyingly difficult Rust, because these days when I code idiomatic Go and idiomatic Rust side-by-side, the Go really isn't "simpler". Sure, there are fewer keywords. Sure, there are fewer concepts one has to understand to get started. But at the end of the day, I always feel it's easier to wrap my head around the Rust code when I ask myself 1) what does this code do and 2) what can go wrong The biggest factor for me is that Rust code is often less LOC for the same logic AND verifiably safe (as long as there's no `unsafe`, of course). Instead of being distracted from the happy path with `if err != nil` you get the same by the simple `?`. match is fantastic for describing conditional logic in a simple way. Zero cost abstractions! You can write crap code in both. You can write overly complex code in Rust overusing generics, Arcs, whatever, just as you can write overly verbose messy code in Go. A bad architecture is not the language's fault. And I remember how easy it is to make bad design decisions when you're still learning the language, something I wrongly blamed Rust for while I was learning it. At the end of the day I really feel Rust is an investment. It takes time and it's annoying, sure. But once I grasped the concepts of the language and got comfortable with it, I really don't feel more productive in Go and I don't feel it's simpler. If anything, Go is more annoying because it takes more LOC for the same logic, it's not as safe (read: future me needs to deal with this in prod), and it's often slower at runtime than the Rust counterpart. Also, Cargo is the nicest tooling I've ever had the pleasure of using. And back to the anti-Rust people, I get it: when people sharing Rust success/praise it's easier to brand them as "cultists" than admitting it's a skill issue. The only things I like about the language is that 1) it's easy to onboard if there are lots of devs on the same project of varying skill and experience, 2) the stdlib having most of what you need is really nice, and 3) there's no function coloring (which is something you pay for with CGO overhead). This slideshow (pic) from this (youtu.be/QrrH2lcl9ew?si=Hx18…) talk shows what happens when devs get comfortable with Rust This (longer than expected) post is what I wish I'd read a couple of years ago when I got into the "simplicity bro" mindset of Go thinking all Rustaceans were dumb ego-coders

Men will do anything to avoid going to therapy

C: Hey, can you hear me? S: Yes I can, can you also hear me? C: Yes I can

It would be so funny if @cursor_ai IPO'd before GTA6... oh wait, that's actually a possibility

At this point, we should just agree that Claude Sonnet 3.5 was a lucky epoch seed

#Terraform is that distant cousin who's always saying you can count on him but when you need him to come, his phone is always unreachable Any time you don't touch TF for a month of two, the plan always fails 😥

Vibe ReOrg now that's what most companies need!