Vishnu M

Senior Software Engineer @bigbinary | Tinkerer👨‍💻

[Armin Ronacher ⇌ @mitsuhiko]

I know that AI makes me more productive yet at the same time I have very little success in speeding up the thinking part. Example from the last two days is just to come up with ways to map some of the upstream provider functionality to Pi.

It took me no time at all to slop something up that ended up with pulling all that complexity in. On the other hand providing an abstraction that works across all of them is still tricky and I feel like I'm about as fast as before, except for the parts where Pi helps me build POCs and probe APIs.

At least for what we're doing right now the easy parts got even easier and the hard parts didn't move nearly as much. Except you can turn your brain off, and pretend the hard parts are easy parts then you're good to go. But then you have slop.

Thank you for reading this rant.

[Mario Zechner @badlogicgames]

People of pi. BIG NEWS. I've sold out. Let me know how you feel about this in the comments below.

https://t.co/dy1ffkhMRf

[Anders K. Hvelplund @Falliblemusings]

Magnus Carlsen gives a great explanation of the extraordinary power of what @DavidDeutschOxf has coined the 'fun criterion'... and the perils of its negation.

[Vishnu M @vishnum_7]

@DanielLockyer Nipah is nowhere near as contagious as Covid-19. Outbreaks are usually small and contained.

[Vishnu M @vishnum_7]

@_swanson A simple solution will be to run a separate Sidekiq process with a high concurrency setting that only pulls from the "io_heavy" queue.

[Vishnu M @vishnum_7]

@_svs_ Btw he actually won the Brazil 2024 GP, not second. It was one of his best drives. And in 2025, he matched that level with a P2 finish after starting from the pitlane. Dude is a machine.

[Vishnu M @vishnum_7]

Time for some code spelunking

[DHH @dhh]

And of course the entire source code is available on GitHub as well. Any PRs that are accepted here will go into both the SaaS version and the version you can run yourself. Because it's the same codebase! https://t.co/XqA10tGFyO

[Vishnu M @vishnum_7]

There are some people you can't help but stop everything to listen to. For me, @ilyasut is one of them.

[Dwarkesh Patel @dwarkesh_sp]

“From 2012 to 2020, it was the age of research. From 2020 to 2025, it was the age of scaling.

Is the belief that if you just 100x the scale, everything would be transformed?

I don't think that's true. It's back to the age of research again, just with big computers.”

@ilyasut

[Vishnu M @vishnum_7]

Thanks @alexandre_ruban! I’m a big fan of your Hotwire guides.

[Alexandre Ruban @alexandre_ruban]

This was such a great read about performance stuff I learned (often the hard way) about Rails performance:

https://t.co/sqZ2Xxp9Bc

[Vishnu M @vishnum_7]

@dhh is such a joy to listen to. In an era of shrinking attention spans, the ability to speak with such clarity and enthusiasm for six hours straight is nothing short of remarkable.

[Lex Fridman @lexfridman]

Here's my 6 hour conversation with @dhh, a legendary programmer, creator of Ruby on Rails, author, and race car driver. This was a fun and inspiring conversation on everything from the future of programming & AI to the nature of happiness & productivity to the value of family, getting married and having kids.

X limits video length to 6 hours. So this full convo doesn't fit (by a few minutes). So, the first 6 hours are here on X. The full version is up everywhere else (see comment).

Timestamps:
0:00 - Episode highlight
1:21 - Introduction
2:32 - Programming - early days
19:57 - JavaScript
30:16 - Google Chrome and DOJ
38:03 - Ruby programming language
45:14 - Beautiful code
1:03:15 - Metaprogramming
1:06:36 - Dynamic typing
1:13:55 - Scaling
1:26:47 - Future of programming
1:44:18 - Future of AI
1:50:13 - Vibe coding
1:58:45 - Rails manifesto: Principles of a great programming language
2:23:11 - Why managers are useless
2:32:32 - Small teams
2:38:39 - Jeff Bezos
2:53:57 - Why meetings are toxic
3:01:43 - Case against retirement
3:09:00 - Hard work
3:14:38 - Why we left the cloud
3:17:48 - AWS
3:27:07 - Owning your own servers
3:33:19 - Elon Musk
3:43:01 - Apple
3:54:48 - Tim Sweeney
4:06:22 - Fatherhood
4:32:04 - Racing
4:59:08 - Cars
5:04:26 - Programming setup
5:19:35 - Programming language for beginners
5:32:53 - Open source
5:41:46 - WordPress drama
5:53:03 - Money and happiness
6:01:56 - Hope

[Vishnu M @vishnum_7]

@scottharveyco Cool. Where will the data be stored? I believe you're using a time-series database? I'd love to know about the implementation details.

[Nate Berkopec @nateberkopec]

We've tested it at a few retainer clients now and I can officially say it's a dud:

RUBY_THREAD_TIMESLICE (Ruby 3.4+) tuning does not make a difference for any real world application we've tried it on.

https://t.co/AVL2vcOWLH

[Peter Zhu @peterzhu2118]

I just published "Implementing Embedded TypedData Objects" about a feature @_byroot and I worked on for Ruby 3.3. A bit late, but better than never.

https://t.co/sePRr3TRdk

[BigBinary @BigBinary]

Continuing our “Scaling Rails” series, our next article is about understanding Queueing Theory.

Rails makes handling background jobs a breeze. We have many sensible choices. We don't have to understand queuing theory to get the job done, and that's a good thing.

However, for the folks who want to take a look under the hood, this is a great blog that discusses Little's Law, Knee curve, why high utilization could be a bad thing, and more read this blog.

https://t.co/Xc39HbB4Xq

[Vishnu M @vishnum_7]

@TonsOfFun111 @nateberkopec It's best to run multiple processes per pod(or dyno) in platforms like Heroku because of how requests are routed. It's nicely explained in this Judoscale blog.
https://t.co/xqBgUnXKVD

[Vishnu M @vishnum_7]

@TonsOfFun111 @nateberkopec One process per core would be ideal because then you don't have to worry about process switching overhead. I believe Nate is suggesting provisioning larger pods(with more cores) to allow more processes to be deployed.

[BigBinary @BigBinary]

Continuing our “Scaling Rails” series, our next article is about how Active Record handles Connection Pooling. As the applications scale, there is an increased load on database operations and connections often become the bottleneck.

https://t.co/D9rwipllVv

[Vishnu M @vishnum_7]

@jeremysmithco @jespr Do try out @NeetoRecord

[Nidhi Sarvaiya @sarvaiya_nidhi]

I came across this excellent “Scaling Rails” series by @BigBinary covering lots of great insights on Puma, GVL, performance tuning & more. Worth checking out!

https://t.co/l2kKVRb3sE

#Rails #RubyOnRails

[BigBinary @BigBinary]

Continuing our “Scaling Rails” series, our next article explores finding the correct number of threads in your Rails application.

https://t.co/QE6rGNWh4x