Chad Lee B.

Freelancing Ruby on Rails Dev (DMs are open)

Software Engineer - Wolf/Roy SSBU main

[Chad Lee B. @chaadow]

I've just realized that I've been featured for 4 consecutive weeks!

Actively contributing to Rails has been a delightful experience, and I will surely continue to do so.

A special shout-out to Jonathan Hefner and @eileencodes for their swift and thorough reviews!

[Ruby on Rails @rails]

Thanks to all of the contributors that were included in this week’s highlights:
@p8
@flavorjones (w/thanks to @ledermann)
@_byroot
@chaadow
jonathanhefner
@bensheldon
@fractaledmind
and...

[Greg Molnar @GregMolnar]

A lot of people could learn from this. So many devs with not so much idea about security are yapping when CVEs are published and with not much substance.
Zack surely knows more about any area of security than those.

[Flow @FlowXII]

Un coach vient de réaliser sa première vente sur Shobu 🥳

[Chad Lee B. @chaadow]

@Daaninator1 bro you know because of your fair into footstool combos, i'm this close to getting out of retirement just to try them out.
Beautiful

[David Cramer @zeeg]

I'm seeing a progression of agents writing software that I have mixed feelings about.

I have been fighting the complexity battle - the sloppy code that for us is really hard to maintain. Junk building on junk, that ultimate compounds the reliability challenges you'll face in real world production scenarios.

Agents dont seem to be getting noticeably better about it.

What does seem noticeable though is their ability to manage it. The code is just as messy, complicated to reason about as before, but the agents are producing fewer broken behaviors. So more code, but they are capable of working through the overhead.

It doesn't account for the issues that arrise from that (e.g. more resources) and they certianly aren't automatically genreating performant code, but it does beg the question:

does software in the future just become unreadable for us? is it just too hard to reason about because the most efficient way build and maintain is via these coding agents?

[Lewis Buckley @lewispb]

I wrote about a recent change to improve performance during Basecamp Rails app deploys https://t.co/ImhyKi6m8B

[Stephen Margheim @fractaledmind]

https://t.co/mcvFhVasw0

[Chad Lee B. @chaadow]

@surehyper what i did a while back was muting him, out of respect for the wolf he was and how he made me love smash and wolf, I couldn't unfollow him

[Robby Russell @robbyrussell]

I sat front row for @dhh's talk yesterday morning. Having talked with him the day before, I’ll admit… I wasn’t particularly surprised (nor unprepared).

A bit of a field report from #RailsWorld: the vibe here is far from doom and gloom. Quite the contrary. Wherever our industry is headed, most of us are still employed as menders… tending to systems that customers rely on and businesses are quite happy to keep paying for.

Most of us aren’t waking up to a blank canvas and designing the architecture of the future. We’re inheriting decisions made years ago, updating old patterns, working around constraints, and keeping this shit running reliably.

I think these newer tools give us an opportunity to wonder a little more about the systems we’ve inherited. To unpack why things work the way they do. To tinker with assumptions we haven’t had the time, confidence, or permission to revisit… and share what we learn so the next person, or agent, has an easier time.

That deployment model we picked eight years ago? Worth another look. Some of our web apps probably wish they were native apps. And there are plenty of architectural decisions we’ve been living with mostly because… well, we’ve been busy living with them.

There’s plenty of understandable anxiety about what these tools mean for our work. I’m increasingly curious about what they give us permission to revisit.

Once my keynote is published, I’ll share more about a little programming-language-adjacent framework I’ve been working on for approaching exactly this kind of curiosity.

In the meantime… keep showing up. Keep wondering.

Long live Ruby. Long live Rails.

p(gloom)

[Flow @FlowXII]

Les gars vous devez voir ça, c'est un des aspects les plus importants à la progression sur n'importe quel jeu compétitif

[Chad Lee B. @chaadow]

@jamesglenos @strugglingnico @SlamDolphin @niggerVAP0RIZER lol I feel you're describing me. And yeah great purchase, I second that

[Flow @FlowXII]

Après énormément de travail...

Nous y sommes enfin. Je vous laisse lire cet article complet pour voir tout ce que Shobu propose dorénavant, car ça va bien au delà des tournois ! https://t.co/AQgXosvUpy

[jpcamara @jpcamara]

Damn it feels good to finally merge this one @rosapolis! Opened long ago, in a forgotten time of hand-coding in 2024.

Thanks for unintentionally putting me on blast @jeremysmithco and kicking me into gear on finishing it out a year ago 😆

https://t.co/42frT26HBT

[Chad Lee B. @chaadow]

@GregMolnar Applied as well!

[Chad Lee B. @chaadow]

@GregMolnar You're right. I'm actually considering having a local AI because I have a feeling Claude etc. will face outages some day.
Regarding debugging, if you're NEW into "software engineering" you're quite doomed, because this is stack overflow on big steroids. ==> laziness guaranteed

[GitHub @github]

We heard you. And we agree.

In light of recent developments in physical media, GitHub is proud to announce that you can now obtain your public repo on CD-ROM.

Keep it. Lend it to friends. Pass it on to your children.

Your code is physically yours, forever. Until you lose it, let's be real.

Order yours today.
https://t.co/z041pdMH7h

[Nate Berkopec @nateberkopec]

A lot of people want to use AI to cheat, to skimp, to be lazy, to bullshit, to pass off bad thinking as profound.

They think we can't tell. We can tell.

Use LLMs to do what wasn't possible before. To apply relentless attention and care. To turn the 8/10 into the 10/10.

[Chad Lee B. @chaadow]

@GregMolnar I did, every patch release I open a review app, and the RAM ( on a sidekiq heroku dyno ) still is x2 than on 3.4, so it's a bummer since i need the least amount of ram possible (with some leeway ) so that i can scale them to parallelize some tiny jobs that requires a bit of ram