Gregory Brown [MOVED, SEE BIO]

@skillstopractice.com

No longer here. Find me on Mastodon instead: https://mastodon.social/@skillstopractice Or if you don't use Mastodon, you can follow my bridged account here on Bluesky: @skillstopractice.mastodon.social.ap.brid.gy

G

Finished that convo - here's what would restore trust. 1) Public disclosure of the rumored January 2025 funding round that had a $700 million valuation. 2) A public business plan. 3) Something rolled out that makes money. 4) Legally+financially sound steps that shield protocol development.

GGregory Brown [MOVED, SEE BIO]@skillstopractice.com · last yr.

Open letter to @why.bsky.team regarding Bluesky revenue model risks + potential mitigations. We've discussed some of this over DM and will continue to be available so, and the notes within it reflect my own take on things only but hopefully clarify. notes.skillstopractice.com/updates/2025...

G

To be very clear... ad revenue is only one way to make money. Nearly any other option I'd welcome with open arms because you can't run a principled business without being financially sustainable. It's startup smoke and mirrors to pivot to "oh you hate revenue bro, that's dumb" So I'm out.

GGregory Brown [MOVED, SEE BIO]@skillstopractice.com · last yr.

I'm leaving Bluesky effective immediately and this is the reason why. I'll post when I get Mastodon set up + an RSS feed + newsletter.

G

Counterpoint to this... I would happily pay $50/month for an atproto-based Bluesky clone that promises "no ads, ever" as long as it was interoperable. So anyone who is building that, just know that you've got at least some customers waiting, especially if you refuse to take VC money.

GGregory Brown [MOVED, SEE BIO]@skillstopractice.com · last yr.

I won't mince words, the day Bluesky rolls out ads is the day that I make this place syndication only and stop hanging out here, and then plot an exit entirely from the platform within 6 months after that. It'd be a broken promise, in *any* form. bsky.app/profile/zipp...

G

Frictionless learning is not a thing. If you're doing something that feels like learning but you're constantly in a flow state and progressing w. ease, you're not learning, you're being trained via someone else's designed system. This is not always a bad thing. But it pays to know the difference.

G

v0.6.0 of "Bug Hunt: Volume 1" is now live, with two new exercises... One is themed on Conway's Game of Life and shows something to watch out for when using Ruby's pattern matching feature. The other is a common "gotcha" when using Ruby hashes, especially if you mostly work in Rails. (1 of 2)

G

We need a new equivalent of UNIX, not at the systems level but at the application building level. (Meaning, a super interoperable fundamental building block that allows for infinite specialization but doesn't require infinite piecemealed integrations)

i'm on Bluesky for the echo chamber of Good Job With Your Project, and I'm Doing This Thing Now That I Enjoy, and You Got This, and Help Me Out With This Problem I'm Having, and Isn't This Thing Pretty Cool, and Check Out This Thing I Made

The main reason why I never offload cognitive thinking to LLMs is that frictiontless output is a pernicious trap. Seems smart, but long term it's you who becomes replaceable. If the use case is to speed up useless work, it's a sign to change your life, not how you produce something to the society.

had a thought about why people outside the tech world (artists, journalists, etc) are quicker to perceive gen AI output as bullshit even though they are generally less deeply familiar with how they work: in most domains, generative models are only trained on the _output_

G

Been slowly and steadily keeping the #distilled.rb feed (and mirrored account w. same content) updated. Will start experimenting with finding stuff outside of Bluesky as well and bringing it here to be more easily found. Would appreciate a repost of the quoted post below to help w. discovery.

Ruby + Rails : Distilled@distilled.skillstopractice.com · last yr.

If you've got a blog where you (at least sometimes) write Ruby-related posts, please reply with a link to your RSS feed below. I am going to try to start keeping an eye on those as well and sharing interesting stuff I find from time to time.

Two fundamental skills in managing complexity: * Partitioning. If I arrange things *thus*, then I can deal with *this* while not dealing with *that*. * Oopsie. Arranging things *thus* actually makes things harder because I have to deal with *this*, *that*, and the partitioning all at once.

Powerful emotions from this post. "...more people are going to be forced to rely on a deposit of knowledge from prior to 2019 — one that can be remixed and perhaps commented on, but not really expanded, because the skills and resources that it takes to expand it have somehow withered away."

Gerry Canavan@gerrycanavan.bsky.social · last yr.

"Mass literacy is a kind of infrastructure, and like all forms of infrastructure in our neoliberal and now potentially post-neoliberal world, it has been allowed to crumble." itself.blog/2025/01/02/n...