Day 6 of #100DaysOfCode
Ran a few scanners on metadata and JSON-LD: found weird errors that several passes on GPT/Gemini didn't pick up. The usual "oh, I missed that" excuse from them. ๐
Deep dives on proper (the current best guess!) GEO article construction.
#buildinpublic
Day 5 of #100DaysOfCode - zero new features shipped!
Instead, chased down some people who dropped off, updated some gnarly bits on the website and completed a few pending directory submissions.
Building Kanso in public -> https://t.co/HHgyYwT2LM
#buildinpublic#indiedevs
Wow, super interesting talk by Ted Barker at BOS2026 @bosconference.
The gold currently spread across random google docs, bookmarks, emails and platforms is just so hard to surface when you really need it.
https://t.co/osm9Q4ZZ0U
@chams_builds Google AI studio definitely does not make it easy! I think they changed how billing worked sometime in May and I didn't get the info or didn't read it :(
Day 4 of #100DaysOfCode
When a bug in production stops the app working, you stop what you're doing and fix it ๐ ๐ฅ
Today, I didn't have an alert that the credit had run out for a pay-as-you-go service, and no auto reload either ๐คฆ
Lesson learnt.
#buildinpublic#saas
Day 3 of #100DaysOfCode
Oh my, directory submission day (again). I know there are automated tools out there, but are they actually any good? How many directories is actually enough? 5? 10?
Maybe I should shell out for one of those auto-submit tools ๐
#buildinpublic#saas#seo
@vadym_petryshyn So real. Every suggestion from AI looks like it was taken back in 2005, so getting creative is the only option.
Oh well, domain name with a .com doesn't seem to be as important as it once was...
Day 2 of #100DaysOfCode
About 2 weeks pre-launch, I changed my app name to something a little more distinct, which also meant a new domain.
Post launch, I spent today working through product directories and learning more than I needed to about GEO & JSON-LD ๐
#buildinpublic
Day 1 of #100DaysOfCode.
Quiet day because of #WAOpen squash sporting commitments ๐พ
โ๏ธ reviewed marketting plan
โ๏ธ added an SEO article
โ๏ธ thinking about which paid feature to work on - personal features for $5 - $10, or a team feature for ~$50 per team.
#buildinpublic
Standard career quizzes tell you what you love. I'm building a tool that maps what you're willing to sacrifice.
Restarting #100DaysOfCode to move from first signups to full team & role features.
Rank your trade-offs: https://t.co/HfOYcNgmNe
#buildinpublic#FutureOfWork
Most career tools tell you who you are. That's not the hard part.
The hard part is knowing what you'd actually trade.
Kanso is live on Product Hunt today - free, 5 minutes.
https://t.co/cjwh728Ozw
#ProductHunt
Website construction with something like @astrodotbuild is so much more productive than my previous static site solution (WP + Local + Static Site).
Astro feels clean and modern, and WP just felt ... archaic .
#buildinpublic
Day 56 of #100DaysOfCode Refactored all of my existing game, game state, agent, model and training code into classes. The code is now (semi) readable! ๐
Thank you to the many #TensorFlow tutorials online that show how to do reinforcement learning!
#Python#MAME
D48 of #100DaysOfCode Finishing off the state machine for the PacMan shell. Can now control it using a #Python app I wrote that tells #MAME to insert coins, start the game and move PacMan. It records the score, works out when a game has ended and can restart the whole process
D46 of #100DaysOfCode was about sampling the state of the PacMan board. First up, using OpenCV to get the image one digit at a time, hash the image, compare against known hashes to give me a number from 0-9, and then build up the final number from the parts. Scoring done! #python