Pats Ecke Sparks
-
I wanted to see what using AI to code is like in its current state, so I bought a Claude Code Pro subscription.
While the code is definitely not clean or organized in a best practice way, I was able to get a working app running in a few days, something that would have taken me much at least few weeks.
The app will be used for our wedding to allow our guests to upload pictures and videos, as well as download them later.
Plenty of apps exist for this, but they usually have limitations or require a pretty penny to be spent (because weddings…).
Now my wife and I have our own privte app that (should) work great for the big day. Super stoked!
The AI usage is a skill in itself, so I’d recommend everyone getting some experience with prompting, using the built in context support, and generally getting a feel of AI’s capability and limitations when it comes to coding.
There’s no better way to demystify AI than to use it in a project.
-
I decided to keep the layout of Sparks for now using the normal collection process that my blogs and projects use, with the small edits to the schema, since it only needs a publish date and the markdown.
I think the SSG power of Astro negates the issue (at least for now) with a large number of content markdown files. I’ll organize my sparks by month in a folder, and this allows for the flexibility to keep my Sparks separate without having to hard-type dates.
Next feature will be figuring out infinite scrolling to replace the pagination for my Sparks page. Pagination makes a lot of sense for blog posts and even projects, but for Sparks, the infinite scrolling would be much better.
-
For me, I have to re-learn how the JavaScript engine and runtimes work. Here’s what I used to refresh the memory this morning.
Also, my next few tweaks to the Sparks feature of my website is going to be how I add Sparks. Right now its another Spark file (markdown), just like my blog posts and project posts. However, I think (at least for now, without an integrated CMS),
I’m going to rewrite a few things so that I can just add Sparks to the same markdown file, maybe organized by month, and the date of each Spark will just be read from that file.
Let’s see how that goes.
-
One commit a day, that’s the goal. Betwen yesterday and today, I implemented my Sparks feature on the website. Super fun actually.
Next goal is to handle a long list of sparks differently than my blog or projects, maybe an easy scrolling function instead of pagination.
-
First spark! Sparks are basically short thoughts that I want to share. So yes, it’s basically my version of tweets.