has reached the end-of-life and is now read-only. Please see the EOL announcement for details

Ok, tonight I'm going to do a dev stream FOR REAL tonight at 8 pm Mountain Standard Time (2 hours from now)! Gonna get to work on making status updates and progress work!

I'll post a link to the stream(s) closer to when I'm starting, so stay tuned!

Alright, I'm planning to start live streaming some dev work in about 40 minutes at roughly 7:20pm Mountain Standard Time (that's the time zone in Denver, Colorado). That should give me just enough time to set up OBS and everything on my new computer...

I'll post a link when I go live, but it'll be on this PeerTube channel:

I'm thinking of doing a dev live stream later today. It's gonna be extremely boring and probably consist of only dependency updates, but maybe I'll actually get some UI stuff done too, who knows!

I'll probably be streaming on, and I'll update again if I end up actually doing it!

Hey so I JUST got an email about new progress tracking features in The (, and it's finally pretty much exactly what I've been looking for in a !

I'm still going to be developing because the name is way better and I have some good ideas for it (and it's FLOSS), but you should definitely try out The StoryGraph in the meantime because it's pretty excellent so far!

Me, the developer of :
Ugh, god, when the hell is Readlebee going to be ready? I want to use it so badly!

Ah, I think I finally understand Server-Side Rendering for JS frameworks, so I suppose I ought to do that for so it doesn't just load a blank page if someone has JavaScript turned off on their browser.

It's been about 1 year since I started working on @Readlebee, so I wrote a blog post about my experience so far:

TL;DR: the development process is very different than what I'm used to because I'm trying to do it "right," and that slow process has been discouraging, but I'm hopeful that I'll get something to show for my work relatively soon.

I tend to pre-write a bunch of code without testing it each step of the way. Most of the time it works just fine and how I want, but with some of the stuff I wrote for earlier, it did not lol

Thank goodness I'm also good at debugging my stuff! 😅

I'm excited to get back to working on so I can share book reviews more easily here... Unfortunately, I'm going to have to finish the actual app before I add support because I'm still a little hazy on getting the protocol completely working.

Now that I'm finally just focusing on getting to a presentable state instead of worrying about late-stage problems, I'm actually making headway again! I'm about halfway through shelf management!

Ok so I need to just build the fucking app just like every other app I make and worry about federation and all this extra shit I've been worrying about. I'm going to stop worrying about what's "best" and just finally *DO IT* and then clean it up later because I'm tired of having this burden of not having anything presentable because I'm frozen in fear of doing something wrong.

It's time to get stuff done and tidy it up later.

Self doubt fueled by lack of sleep 

Ugh what's wrong with me. I keep going back and forth on dev concepts—should I build the front and back end together to make it easier to understand how they interact, or should I build out the back end and API completely and build the front end with what's available in mind? Should I use Swagger to make sure the API is easily readable /first/ or should I just document the API when it's done?

I'm so tired of not knowing the "best" way to do things.

I'm realizing just /how much/ help I'm going to need on the project... this is a very large task, and I'm really going to need help implementing features beyond the barebones functionality of book tracking, comments, and reviews. The concept of federations is overwhelming me at this moment, so I'm really hoping that some people will be able to come to my aid when the time comes.

I'm primarily a front end developer, and all this back end stuff is torture!

I just spent all of tonight and most of this morning contributing to and improving the `sequelize-erd` project specifically so I could visualize the database structure I've set up for so far:

In the end, it was very worth it because it showed not just the /structure/, but also how Sequelize /interprets/ what I set up, so I was able to fix a bunch of errors because of it! 🥳

I started actually reading through the Sequelize docs so I could learn how it actually worked, and it turns out that knowing how to use things is helpful for using them!

Moving forward with should be much nicer now that I actually know how to query the data correctly...

Ok, my current idea for data structure is to split the unified "Status" table into two double-duty tables that store Ratings+Reviews and Updates+Progress. That way it'll be a little bit easier to manage than just trying to split from one table.

I still need to figure out what to do about books, though... I want to be able to target specific editions for reviews, but I don't want a ton of repetition in the database... using editions from Inventaire could work, but it's...

Show thread

Gah, I'm hitting a huge snag with shelf items because I haven't fully worked out book references yet. I may need to refactor the database again—I think I need more tables and a better way to think about the data structure... I was hoping I could keep the database relatively small/clever, but I'm seeing now that it won't really be possible with such a large project...

I have a headache from trying to figure it out right now... time for a break so I can process and mull over options.

Show thread

Well, my wife is going out tonight, which means it's dev time! I probably won't stream it this time, but I should hopefully be able to finish shelves, shelf items, and maybe even get started on book references!

I'm excited to see how much I can get done!

Should I write 's front end in instead of what I'm currently using for professional skill-building purposes and maybe a greater range of developer familiarity, or should I keep using the tiny framework I'm currently using that I love called that's easy to learn and understand anyway and that everyone ought to be using instead.

Show older

‼️🔛‼️'s choices:


the mastodon instance at is retired

see the end-of-life plan for details: