Wanted a loosely structured workout tracker for a while so started building it. Don’t want recos or gamified whatever just good interaction patterns simple tracking and data vis over time. Worked on backend implementation today and will work from there. Excited to get using it

It all matters and none of it does so just try -Alyssa L.

Did some more refinement on the logbook color system getting rid of the final beige tones and making sure we landed on a monochrome set for both light and dark mode. Added the ability to hide and revela filters on mobile to match the web experience. Worked in a reversed reveal animation for the mobile filter section moving top down and left right as opposed to web's bottom up reveal. Added a type in population animation to the top section blurb. On to the type system next.

After getting telegram post pipeline up and running did a visual pass today. Swapped the original beige color palette claude generated for a monochrome setup for both light and dark mode. Added an ASCII character gradient with a film style sizzle animation on some of the characters. This still needs some work, lot of passes to get it looking decent. Added an animation to the filter open and close and consolidated the categories present as well.

Webhook test

Render test

/start

Got the telegram to site publishing pipeline up setting up the required webhook and infrastructure in Vercel and telegram. I message a custom bot with the correct syntax and it posts it here. Telegram → server → repo → Vercel. After testing realized I needed to clean up ordering on same day posts with a slug tie breaker (learned what a slug was). Also added an optinal title feature that seperates a first line with a space under it as a title when creating the .md post file, and added vercel analytics.

Got the idea to create a telegram post pipeline from @danywander on X. Created the plumbing for the system today adding and api/fee.json enpoint to pull in new entries and then on Claude's suggestion split the render path into client server boundaries so every reload was less demanding. Will get the actual conection set up soon.

Created a progressive scoring system with degradation of the "cook-o-meter" anytime there are no hits and with and increase when there are hits. The curtain animation was sluggish and choppy and I found it was re-rendering the image over and over to compensate the skew so I removed that effect. Added Chicken survivors at the end of the game. Testers (the fam) are already reporting increased high scores.

Decided to try and make a game and work with some 3D using claude code. Created a whack a mole style game using low res 3D models and introduced some bop effects and timing dynamics. The game records score and terminates at 30 seconds.

Updated portfolio today. Added images and some video to the tablet control case study. Finalized the language for the "results" section. Decided to remove the image banner from behind the initial hero section interface screenshot, it doesn't add anything to the work.

Rendered a bunch of video at work today for the upcoming install. Shared it in 8k and needed it in 4k. Bless Claude and ffmpeg. Interesting new retail chat project proposed.

Removed Bento from my portfolio as it's dated work and can be added as one off visual assets but may distract from more recent case studies. Took the card off the home page and updated the tablet control case card to be full width. Change the cards fully this week because they don't communicate anything about the projects outside of visual and video and the layout feels out of proportion/unorganized.

Jumped back in to using github to push this site as well as another project I worked on today. Both are deployed on vercel now. Didn't make any visual changes here but did create a shader controller with a few manipulable variables to adjust the appearance of the effect. Ended up pretty cool, looks a little bit like a gas giant randomizer. Claude code is wild.

Completed lists module in the boot.dev "Learn to Code in Python" course.

Decided to create this logbook to document the path of learning to build in code. Watched some videos, upgraded my claude plan, and got started. V1 is below with dummy content, intend to update the styling and organization over time. Step 1 was making the jump to get something built in code.

Completed loops module in the boot.dev "Learn to Code in Python" course.