Mark

Longtime software developer.

[Boris Cherny @bcherny]

@Mahaximus_ I did not use the word “graph”, nor am I talking about graphs in this video. Please don’t attribute words to me that I did not say. I do encourage people to watch the video!

[Boris Cherny @bcherny]

@unicodef1wn I did not write this.. please don’t attribute stuff to me if it wasn’t me 😅

[Claude @claudeai]

Introducing Claude Opus 5.

It's a thoughtful and proactive model that comes close to the frontier intelligence of Fable 5 at half the price.

[Forrest Brazeal @forrestbrazeal]

What working in Big Tech feels like:

[DHH @dhh]

I was blissfully unaware of just how nutty things had gotten in much of Linux land, and didn't realize GNOME had been fully captured. But whatever. Great thing about open source is that we can route right around this nonsense. Thank heavens for Hyprland!

[Yukihiro Matz @yukihiro_matz]

Link: Dear Rubyists: Shopify Isn’t Your Enemy | byroot’s blog : https://t.co/SbSVd70GRL

[Mark @mrkcor]

Who would have thought? 😅 https://t.co/BemvJeZmj5

[DHH @dhh]

Long stretches of uninterrupted time is the most powerful productivity cheat for competent programmers working on interesting projects. Unbelievable what a tiny team of such individuals can accomplish. Decade after decade.

[Andy Croll @andycroll]

Finally happened. Ran out. Need more mentors at https://t.co/ytsaQdYhxF

Struggling in: Australia, Azerbaijan, China, Colombia, France, India, Indonesia, Netherlands, United Kingdom & even the USA.

Share widely.

[Amsterdam Ruby Meetup @amsrb]

Hello Rubyists! We're planning the next couple Amsterdam Ruby meetups and we're looking for places that can host us! Do you have space for 30-50 people on a Tuesday/Thursday evening 18:00-21:00 or later, including a beamer/monitor? Get in touch on Slack or at [email protected]!

[Sixo | Transformers @SixoTF]

❤️

[Facundo Espinosa 🤖💎 @faqndoE97]

A random day you’re looking something on a repo and found commits that are gems 😂 @dhh

https://t.co/2ihZkOiJS0

[Gergely Orosz @GergelyOrosz]

Automattic did so much good for the open source community for ~20 years.

And yet, claiming it is defending open source ethics (of giving back) it committed blatant theft: stealing 13 years’ work and userbase of another team.

Absolutely unethical.

I no longer trust Automattic.

[DHH @dhh]

This is totally crazy. Like if the operators of rubygems dot org just decided to expropriate the official Rails gems, hand over control to a new team, and lock the core team out of it. We're in uncharted and dangerous territory for open source now. What a sad sight.

[Aaron Patterson @tenderlove]

Honestly, me since 2008 (I think?? 😅). I love Ruby and I love Rails. Nothing else makes me feel like I love doing web dev

[Lucian Ghinda @lucianghinda]

Please RT 👇 so more people find out about these Ruby and Ruby on Rails directories and submit their company website to be listed there.

Let's grow these directories together!

https://t.co/IC6MpGIZfG

[Aron Rotteveel @ArondeParon]

I'm hiring!

Looking for product-minded engineers who value shipping value over technical wankery, love @laravelphp as much as we do and are keen to work with a fully remote team across the globe.

👉 https://t.co/Ngdr8V545R

[Jason Fried @jasonfried]

The problem with software estimates is that they're both entirely right and entirely wrong.

Yes there's a 3 week version of something. And a 6 week version. And a 4 month version. And a 12 month version. That's correct.

Yet, you'll almost always be wrong whichever you pick. Because estimates aren't walls — they're windows. Too easy to open and climb through to the next one.

The 3 week version will turn into the 6 week version will turn into the 12 week version. You can see right through.

Software that encourages you to estimate how long something will take makes it even worse. That software is part of there problem. You know which products I'm talking about.

So what to do instead?

Set an appetite.

A appetite is like a budget. Not "we think it'll take 4 weeks" but "we're only giving it 4 weeks." That's all we've got side aside for it. Then the team tasked with the work has to get creative and figure out the 4 week version of that feature. There is no 6, 8, 10, or 12 week version when the appetite is 4 weeks. Just like there's no $7,000 vacation when you only can afford a $2500 one. And you know how that ends up if you overspend.

Are there times when you need to give something another week? Maybe even two? Yes. There's some margin for that because it can only happen once per project, and it's commensurate with the time spent. You don't double the time, maybe you give it 10% more time if you need to. A little margin for error and reality is built in there. This isn't absolutist, this isn't fundamentalism.

And yes, there are times when things aren't completed within the time allotted, and there's no obvious, honest path to finishing it with a touch more time. In those cases the project dies, we internalize, and hope that doesn't happen again. It rarely does here at 37signals, but it has. It's part of the cost of doing things this way. The payoff is huge, the downside is limited — that's a tradeoff we can live with.

[DHH @dhh]

I think there's room for many different paths in the framework world, but also that it's healthy to draw contrasts: There will never be a Rails Inc. We will not raise venture capital. We will not pursue our own cloud. Just great open source work, available for free, forever.

[Hetzner @Hetzner_Online]

Well, @DHH made a good point at #RailsWorld in Toronto!
$250/month for only 2 threads - seriously? Ain't nobody got time for expensive servers when you can get better options for way cheaper. It's time to stop overpaying, everyone! 💰
➡️https://t.co/vocUD3RHa9