Welcome to my blog: Purpose and Technical Details

Introduction

Welcome! I’m a creative native iOS developer who loves exploring a variety of technologies.

It makes sense to mention, considering the name of this blog, that I was diagnosed with ADHD early on.

What once felt like a curse turned out to be a blessing and I want to talk about it : managing your dopamine isn’t just important for people with ADHD — it’s a key to focus, success, and happiness for everyone.

I'll also mention that I am addicted to sports (my favorites are Brazilian Jiu Jitsu and calisthenics) and I am always looking for ways to improve my performances.

Why This Blog?

Over the years, I’ve worn many hats: engineer, tinkerer, and sometimes guinea pig. Along the way, I’ve picked up all sorts of insights. This blog is where I collect and share those discoveries. In short, I'll :

• Centralize Knowledge

• Encourage Experimentation

• Relay crusty findings

• Document My Journey

• Share random shit

Technical Stack

Since I’m primarily an iOS developer, I didn’t set out to become a full‐stack web guru. But I do want a solid, maintainable blog — one that’s easy to update, looks clean/minimalist, and scales without much overhead. Here’s what I chose:

• Fork of the talented Leo's blog : leohuynh.dev

  • Itself is a fork of the popular timlrx/tailwind-nextjs-starter-blog.
  • Gives me an excellent foundation without reinventing the wheel.
  • Didn't want a massive wordpress nor a blackbox! I like the simplicity of markdown for posts along with the possibility to inject react components.

• React & Next.js

  • Server‐side rendering for fast initial loads.
  • File‐based routing makes adding a new post as simple as dropping a Markdown file in the /data/blog folder.

• Contentlayer

  • Transforms Markdown frontmatter into typed data automatically.
  • I get TypeScript inference for my post metadata, which cuts down on typo‐surfacing errors.

• Tailwind CSS

  • Utility‐first styling that’s easy to extend.
  • Consistent design tokens without wrestling with a massive custom CSS file.

• Vercel

  • Instant deployments on every Git push.
  • Zero‐configuration SSL, caching, and edge functions out of the box.

• Spline

  • I used spline to create the 3d Keyboard.

Each new post lives under /data/posts as a .mdx file. Because of Contentlayer, I get full type safety on frontmatter fields like title, date, tags, and summary.

What to Expect

Over the coming weeks and months, you can expect posts on topics such as:

• SwiftUI stuffs: Mainly architecture related and/or open source projets
• AI stuffs: iOS or mac apps plugged to AI apis
• Node/Bun stuffs: Showcases of what I consider clean architecture
• Infrastructure stuffs: Examples of IaC on AWS with pulumi
• Dopamine Hacks & Productivity: Brief experiments I run — dry fasting, animal based diet, sports etc..
• Random shit: Past travels or my portfolio from a past life as a model. That kind of shit.

I’ll aim for practical code examples whenever possible. If a dopamine hack comes through, I’ll log my subjective mood before and after, plus any biometric data.

How to Follow Along

• RSS Feed: /feed.xml (auto‐generated)
• GitHub Repo: I’ll push every change to a public repository so you can track the exact commits—especially useful if you want to clone the site.
• GitHub Discussions / Issues: If you spot a typo, want to suggest a topic, or have a variant of a hack that worked for you, open an issue or discussion on the repo.

Conclusion

Whether you’re here for software development stuffs or dopamine management experiments, I hope you find something that sparks your curiosity. I’ve learned that the act of writing about a hack or workflow often uncovers gaps in my own understanding—so thank you for being here, helping me learn, too.

Happy coding, experimenting, and optimizing 🚀

PS:

A portion of my posts will often be generated by AI (including this one). I usually start by throwing down the key points of what I want to say.

The AI then takes those notes and builds the initial structure. Once that draft is ready, I go through it, tweak any phrasing, correct details, and make sure it sounds like me before I commit/push (because, let's be honest, chatGPT likes to fuck flies)!