It’s good that there’s finally some output, because there has been weeks where the lack of progress has been quite frustrating.

However, when I look back at the last 1+ month, I realized there is a lot of hidden work that went into discovering a structure for how to develop HaS. And it was not what I had in my when I first started.

A lot of the process’s peculiar details came from my own constraints:

• Mostly solo development, with no prior background in actual gamedev.

• Running this on the side of my full-time work + family duties.

• HaS being what it is: a narrative driven game that strive for directed, but also procedural stories.

What I discovered was that: for a particular game & team setup, a good process can really reduce the friction and overhead.

In this case, I stumbled-upon production pipeline was:

→ Write the stories for HaS in blog post form

→ break them apart to create an Interactive Fiction prototype (Twine)

→ imagine what art/music to add

→ translate to engine/code requirements.

This accomplished a few things:

Fleshed out the characters

Now, the characters feels pretty strong. From major ones like PICO and Elodin to the support casts like Eleanor, Martin, Shiori, Diego, etc feels fleshed out. This happened as a consequence to writing and thinking about what they would say or do.

And instead of creating them from a top-down troupes, stitch them back from separate writing pieces allowed them to be nuanced, full of different beliefs and contradictions - the very value that HaS aims to portrait.

On the mechanical side, it also led to the creation of a “framework” for each character: internal thoughts, habits, speech/cognitive pattern, personality types, etc. This keep them coherent across various pieces (a hat tip to Brandon Sanderson’s lecture on building characters).

After some initial investments, HaS’s characters feels like they are alive now. I could then place them into a scene and ask “what would they do/say”, simplifying a lot of the writing process.

Structured the story’s pace

Writing taught me pace-control at various level: the macro of the whole blog post and the micros of paragraphs and sentences. This is emphasized even more as I attempt to turn the writing into the IF prototype.

At many times, it kinda felt like making cut-scenes for the game, the sort that you would see in Stardew Valley when you hit a certain relationship threshold. And if my instinct are right, HaS will be a game with lots of cut-scenes.

Supported the after-hour, solo-dev setup

This turned out to be huge for me. Making HaS required learning about writing, pixel art and (later) music production, besides the usual programming bits. But learning them past a certain level turned out to be seriously hard work, which drained energy quickly.

Thus, a more gradual process that centralized around writing allowed me to make constant progress, which means maintaining momentum and morale. And those are the necessary currency when you are working for passion pay instead of hard cash.

With deliberate practice, it’s also getting easier to slot writing time into the 1-2 hours free time I have every night, without cutting back too much on sleep, family time and other important things.

Set the stage for the visual/audio

I actually didn’t found time to get back into Aseprite or to learn to make music. But because of the writing work, I feel that there are now vivid pictures of what the pixel-art environment and characters should look like.

As for music, it currently comes in the form of a playlist that I kept while writing, as well as a list of artist, composer and style notes whenever something catchy came up. I’m cautiously optimistic that I this will train my music taste somewhat, so I can make some okay tracks later (just not sure about timeline, haha😝).

Kick-started game-design thinking

This mostly happen with the IF prototypes + back-and-forth thoughts. Because HaS’s player interaction is mostly reading, observing and sometimes making decisions, the IF format feels quite appropriate to test them.

Obviously it won’t be enough, but the prototyping helped pinning down better ideas about 2 separate mechanisms: observing characters and story “branching” with the drinks PICO serve.

Sketched the requirements for the game engine

Having explore Bevy more recently, I am of the leaning into the idea that the modular, ECS nature of it will be a good fit for HaS. If each character have a unique system of behavior, it would be feasible to “plug” their systems into the game (we’ll have to see about performance at scale, but I’m hopeful).

Because I work on infra automation at work, I can’t stop comparing this to k8s controller, haha.

Surprisingly here, I found the writing work to be more helpful than the IF prototypes, since the space to describe what a character’s “loop” is more broad.

Obviously, writing alone don’t cut it, so we will have to do a lot more exploration with Bevy in the future. However, being able to see a more concrete shape of the required system is still a great boon.

Built something to show

The last, and somewhat intentional, result of all this work is that I have something to show. Instead of vaguely talking about the game, I can now share blog posts about the story beats to people, showing them what kind of story to expect. This has already earned a few unexpected encouragement (thank you), which really helps with motivation!

After thoughts

All this is to say that I’m somewhat optimistic about the progress so far, even though some weeks things moved at the snail’s pace. The hidden part of the iceberg is being built. And hopefully it will build the foundation to make more things.

While I mostly work on the code by myself, hopefully there will be a point where I can bring in others to help with programming. This means setting up the repository such that others feels easy to start developing.

For games, a challenge here would be packaging the development environments: you would need a compiler + linker (Rust), lots of low-level library for device graphics, input, audio, etc. Things might be different across combinations of OS and CPU architecture, too.

At work, where I only build back end/infra software, we typically put the development dependencies into a Docker image (running Linux)and run that. However, this is not as straight forward for games:

• For once, the performance of a Linux-based container in OSX is terrible.

• I also read that it’s not simple to funnel things like graphics and audio out of a container (haven’t tried it, actually).

=> This call for a different packaging approach.

I have been dabbling with Nix for other stuff, and maybe it is a better match for this problem, because:

• We can declarative define an environment (binary, env variables, file systems, etc) and pin those dependencies.

• We can define variations of the environment for Linux, OSX, as well as different CPU/GPU architectures.

• The environments setup with Nix will be native to the developer’s machine.

It’s a bit of work to create. For example, instead of running lots of apt-get install [pkgs] and rely on assumed system paths, I now have to declare them upfront and set variables like LD_LIBRARY_PATH. Knowing exactly what to do takes a decent of work to figure out. You typically need to dive into Github issues, obscure forums and other Slack/Reddit, etc. Though this is slightly easier nowadays with support from tools like Copilot or Claude, however.

I also found: https://github.com/drxm1/bevy-project-template-nixos-wayland, which helps a lot when I need to reference how to do something.

Hopefully this approach will pay off sometime in the future. At least for now, the real benefit is that it teaches me exactly what is required to build the game. It also helped me understand where Nix, Docker, package managers (Go, Rust), Bazel, etc fits in the big picture of building a program.

• The recent AI disclosure saga involving Steam and Epic’s CEO.

• An RFD about LLM use from Oxide Computer, a company whose engineering culture I really like.

• My own thoughts (and fears) about how people will react to how I use LLMs in certain pre-production phrases of “Have a sip” (yes, this is also that kind of disclosure).

Since I still have a day job as a software engineer in infrastructure, it’s very hard to totally ignore “gen-AI” (or LLMs, specifically). And what’s more, because “Have a sip“ is centered around an intelligent, self-conscious robot and also touches on how AI impacts on ordinary people’s lives, it’s a topic to talk about early.

This is explored in more depth below.

Values of gen-AI usages

I generally consider gen-AI in its current iteration more like a tool. Thus, I think it’s worth looking at its usage like other tools: in terms of the values it brings to the table.

What comes to my mind is very similar to what (I think) Oxide’s leans towards:

• Using gen-AI does not replace human’s responsibility and role in creative endeavors, of which writing, drawing, composing and even writing software are parts of.

• We have to be mindful when using gen-AI, for while its outputs can sharpen our thoughts, over-reliance can potentially atrophy the “thinking muscles”, which is our most important tool.

• Gen-AI (and specifically LLMs) are probabilistic tools that can be guided by human-designed workflows, which either comes from the gen-AI companies or from us. Because of this nature, it’s nigh impossible to expect their output to rigorously capture the full gamut of nuances and emotions that we need to handle/express.

• Leaning too hard in gen-AI can erode human trust, which are essential to our teamwork, as well as the relationships we have with our players and other partners.

When/where and how to use gen-AI

I will separate gen-AI in general and LLMs a bit here, because there are cases where they are used for distinctive purposes.

For research

I strongly believe that all great work is the result of spending an unreasonable amount of time on problems others simply dismiss (but not necessarily the other way around, unfortunately). What this means is that a great deal of research and experimentation must happen for us to write good stories, draw interesting artworks, compose pleasing music or write robust code.

In the past, when (Google’s) search was not littered with SEO ads, it was the de facto research tool on the Internet. Before that, we would go to the library, read curated magazines, talk to experts, go to classes, etc. These are all research activities.

LLMs, due to being new, do not exhibit this issue. Thus, its large corpus of material is very useful if we need to do any kind of research. Though, I would argue that it’s better at text-based search, which is useful for writing and software engineering. I have yet to find any prominent image-based or melody-based search tool.

Still, this is just a phase. Should there come a time when even LLMs are littered with ads and engineered contents, we should do fine if our research skills remain strong. This means honing basic skills like fact-checking, finding and navigating specialized publications (research journals, community forums, user groups, etc.), as well as reading-comprehension.

For editing, reviewing

LLMs presents two very powerful paradigm:

• An instant feedback loop, trained on a large corpus of human behaviors on the Internet.

• A dataset of what many people considered to be “good”, in the sense that it’s popular (instead of being an absolute good, if there is such a thing).

This allows them to assist as editors and reviewers in the form of things (e.g: spelling, grammar, structure, flow, etc.). However, it does not offer much beyond telling us what’s popular, when it comes to the essence of things.

To produce good work, we must perfect both the form and the essence.

For creating

This section is really long, because I think this is where the most debate about gen-AI usage will be. Plus, I have personal anecdotes to tell.

One of the hardest tasks for any creative person, in my opinion, is to create something from a blank state. Here, gen-AI is very powerful here, as it can leap into the unknown with just a little bit of prompting. It’s like sending a scout into the fog of war, so that we can get the lay of the land (and spot important activities, sometimes).

If used well, this essentially facilitates faster prototyping and visualization of concepts that would have taken considerable efforts to get started.

However, I would caution against using gen-AI beyond prototypes and throw-away sketches, because it’s not going to match exactly what we have in our mind at the end of the day. Plus, relying too much on prompting derives ones from the actual production skills and knowledge that we will need to finish the work.

I think my first hand experiences here will help, because I have experienced this from multiple angles: a newbie (in pixel art), an intermediate hobbyist (in writing) and an expert (in software engineering). Because of the timing, I have perspectives for both pre/post gen-AI rise.

As a newbie

When we are new, we lack both the understanding of the domain, as well as the language and context to ask questions. For example, when I first started drawing pixel art, I struggled to understand how to pick colors for shades. It was only after learning about color ramps that I had a better idea on the how and why. It turns out that there is both a logical process and an artistic choice behind these. During this phase, it was actually being able to find good books or guided learning experiences (e.g Pixel Logic, Pixel Art Academy: Learn Mode). They gave me a more holistic lay of the land, which helped a lot in mapping out how I should improve my skills.

During this time, I also dabbled in using Stable Diffusion and DALL-E and even specific pixel art gen-AI tools like PixelLab.ai to generate some work, but the result has not been dissatisfactory. I would chart this partly due to not knowing how to prompt and partly because what I have in mine is very unpopular (e.g: non-human character, scene with very specific compositions, etc).

As an intermediately-skilled person

When we are somewhat knowledgeable, it’s actually the practice bits that will get us to produce better results. Using gen-AI will not help us here.

• Before gen-AI, I had already written a fair bit of things (mostly technical stuff, but also the script for a music play and some fictions). Also I read a lot of fiction, so I roughly knew what good writing should feel like, even if I couldn’t produce to that degree.

• When chatGPT came out, I was amazed at first in how it can write very convincing stories albeit with me prompting heavily. However, I realized it was a clutch once I started on writing for “Have a sip”, as I ended up spending far more time prompting to reach a particular feeling than actually writing (maybe I don’t know how to prompt it to write mono-no-aware stories). But at that point, I realized a more detailed prompt doesn’t actually help. To save time, I should just do the dirty work instead. And over the 1+ year of writing and re-writing a lot of parts in “Have a sip”, I think things have gotten better, to the point where I can sit down and write an acceptable piece in 1-3 weekend evenings (around 4-12 hours of writing, excluding the thinking time). This article, for example, took about 4.5 hours.

• Meanwhile, continued use of chatGPT to generate things start to feel weird, beyond a certain point (especially with the chatGPT 5.x). Sometimes it would throw me back a technobabble that had neither head nor tail. Or when it works, it would sometimes generate stories so clique that it’s cringy to read, not the type of nuanced writing that I would have enjoyed.

Looking back, I believe the act of writing frequently helped more. With a good and fast feedback loop, which LLMs can somewhat provide, it’s easier to do deliberate practice and improve our own skills. This pays dividends more than any advance prompting technique can give, because now we don’t need an extra layer to translate our ideas into reality.

As a person with expertise

When we have reasonable expertise, LLMs are time-savers. This applies to my day job as a software engineer. In most cases, even at 200 WPM, I can’t match the output of a few simple prompts in chatGPT at all. And sometimes I would spend far too much time thinking/procrastinating that I don’t have anything to show for output. This is where I think gen-AI shines, as I can give it pretty specific instructions on what I want, get the generated output and do a bit of editing to arrive at exactly what I would need. However, to get to this point, I had already spent 10+ years writing a crap load of code, reading both good and terribly-written programs (both my own and others), as well as building enough intuition on what worked and what didn’t.

This is where there is a dividend in learning how to prompt, actually, because it allows us to exert more precise control on the output of LLMs. And if we think about it, this is no different from learning a programming language/DSLs. Then, the more we understand the underlying mechanics, the better we will be at controlling the outcome.

A note on ethics/copyright

This part could be sensitive, since as creative people, we also need to make ends meet. And it’s quite clear that gen-AI is eating our shares of the pie.

I’m somewhat lucky that I don’t have to compete with gen-AI for my day job yet. And for my work on “Have a sip”, I have shifted from a protective, commercial-minded mindset to more of a hobbyist one, so I don’t mind things being scraped and copied as much.

However, it’s pretty clear that these gen-AI techs are being trained without people’s consent, whether we like it or not. And it’s a real issue that it’s taking away jobs and growth opportunities for various people, especially folks who make a living producing creative works.

So it’s a conundrum: as people keep paying for gen-AI and work that leverages gen-AI, things will be increasingly harder for us creatives. But at the same time, it’s not possible to escape from gen-AI usage, especially because it does have some real benefits.

I’m not so visionary that I have a solution here. Personally, I feel that applying the canceling culture on anything AI-generated is just venting, as we can’t fight the tides alone. Plus, I believe a certain group of creatives, myself included, benefits from being able to leverage gen-AI to do more things with less resources and time. However, I also don’t want to fully embrace generated content, which has started to flood the Internet.

I just hope that as we struggle against this new phenomenon, we will be able to come out of it stronger instead. And to that end, I think it’s better to be more kind to those we feel are genuine human creators, while being more critical of generated content.

If it’s any consolation, I actually feel that it’s the very act of using gen-AI to assist with production of “Have a sip” that left me feeling more confident in my own skills. As I became more aware that, without significant investments, gen-AI wouldn’t be able to produce work that is close to my expectations.

Admittedly, these thoughts might change in the future, as more powerful models are rolled out, or if someone uses gen-AI to actively steal my work. But if someone really wants it to happen, it would happen regardless of if gen-AI was involved or not.

In the end, I don’t think we can fight the tides of our time. But at least within BitsGofer Studio, I will remain committed to ship human-crafted products and be honest about how it’s made. The audience will be the judge on whether the results are hollow or genuine.

Conclusions

As with many of my musings, there isn’t a clear outcome from this article.

However, as this gets applied to BitsGofer studio, I think what will stay is that:

• We don’t reject gen-AI outright. Instead, we will learn to leverage it well.

• We will still work on honing our creative muscles.

• We should be honest about how we use gen-AI to our players and partners, even if it hurts reception at first.
  This is because we value human trust, and that means not lying about how we do things.

A surprising outcome

Since I have been thinking about this AI debate for many months now, it actually produced something that I’m quite pleased about:

In “Have a sip”, there will be a character (Rebecca) who is an aspiring musician, with a love-hate relationship with AI-generated music. A lot of my musing here will actually fuel that aspect of her character.

Try to copy that , LLMs :)

P.S. Forgive my StarCraft references, if you notice them.

A friend of mine mentioned the idea that using gen-AI is like “sending a scout to the fog of war”, and it immediately trigger me to think about “form” and “essence”, haha.

Sometimes I don’t know why I still put hours into such an old game (1000+ hours now, haha), but it’s definitely something that I keep coming back for comfort.

During these plays, I found myself increasingly wanting to customize various aspect of the game, especially the NPCs. A big part of it is stylish preference (I tend to like certain styles that are more common in older anime manga). It’s also nice to see variety after playing for so long.

I used to have lots of portraits and character sprites mods. However, because the load order and different programming styles, they ended up conflict with each other. So at first I started a mod where I can program these changes correctly.

In the midst of that, I got interested in pixel art. So the thought became: how about actually customizing the game assets myself. This led me down to learn a completely new skillset in drawing, which turned out to be a fun hobby, too. Thus, I attempted to create extra outfits that each NPCs that matches the seasons.

The mod is incomplete, as other priorities in work, life and recently my own work for “Have a sip” have picked up. However, it’s here if you still play Stardew Valley:

https://www.nexusmods.com/stardewvalley/mods/10999

Credits: I just based my edits on Ohodavi’s incredible work for the Stardew Valley’s anime portraits. He’s a talented artist and produce much better quality work than my shabby things.

Here are some samples:

The base characters are from Ohodavi’s mod, with the (shabby, lol) extra outfits are made by me :P

Enjoy,
exklamationmark

Outside of making the game, just setting up the technical infrastructure to run everything is no simple task. For example, there are:

• Github

• Google Workspace

• Communication

• and more

Even as someone who work in infra, thus having the knowledge and know-how, I actually doing all this work is tiresome for me, haha. But I think it’s worth it, especially if I ever need to bring in external collaborators in the future (e.g: artists, composers, developers, etc).

One thing I learnt from my job and decide to do different this time, however, is to try and manage things as code.

Of course, it can’t be 100% infrastructure-as-code. But it should be possible to as automated as possible. That way, it will be possible to keep the technical operations lean (since it’s automated).

Aside: Choosing a communication platform

This actually took a few days to figure out. At first, I was wonder if it make sense to self-host a communication tool like matrix. This is because most tools out there like Slack, Google Workspace, MS Office, Discord, etc will charge you per user, which, if you are running a studio of mostly contractors and part-timer, will be a huge unnecessary cost.

But diving deeper into the hosting work involved revealed that the labor cost is expensive as well. At this point, I’d prefer some free service, try not to rely on it too much and the re-evaluate in the future.

In the end, I chose Slack because that’s what I’m using daily && feel that it’s a good platform (as opposed to Google Talk or MS Teams, which I also used in the past).

Let’s just hope that it’s possible to migrate/manage this better in the future.

The game “Have a sip” is about quiet human moments. Because of this, the game’s stories need a certain type of context and background. And because it’s 2025, writing about a “robot running a traveling coffee truck” actually requires serious thinking, especially against the backdrop of all the current AI developments.

The starting points

I chose a near-future fiction world of 206X (when HS is hopefully finished :P), so these axioms can be established:

• Robots are (somewhat) wide-spread in society.

• There isn’t an artificial super-intelligence.

• People and society as we know it today still exist at large.

This means a robot serving coffee is not a spectacle that draws a crowd. It also allows for the player’s character - the quiet robot - to feel unique.

Similarly, the lack of an artificial super-intelligence is intentional, because the presence of a Skynet/GLaDOS, or even a benevolent super-AI will cast a very, very different light on how society would feel about thinking machines.

Corollary, this implies that in our fictional world, advanced computing techs like quantum computing or biocomputation haven’t had a commercial breakthrough. Plus, other life-improving techs like fusion energy, neural links, etc are not there yet either.

Lastly, keeping the fictional society more or less the same as we know it today (late 2025) is a key point for HS. It means that stories about life’s impermanence, small joys and happiness are still relevant. It also allows us to carry existing tensions of the time into the game: rich vs poor, native vs foreigners, city vs rural, AI vs human, etc. These conflicts then serve as contrasts to the cozy, healing sections, clearly delineating emotional peaks and valleys.

In fact, ensuring this “human 1.0” setup is fairly important to me, as I read a fair amount of sci-fi where a single technology leap, like brain-computer interface, gene-editing or even language comprehension can change the very fabric of society/thoughts. I don’t want those to be the focus of HS, because this is not a cyberpunk game.

The game’s world is definitely far from grimdark, but I also don’t feel that it’s exactly solarpunk/hopepunk either. If you know of a label for this, feel free to suggest it to me.

Even more details

Next, the three axioms above need to be furnished with additional details, so the world feels more “full”, consistent and believable. For example, let’s take the “no artificial super-intelligence” axiom, which seems to run against a lot of pep talk about AI as of late 2025. To make it flow better in the fiction, I added these three trains of thoughts:

AI growth is stagnant due to economic causes

This is quite likely to me. Similar to many hype cycles, there will be a point where people and investors start to demand value from AI investments. This is likely to retain only profitable AI companies who produce models that are closer to tools than real intelligence (because those will sell). As an older person in tech, I feel this is more likely, unless we actually experienced another breakthrough similar to the jump from expert systems to deep learning.

Legal and bureaucratic frameworks drag growth even further

This is probably the weakest part of the fiction, seeing that AI companies are doing whatever they please for the most part. But maybe at some point, there will be large-enough issues that force regulations to step in, like GDPR.

Moral and existential hesitation runs strong

This one is quite believable, as we already saw people who were key to modern AI developments talk about their fears of AI. The degree of severity will be different depending on who we ask, but I think it’s safe to say that most regular folks harbor some doubts about whether AI is truly a good thing to have. If you are in doubt, look no further than the recent Steam’s AI disclosure saga to see how this plays out.

I am a tech/knowledge worker who lives and breathes these technology bubbles. And I have to admit it’s not always easy to distinguish where the actual possible technological progress ends and where the koolaid begins.

Closing thoughts

Anyway, we should have enough AI speculations for now. What I want to share here is the logic behind the world of HS. I hope all this work will make the phrase “a robot running a traveling coffee truck” feel more believable.

If you enjoy reading these world-building details ^_^, there’s more to come. Please stay tuned!

Cheers,
exklamationmark

Journey with a quiet robot who inherits a traveling coffee truck. Keep a cozy space for strangers and regulars. Master brewing and learn the rhythms of the business. In a city optimized for hustle, would you still serve with mindfulness and care?

After many revisions, the game I first envisioned in 2023: Have a sip (HS) now feels quite solid.

The trigger that sparked work on HS was my own mid-life crisis [@_@]. This was, after all, a time when I desperately needed a creative effort that I have full agency over. The project has also been sustained by the desire to create stories for myself and others (perhaps even for my son when he’s old enough). These are stories that are not preachy, more grown-up, yet can still channel hopefulness against the backdrop of cold, harsh reality.

Since then, the project has started to take on a life of its own. And it’s now at a point where I am comfortable sharing more details.

At its heart, “Have a sip” has a simple premise: serve drinks to patrons, then sit back as their stories unfold. While the part about drink-making is interesting itself, it’s the characters that ordered the drinks, their conversations and life that are the core identity of the game.

On that front, I do have specific stories to tell, for example:

• A moment filled with child-like amazement, where a toddler attempts to show her parents the new flower she noticed on the sidewalk.

• A wishful, melancholic evening when an aged worker thought about his past choices and how things could have turned out differently.

• Minutes after a son sent off his elderly parents at the train station, with him noticing visible marks of time on their silhouette.

• Break time after school, with excited teenagers swapping tips and theories on their latest (board) games.

• A lazy Sunday morning where a tabby cat greets two strangers, rubbing his cheek at their legs and purring with satisfaction.

• and other small, fleeting stories like these...

These moments are not epic adventure stories. In many cases, they aren’t particularly dramatic either. They are also not the sensational stories that seem to dominate my media feeds. Still, I deeply believe there’s something to be gained from stories like these, where we slow down and see the world through a more grounded, nuanced and personal lens. It’s relaxing and cleansing, in a spiritual way, too.

If you have ever read or watched Bartender, Gohan no Otomo or Yokohama Kaidashi Kikou, these stories about life should feel familiar. It’s because “Have a sip” draw a great deal of inspiration from Japanese works categorized as mono no aware (物の哀れ) or iyashikei (癒し系).

Going further, I want these stories told not just with words, but also accompanied with visuals, audio and interactivity. As a result, “Have a sip” is a game instead of a fiction series. Being ambitious, I also wanted to push the envelope so there’s actual gameplay: making drinks, running an F&B business, delivering to people. This will invite the “readers” to participate in the world, where people-watching goes beyond lines in the dialog box itself. Now as “players”, they will be able to interact with the stories’ characters, contemplate the events in the context of a larger world, and even draw their own meaning about the negative space between conversations.

I believe this is a goal worth striving for, even though it immediately raises the difficulty level by 1000x!

Surprisingly, rather than feeling dread and giving up, I found myself coming back to work on HS again and again, even as I drown in work deadlines, family responsibilities and health issues. Having produced some fictions in the past, this tells me that the idea has legs and will go places in the future. So it’s a responsibility of mine to see this through.

As the end of 2025 draws near, it’s almost 2 years of moonlighting on “Have a sip”. I’m pretty happy, actually, that there’s enough material to share about it publicly.

It’s probably not going to be finished anytime soon and there will be a lot of production hurdles, especially as I have very limited time as a solo dev on a hobby project.

However, if you have read this far, I believe that HS will be a project that you will enjoy. So please keep coming back to this blog from time to time for more updates :)

Finally, I wish you well and sincerely hope we can connect around HS in the future.

Cheers,
exklamationmark