Creating My Own Public Software Engineering Journal
Context or Problem
I use Obsidian for note-taking and like it. However, the lack of a premium subscription makes accessing my notes from other devices annoying. I’m considering switching to Git-based Markdown, which would keep my notes in my GitHub repo, and then building a website to view them.
Experiment
I’ve tried out a bunch of static site generators—Next.js, Hugo, Jekyll, Eleventy, and more. But Astro feels like the best fit. I can write Markdown like usual, style it with modern HTML and Tailwind CSS, and not worry about a ton of dependencies or configuration. Just write what I want, then add components later.
Outcome
In the past, I often pursued perfection and idealism, which ultimately led to inaction, laziness, and procrastination. A ‘pragmatic approach’, as described in a book I read, has helped me overcome this. I now embrace a ‘do things for the goal, refactor later’ mentality. Now I should be able to focus on building things while documenting it on here anytime.
Possible Next Step
Consider implementing a responsive design for better viewing on mobile devices. Review the layout and make adjustments to ensure content is accessible and user-friendly across various screen sizes.