Tessera
Folgen

Josh Brown

@joshantbrown.com

Product Engineer. Ruby / Hotwire. Aspiring polymath; designer, developer, writer, maker, creator, gamer and aviator. Occasionally stream on Twitch and YouTube.

77 Posts586 Follower346 Folgt
Josh Brown@joshantbrown.com · 2y ago

Occasionally I find myself reflecting on the Principles behind the Agile Manifesto - and it always surprises me just how much they've formed a foundational basis for my own product/software development philosophies that continue to provide value. Here's a couple that I find particularly of note: 🧵

Josh Brown@joshantbrown.com · 2y ago

Status enums are a slippery slope At some point you’ll want to know when something reached a certain status, or you’ll have some combination of statuses that have some special meaning, and it spawns complexity Nullable dates work much better. If you must have a status, consider a status model

Joel Drapper 🇬🇧🇺🇦@joel.drapper.me · 2y ago

Status enums like this in Rails apps are almost always a mistake. This would be much better modelled as nullable dates — created_at, started_at, completed_at, delivered_at, paid_at, cancelled_at. You can then use scopes to select where null or where not null.

Josh Brown@joshantbrown.com · 2y ago

Been having fun with #AdventOfCode so far. Thought I'd share some of my solutions, so here's day 4: I've been trying to incorporate and learn about some lesser used Ruby methods, today's was repeated_permutation to generate all the different directions the search should move in.

BildBild
Josh Brown@joshantbrown.com · 2y ago

Tailscale really is a joy to use. The airfield I help operate runs some software that uploads weather data to our website, but it’s old and only supports insecure FTP for uploads. No issue – just run an FTP server in Docker and bind it to a private ip through Tailscale.

Josh Brown@joshantbrown.com · 2y ago

Here’s how I write commit messages (even if no one else will see them): Use imperative mood. Use sentence case. Explain purpose of change. Use body if more complex change. Start with an emoji: gitmoji.dev. Anyone unfamiliar with the code (likely my future self) can use them to understand it.

gitmoji

An emoji guide for your commit messages.

gitmoji.dev

schwad@schwad.org · 2y ago

what are your commit messages like on apps where you're the only one who will see them

Josh Brown@joshantbrown.com · 2y ago

I was amazed the other day at how easy it is to connect to the “firehose” of Bluesky and just see every interaction in real-time. With just one gem, and several lines of code. 🤯 github.com/mackuba/skyf...

GitHub - mackuba/skyfall: A Ruby gem for streaming data from the Bluesky/AtProto firehose

A Ruby gem for streaming data from the Bluesky/AtProto firehose - mackuba/skyfall

github.com

Andy Bell@bell.bz · 2y ago

It costs $42k a month to hack around on the Twitter API It costs $0 a month to hack around on the bluesky API Bluesky is also open source so you can hack around with actual bluesky if you want too

Josh Brown@joshantbrown.com · 2y ago

It would be nice if when you joined a starter pack on here it had the option of requesting to join it. I imagine it’s a bit of a chore to keep on top of right now. Maybe could evolve into some community grouping feature of sorts. Especially when combined with feeds.

Josh Brown@joshantbrown.com · 2y ago

I really like the data portability aspect of At Protocol. Excited to see how it develops. One major thing I think is potentially missing right now is access control. How can I restrict which apps and/or users can see my data?

dan@danabra.mov · 2y ago

i wonder if diagrams like these might help draw the distinction between ActivityPub (and how Mastodon uses it) and AT Protocol (and how it’s used by Bluesky and atproto apps)? with AP, instance = application + hosting. data gets sent between instances. with AT, data flows *from* hosting *to* apps

diagram with multiple application+hosting boxes. each box contains some users and some posts. data is sent between the boxes.