@mewbassprr @jaredwhite if I can share a maybe useful POV about neo-parents interpretation: 1) most of the time they’re just struggling to do something that remotely work for family’s balance 2) often they are overwhelmed at the point they don’t notice that they’d need “you” until “you” are not as near as before (reasonably!).

@jaredwhite @mewbassprr I confirm, as a parent, I have not a social life. At least not in the way an adult would consider it. Rarely I hang out with adults alone and when I do my wife is at home with a double load of things to do. But the funniest part is when I’m hanging out but start falling asleep along with the baby at 9:30 pm 🤣 hard business!

@soulcutter @testdouble lovely one! TY!

I wrote a post to braindump what I'm currently working on: allowing lock-free access to class instance variables from Ractors.

https://byroot.github.io/ruby/performance/2025/05/24/unlocking-ractors-class-variables.html

There are few people as wise about software and teams as @sarahmei.
So this is definitely worth keeping an eye on. https://sarahmei.substack.com/p/hello-again

@bkuhlmann I have no doubt. I just add there are different POV about what the better choice (and overall choices similar to this one) could be given you’re playing CTO/tech lead role or external consultant or whatever else and given different kinds of team you’re working with.

…we people in software engineering always reach for a «it depends» in the end 🤣

Nonetheless I feel your point 100% shareable 👍

@bkuhlmann fwiw I’m with you. But I think that -usually- preserving the boring boilerplate of a plain initializer and plain setter/getter declaration is a value. It’s familiar and welcoming for both experts and language newcomers. At least when writing POROs.

One of my new favourite tech / software development #podcasts for some time now is @deadcode, presented by @jardo . Perhaps a bit more ruby than others but touches many more generic topics with recently @heydon, @Daojoan, @timriley, @Felienne, @CoralineAda check: https://deadcode.website

I've created a Ruby library to check for valid Tax Identification Numbers in Europe 🙌🏻
https://github.com/cults/tin_valid

It's a pleasure to write Ruby gems, can't wait for the next thing that makes sense to extract from my app.
#ruby #cults3d

@markwyner @404mediaco good to know, ty! I’ll put it in the read it later and give it a second chance, then 🙂

@markwyner @404mediaco article not found

Best AI use case so far

- bin/rails c --sandbox
- debugger (having `debug` #ruby gem installed)
- `trace call /sidekiq-book/ into: 'trace.txt'`
- `OrderCreator.new.complete_order(Order.last)`
- (chat bot) read #file:'trace.txt' and converto it into a mermaid sequence diagram with return values

This is what I expect from a useful, enabling tool.

Is Node.js the future of backend development, or just a beautifully wrapped grenade?

Lately, I see more and more backend systems, yes, even monoliths, built entirely in Node.js, sometimes with server-side rendering layered on top. These are not toy projects. These are services touching sensitive PII data, sometimes in regulated industries.

When I first used Node.js years ago, I remember:
• Security concepts were… let’s say aspirational.
• Licensing hell due to questionable npm dependencies.
• Tests were flaky, with mocking turning into dark rituals.
• Behavior of libraries changed weekly like socks, but more dangerous.
• Internet required to run a “local” build. How comforting.

Even with TypeScript, it all melts back into JavaScript at runtime, a language so flexible it can hang itself.

Sure, SSR and monoliths can simplify architecture. But they also widen the attack surface, especially when:
• The backend is non-compiled.
• Every endpoint is a potential open door.
• The system needs Node + a fleet of dependencies + a container + prayer just to run.

Compare that to a compiled, stateless binary that:
• Runs in a scratch container.
• Requires zero runtime dependencies.
• Has encryption at rest, in transit, and ideally per-user.
• Can be observed, scaled, audited, stateless and destroyed with precision.

I’ve shipped frontends that are static, CDN-delivered, secure by design, and light enough to fit on a floppy disk. By running them with Node, I’m loading gigabytes of unknown tooling to render “Hello, user”.

So I wonder:
Is this the future? Or am I just… old?

Are we replacing mature, scalable architectures with serverless spaghetti and 12-factor mayhem because “it works on Vercel”?

Tell me how you build secure, observable, compliant systems in Node.js.
Genuinely curious.
Mildly terrified and maybe old.

#NodeJS #BackendSecurity #SecureCoding #PII #Compliance #SoftwareArchitecture #ServerSideRendering #TypeScript #Java #Kotlin #Golang #Erlang #Ruby #Scalability #Observability #DevSecOps #LegacyVsModern #SecureByDesign #CompiledLanguages #CloudArchitecture #StatelessDesign #SecurityTheatre #TechSatire #LinkedInTechRant

https://github.com/rubycdp/cuprite/issues/296 has any fellow #ruby ist any experience with this issue with remote debugging with Chrome (and Cuprite, but here the driver is a detail, amirite?) Instead of opening a connection to a WS we do a GET to a google public service spitting out a lot of things plus some JS that once executed will open the requested WS... is it really like that? And what if I'm offline? Please tell me I'm completely astray.

Just released AyeVar 🏴‍☠️ a Ruby gem that raises an exception if you access an undefined instance variable.

https://github.com/joeldrapper/aye_var

I did some sort of rubber duck blogging about a patch I'm currently working on: https://byroot.github.io/ruby/performance/2025/04/26/unlocking-ractors-object-id.html

#RuboCop celebrated its 13th birthday yesterday! It's amazing how far we've come along and how strong the project is going after all that time. A huge THANKS to everyone who was part of this amazing journey so far. As usual - the best is yet to come!

#Ruby

@lucian interesting article about this https://dmitrytsepelev.dev/attr-accessor-in-ruby. O don’t know if underlying interpreter behavior changed in the mean time and I don’t know in deep the implications of jit on the matter. But it remains nevertheless interesting

@davetron5000 I'm using Phlex since 2022 and I love it, it solves most of the problems i have with the Rails frontend.