The Cost of Blogging →

Reading this post from Online Goddess, and obviously got me thinking, with all the time and effort for building and using this blog as my medium for documenting my journey about something, tech, project, life, or other thing.

Sometimes sharing things that interest me, and might be useful for other people.

The actual thing that cost me money, currently, only the domain, I have bunch of it. I bought this domain for sometimes, some of this blog post has survived few provider, and ended up using Jekyll as my engine, it’s simple, works with my workflow, GitHub -> Netlify and that’s it.

Other post might have other view the cost of being online, here and here.

Even though I and not counting those cost, but the mental model, cognitive load, and cognitive exercise are huge benefit for me, in this AI era. Yes, sometimes I missed the struggle of thinking, hit the wall, or can’t find the exact word for things I’m thinking of. Now, just throw it to AI, and it will figure it out, one way or another, true answer, sloppy or hallucinating.

I do like writing (and reading), even though sometimes falls into “summarize this book for me” trap, with reading without asking AI, we can see inside the brain of the author.

The loast art of looking →

You don’t impose yourself on the thing, because you simply can’t. You don’t have the skill. Even the best artists in the entire world know that they cannot render reality. So you just let yourself be curious about it. And you’d be amazed by what’s out there when you really look.

Speed Traps

Speed Traps

Yes, I do mentioned about using AI as part my current journey as I found or rather rediscovering SWE passion, AI could do so much as my brain could understand and design some system or service that I wanted to build, using AI code assistant of course.

And by using AI Code Assistant, I have quite enormous code output, I say enormous was compared with my previous life obviously, you can see the commit and push in my Github repo.

One push can have multiple files.

This invites speed traps, I felt it, I can see that this not “normal”, how can I track all changes underneath, the changes done by my AI agent, it’s too fast, too soon, afraid but happy at the same time.

I can set some guardrails, rules, souls, or any kind of approach that industry currently use, and deeply I still have doubt about how can I trust everything the AI tell me or write me to, the codes, the decisions.

Yes, I do keep my skepticism, a healthy one, I need to keep the output in check, how it honor my BDD, PRD and task that I delegate to AI. But the traps still there, it always there, so be careful, don’t too dependent and blindly trust anything from AI, they can spit out anything believable for their users.

A Place For My Head

A Place For My Head

This is not an album name, this blog, it really is a place for my head, place to write, away from AI, writing for writing sake, keep the editor simple, i’d like keep learning to articulate my brain, thoughts, and how to make it into words.

A code, machine can understand, interprete it, compiled it. and words, even though AI can “understand” it, but it will lack of empathy, and will not be like really-really understands it.

So here it is, writing bunch of “nonsense”, flaws, no need to be perfect writings, there is no such thing.


Tag: #life

Rediscovering Software Engineering passion

Like many of us who stumbled and “played” with AI, with many LLM providers around, it is hard to miss — almost everything is at your fingertips. AI already has its place with many users: ChatGPT, Copilot, Claude, anything on the market. Some know what they’re doing, some don’t.

At first I was aimlessly using AI — generating funny images, manipulating images with prompts, and other things like refining article posts or Confluence entries.

After a while I noticed that the models are good at helping me with my struggle in building software — software that I can actually use.

I’ve known the term “vibe coding” for some time. I thought it was silly, but after getting to know it, understanding the workflow, and knowing how to build a product, it’s not that bad. I used to build stuff on my own, develop it from the ground up. Preparing a project was cumbersome — decisions on what technology to use, whether it will last long-term, that kind of cognitive load. I know how to build software, I know a thing or two about building a good product, but that cognitive load, the context switching that can hurt you, and all the tasks that need managerial skills rather than code itself, made me “avoid” building software.

Since I know how to think like a system — or rather, practice Systems Thinking — this engineer’s brain can’t help it when I see what AI can do, how it can help me build stuff that I might use or not use. Build software that’s specific to my company, or just for fun. I can do that right now, with the help of AI or agents I deploy to build stuff.

That preparation — decision-making for the tech stack, the language, the database, frontend, backend, everything — I can delegate those decisions to an AI code assistant. They can help me out, even with a language I’m not familiar with, like TypeScript for instance.

I can focus on defining and refining what product I need to build, create the spec in a document, let the AI read it, and prepare what I need within the spec. Let the AI write the PRD, build based on that, refine, build, refine, repeat.

With my current responsibilities — managing people more than code — and with the little time I have, it’s such a breath of fresh air. I’ve suddenly rediscovered my passion for software engineering — through AI.