I've started breaking up my API types this way on the frontend. It's been an okay way to model optional Eloquent relationships.

It helps enforce that child components only get objects with required relations (like a campaign with characters). I do miss shared types across front+back though.

I've been working on Dungeon Docket, a lightweight inventory management app for my dungeons & dragons players. Ultimately I don't know what will come of it, but it's been a good excuse to keep learning and keep building. Maybe I can launch it with a copy of the free SRD items.

This was a great read! I really found the bit about "2 hours a day, every work day" particularly interesting. Do you have any tips on how you break down a new feature into 2 hour work sessions? Do you use any project management tools to manage your backlog?

This is impressive growth, nice work!

You gotta stay strong a wait for the OLED version! The OLED switch looks incredible, but hard to justify the upgrade.

Congrats on the launch!

If you’re planning on integrating with home assistant, ESPHome makes it super easy to integrate the esp32 platform. Just write a few lines of yaml and flash the microcontroller

Welcome home! 😎

Neat! I’ve always wondered how it would do for development work, excited to see what you do with it!

We leverage the AT Protocol to store your page, meaning your data actually lives right on your bluesky profile. Here's mine: atproto-browser.vercel.app/at/did:plc:j...

Read more about how Woosh works at federation.studio/blog/introdu...