Manu J

Puma, Falcon, or Pitchfork? Choosing the right web server for your Ruby app is a big decision. In my @railsconf talk, I break down the key differences, performance trade-offs, and how to choose the right one for your specific application. youtu.be/gLYx83CaCNw?si…

Her name was Lini Puthussery. She was 31 years old. A nurse at the Perambra Taluk Hospital in Kozhikode Kerala. She had been working there for six years. She had two sons. Ritul was five years old. Sidharth was two years old. In May 2018 the Nipah virus arrived in Kerala. Two brothers and a relative were brought to the hospital with symptoms nobody had seen before. Lini was on night duty when they arrived. She cared for them through the night. They died soon after. Confirmed Nipah positive. By Friday Lini herself had fallen ill. She was shifted to the ICU at Kozhikode Medical College Hospital. When she learned she had contracted the Nipah virus she asked the hospital not to allow her two sisters to visit. She did not want them exposed. From the ICU she wrote a note to her husband Sajeesh. “Sajeesh I am almost on my way. I don’t think I will be able to see you. Sorry. Please look after our little ones and take them to the Gulf. They should not be alone like our father. Lots of love.” She died on May 21, 2018. Her body was cremated quickly to prevent the spread of infection. Her family could not say a proper goodbye. She did not hesitate when the patients arrived. She did not ask who would care for her sons if she fell ill. She showed up for her shift and did her job. Today is International Nurses Day. Her name was Lini Puthussery. She deserves to be remembered.

Pulled 120+ malicious packages from @rubygems today. The target wasn't end users - it was RubyGems itself (XSS, data exfiltration). Reminder: sometimes the registry is the one under attack. #ruby #rubygems #security

Never seen this error from Google before in 20 plus years of using it.

Carbon Fiber is a high performance Ruby Fiber Scheduler powered by Zig and libxev (same as used in Ghostty). I've just released a new version: updated to Zig 0.16, latest libxev. Some optimizations, too—it's now faster! (benchmarks in README) github.com/yaroslav/carbo…

@better_auth Do the plugins listed under enterprise require an enterprise plan OR are they listed there as "enterprise features" ?

Really exciting to see Herb being adopted at GitHub! 🌿 Over the past months, the GitHub team has been running Herb across one of the largest Rails codebases out there where Herb helped uncover real issues missed by existing tooling while also providing invaluable feedback. 🙌

Claiming that "all my code is now written by an agent" is ambiguous. It includes: 1. Folks who know what they are doing and care about software design, who can now produce code much faster. 2. Vibe coders who treat the agent as a black box that generates a working system. I validate daily that, with the current models, vibe coding is not suitable for building minimally maintainable systems. Agents introduce major internal quality issues quickly and spread them even faster because they echo existing patterns so well. I see two challenges for programmers today: First, learning how to do (1) properly: how to create the right context for agents, how to orchestrate them and manage their memory, how to remove toil, parallelize work, etc. In other words: maximize the value we can extract from this new sorcery. Second, vibe coding is fantastic for non-programmers to create value by doing things they could not do before: quickly iterating on ideas, automating workflows, building ad-hoc tools, and so on. The key question is: where internal software quality starts to matter, and how to enforce it without diminishing this new source of value. I am also increasingly convinced that many companies that blindly embrace vibe coding and chase futuristic PR headlines are about to discover the terrors of technical debt at scale.

I've been working hard on getting Syntax Tree migrated to Prism, and I keep having "oh but this one more thing" moments. The rabbit hole is deep on this 🧵. For context, the PR I'm trying to get pushed over the finish line is: github.com/ruby-syntax-tr…

@robzolkos @andrewculver What have you both learnt and how? I'm finding that LLMs are great at filling in gaps (known unknowns) but for something completely unknown I'm not confident of trusting it 100%.

@andrewculver Everything. Ive learnt more in the past 12 months than probably the decade before.

I love how easy it is to learn new things in the AI era. I'm cranking through a backlog of stuff that previously felt too difficult or time consuming to conquer. What new stuff are you learning?

Instead of going back and forth with your agent saying "hmm little more, no a little less" just ask it to build you a control to tweak it yourself, then give it the params you like.

@mrkaran_ How are you splitting the work between the two?

I am loving how good of a combo of kimi 2.6 + gpt 5.4xhigh feels for pretty much any task. You won't miss slopus at all with this.

Back from my hibernation and looking for my next gig. Open to software developer / architect / CTO roles (contract or full-time). Link in bio. DMs open. Retweets appreciated! 🙏 Experienced in building high-performing organizations, highly-scalable software systems, and high-growth SaaS products in multiple verticals. Deep familiarity with #openai, #azure, #dotnet, #typescript ecosystems.

An alternative to descript from the creator of asdf!

@bradgessler @_byroot Looks like it is the default behaviour after rails 7.2 and you should set `config.active_record.permanent_connection_checkout = :disallowed` or `deprecated` to find where your connections are being held permanently #config-active-record-permanent-connection-checkout" target="_blank" rel="nofollow noopener">guides.rubyonrails.org/configuring.ht… gist.github.com/ioquatix/f419b…

@techsutra @_byroot Rails 8.1. I didn’t see auto release in the source, but that’s the thing I need, ideally in a block for LLM calls. Did you see it in a PR somewhere?

Less contention overall, but I'm still running into threading issues when I have a bunch of LLMs running on a background job on a server. Has anybody else run into this?

@mrkaran_ @VictoriaMetrics That's great to hear!

Yes, in fact that’s the direction I'm working towards. I’m actively refactoring Logchef to support multiple backends, and I’m currently experimenting with VictoriaLogs (from @VictoriaMetrics) as one of them. DuckDB/Parquet is also something I want to support, especially for small deployments, local-first setups, and single-node use cases. I wouldn’t promise a timeline yet, but it’s definitely on the roadmap as part of making Logchef - so you get auth/rbac/alerts etc out of box!

@mrkaran_ The vector integration link from logchef.app/getting-starte… (at the bottom) gives a 404

@mrkaran_ Thanks for making this freely available! Do you have any plans to add duckdb/parquet support?

@techsutra Fixed. sorry and thanks for reporting! logchef.app/integration/ve…

@_swanson @bradgessler @ioquatix Yep. Exactly!

@techsutra @bradgessler @ioquatix I see so something like: - Select text and ask llm "fix any typos" could be a http request that runs for 30sec with falcon - When an email is received, run a set of rules against is would be done in a background job (via async-job)

@_swanson @bradgessler @ioquatix It depends. Unless the user is waiting for the result and an error be bubbled up to the user in realtime, I would rather use a background job for observability, retries, known scaling mechanisms etc.

@techsutra @bradgessler @ioquatix I see -- though in this case, blocking IO might be triggered from outside an HTTP request (webhook comes in -> run a pipeline of LLM calls) -- would you have that make another http call? or queue jobs?

You are building a Rails app that runs agent flows / pipelines so you end up making lots of blocking inference API calls Is the future: - Running a bunch of async jobs - Offload I/O heavy work and get callbacks - Something else Consider that tool calls need to hit Rails app