Waiting 55,000 years for your sprint to start

How It Started

Just have to wait 55,000+ years for the sprint

How It’s Going

That’s a bit a better

🤖🤖🤖

What’s New with Writi

Writi can now successfully run sprints! We have the entire sprint flow from creation to results. The messages themselves need work obviously and I need to add some Writi flare to them, but the bare minimum functionality is there! You can create a sprint, join it, sign out, and get sprint results.

New commands:

/write for - Create a sprint
- options
  - [MIN] -Sprint for MIN minutes, starting in 1 minute
  - [MIN] at [XX] - Sprint for MIN minutes, starting at :XX on the clock within the next hour
  - [MIN1] in [MIN2] - Sprint for MIN1 minutes, starting in MIN2 minutes (MIN2 can be 0 if you want to start immediately)
/in - Join the sprint
- options
  - wordcount - Starting wordcount, optional
/out - Sign out of the sprint
- options
  - wordcount - Ending wordcount, optional

Some behind-the-scenes stuff I also worked on was making sure the bot would be able to continue running sprints even if it restarted, as before that, if the bot went down, it lost all currently running sprints. I also added some better error-handling so that I would be able to communicate to the user any issues in a more user-friendly way. Still more work to be done there, though!

Now that Writi can run sprints, though, I want to get testers involved and invited to my Write Time App Discord server, so if you’re interested, keep an eye out for the tester call coming soon 👀.

🍄‍🟫🍄‍🟫🍄‍🟫

Developer’s Log

I shared that first screenshot around to my friends and accountability group immediately after. It was just so funny being so mind-boggling far into the future, but it was just a bit of a mismatch between seconds and milliseconds when doing the dynamic timestamp in Discord. The sprint time was still correct in the database and the bot would run it at the correct time. I was at first relying on someone else’s npm package to do the conversion for me (the Date object to Discord dynamic timestamp), but it clearly wasn’t working, so I had to scratch that and add it to my code directly.

We have a bit more progress from last time, but most of it was done in the last week, after I got a handful of rejections added to the job app pile after going through mid and final rounds for some companies. There was a lot of anxiety before I got the last email I was already expecting for a few days, but I turned that disappointment into spite into code. I have some other stuff in the pipeline but hoping I can continue this momentum on Writi. I’d love to finally get the actual website up and running even though it won’t have much yet.

I’m glad to share some more concrete updates this time. Happy writing!

🌱 angela

🌿🌿🌿