Every New Year's resolution I had over the past years never worked out. So I stopped having them and thought about something manageable I could achieve. Which was also not working out because every time I try to work on a side project with a deadline, something occurs and moves my attention.

With this in mind, I started to make a wishlist for the new year. A list of things that were nice to achieve but not mandatory.

As a developer, for example, I want to release my newly created app, which I worked on in December (#AdventOfProgress). Then, use this app as a template and create a new app with a different topic, where I can reuse 75% of the code I already have. :) If this gets done this year, it would be nice to also have a small React Native app for #pelletyze. This could also be done in a small focused sprint because I only need the frontend; the backend is already working.

Fast forward; writing the above was in the past, and the pattern continued. I’ve created an entirely different app without finishing the first one. 😂 On which is now focus all my spare time. It is a little kids game. More of this in the next post.

Having a wishlist with maybe some milestones is a nice thing, I think. For example, having something done on my birthday. Or achieving X until summer and Y until autumn and so on. :)

Besides all the projects, there is still the private life, where I have to achieve things that are not fully in my control. Here, I stopped entirely having wishes. Here is the mantra: it’s done when it’s done. 😂😂

85 of #100DaysToOffload
#log
Thoughts? Discuss...

I left 2025 satisfied and happy among my loved ones. We gathered at my home with some friends and their kids. It was a nice evening. While waking up, I started to write these words. I initially planned to write them before leaving 2025. But this time I will publish my review. For 2024, I’ve started the post but never finished it.

While reading the never-published post of 2024, I realized that 2025 was good and not as bumpy of a ride as 2024. 2024 had many ups and downs. And I can say personally and as a family, we settled somehow.

2025 started with finishing #100DaysToOffload at the end of January. Finishing the challenge made me proud. Because I never really finished something similar on the web. All I started was abandoned after some time.

Most of the spring and summer were not present for me, writing-wise. I had numerous freelance projects and focused a lot on family and non-IT-related stuff at home. In consequence, I did not write a lot. I’ve started the #TheMonthProject to push me to get my #pelletyze app done. I had a lot of fun writing these posts. But because of spring and summer, I released it quite late in October 2025. But this was marked as a giant achievement for me. I worked a lot on #pelletyze and I’m happy that it is now in a presentable state. :) Since the release, I did some small updates but never did marketing for the site to reach a user base. Because I still have some features and small improvements I want to implement before bringing it to a wider audience.

In spring, I tried Cursor and made a subscription. I wanted to see what AI hype is all about and how it works out. For a year I was already a Copilot/Supermaven user and had a small glimpse of what AI can do. For me it was quite a learning curve, because I needed to find my flow. After I found it, I tried Claude Code and never looked back. 😅 I still have a Cursor subscription because I’ve subscribed for a year, like I did with Copilot and Supermaven. Which was not a mistake, but in a year a lot can happen. Especially in the tech and AI space. So for the future, I know that I just try things out on a monthly basis. My most used AI tools now are ChatGPT and Claude Code. Maybe I should also write about my usage of them in another post. To end the paragraph, I can say that in 2025 AI had a massive impact on how I work now, and it improved a lot for me.

In the summer I made an old friend after over 10 years. We split in a not-so-friendly way and never talked it out, so I never knew in which state we were. But I tried to take all the courage and wrote him a message with what I feel about us. The good thing is no one was mad, and we’ve met and talked for some hours. :)

Over the summer, we made a hard decision. Our oldest was on the path to start school. But we decided to let him go to the kindergarten for one more year. He is now with his brother in a new kindergarten. The hardest part is not the new location or that he is not in school; for him, the hardest thing was leaving his friends. Which is something we had in mind but never thought that it would have such an impact on a little boy. Socially it is hard for him. But we hope that eventually, it is better for him. Since he got six on his school enrollment. He was not thoroughly ready for it. In 2026, we then have his school enrollment, and I hope that it improves everything for him, because he can then see his old friends again daily.

In December, I started my #AdventOfProgress event. Last year I did #AdventOfCode and #AdventOfTypescript and while it was fun, it cost me a lot of time I could have spent on something better. And this year, I wanted to spend the time on something with a real outcome. So I developed a React Native app in December. It was a lot of fun, and I had a prototype, which was planned to be done in the spring of 2025. 😅 But this is not relevant. I completed something again in 2025, and this is important. I now need to tweak some things and complete the landing page so I have a releasable app. The prototype is installed on iOS and Android on the phones of some friends, and this is a wonderful feeling. They can provide feedback, and I have a small audience right from the start. :)

Over the December break, I also finished most of our basement, especially the playroom for the kids. I’ve added a swing, a therapy swing. We know this type of swing from the occupational therapy for the little one. The boys and all the other kids who visited us over the last few days had a lot of fun with it. I also added wall bars so the kids can climb and “hang” around. Finishing this project gave me a gigantic relief and gave me a feeling of being free. Sounds strange, but this project was now in the works for some years. Which was not my fault. Mostly. Progress here had depended on some external people.

So the 24.12. marked a point where I could check some points on my to-do list as done. So I could start some new things, which were waiting for some time now. In this case, start setting up a home lab. I used an old notebook to install Proxmox, Forgejo, and Vaultwarden. I can now self-host my Git projects in my local environment and access them via VPN from the outside. Setting up Proxmox with a good backup strategy gives me a foundation I can build upon in the future. I plan to extend this all with Home Assistant and other tools that will improve my life. :)

All this sums up 2025 quite well. It was a good year. And I look forward to what 2026 will give me and my family. 😎

83 of #100DaysToOffload
#log #lastyear #review #2025
Thoughts? Discuss...

Currently, I'm on a path to improve the UX a bit by giving more feedback on actions.

Last time I brought a CSV import error to the frontend, which otherwise failed silently and had been a requirement from the start.

The next step is to show a success message after the user imported CSV Data successfully. The difficulty here was, that I didn't want to convert my import component into a client component. So I was unable to use useActionState. My solution now is, that I created a Catch-all Segments route. Now, after a successful import, I can simply redirect to this page and show a success message. Which is not ideal, and I would prefer something like useActionState for server components, but it is what it is.

18 of #100DaysToOffload
#pelletyze
Thoughts? Discuss...

Finally, I found a solution to throw an error at the frontend, while importing wrong CSV Data on the server. For Fast-CSV, I needed a solution to parse the data and put the data into the database. While this part was easy, the error message from Supabase was swallowed, and I had no practical option to present the error to the frontend. Or, there was no uncomplicated way, since now. :D

const stream = csv
  .parse(options)
  .on("error", (error) => {
    console.log(error);
  })
  .on("data", (row) => {
    result.push(row);
  })
  .on("end", async () => {
    const supabase = await createClient();
    const { error, statusText } = await supabase
      .from("fillings_import")
      .upsert(completeFillings(result))
      .select();

    if (error) {
      throw new Error(`${error.message}, ${statusText}`);
    }
  });

stream.write(fileData);
stream.end();

This was my initial solution, and the error at the end was never shown. 🤷

The new version is wrapped with a new Promise and calls reject if adding data to Supabase produces an error. Easy, right? I'm so happy that I don't need to wrap an <ErrorBoundary /> or something else.

await new Promise<void>((resolve, reject) => {
  const stream = csv
    .parse(options)
    .on("error", (error) => {
      console.log(error);
    })
    .on("data", (row) => {
      result.push(row);
    })
    .on("end", async () => {
      const supabase = await createClient();
      const { error, statusText } = await supabase
        .from("fillings_import")
        .upsert(completeFillings(result))
        .select();

      if (error) {
        console.error({ error, statusText, result });
        reject(new Error("Looks like your CSV is not formatted correctly"));
      }

      resolve();
    });

  stream.write(fileData);
  stream.end();
});

This little fix makes me happier than it perhaps should. But in the end, that it. I thought much more about a solution than it took time to write the code. I thought at least on and off for 3 days about it. And today, the “a-ha” moment under the shower. 😎

14 of #100DaysToOffload
#pelletyze
Thoughts? Discuss...

The first one I did was next-intl v4. They wrote a nice blog post before v4 was released. So you were able to prepare your codebase before the switch, which was great and worked very well and without problems. 👍

Next in line was Tailwind CSS v4. And with it, Tailwind-Merge v3. You need to upgrade them together. Because twMerge dropped tw v3 support. Basically, this worked flawlessly. But some adjustments needed to be done. I use the reset.css from Josh W Comeau which needs special treatment when used with Tailwind CSS v4. Furthermore, I've added some custom styling to the html, body and h1...h6 tags. The result was that I had to wrap them to the correct layers for, so they will not collide with TWv4.

@import "./reset.css" layer(base);
@import "./custom.css" layer(base);

While using the codemod from TWv4 to migrate everything, it swallowed my custom classes. Which I had to add back manually. The new solution is with CSS only and is straightforward.

@utility border-image-highlight-b {
  border-width: (--tw-border-width);
  border-image: linear-gradient(
      to right,
      var(--tw-gradient-from),
      var(--tw-gradient-to)
    )
    1;
}

That's it. The rest was done via the codemod. :)

After the TWv4 upgrade was done, I continued with the Next.js v15 upgrade. Next.js also brought a codemod with it which did its job also very code. But it had an easy job here because I did nothing special. It changed some code in the code, which I had to clean up a bit afterward. Because it looked ugly and was too verbose.

Let's continue with the biggest pain, while I did the update on my #pelletyze codebase. ESLint v9. I was tried and erroring my way through the process but the documentation on both sides, Next.js and ESLInt were not so user-friendly then for the other codebases. Sure, if you just use ESLint, you are fine. But the combination with Next.js was a bit of a pain in the ass. Therefore, I don't like the look of the new flat config, especially the fix Next.js needed to bring in, to get everything to work. I hope this will improve in the future.

Before or after you upgrade, delete the .next folder. I had seen it much earlier to save some sanity. Because every lint run failed, and because there was some old code in it. Which gave me this error: a.getScope is not a function. After this issue was solved, I needed to add some packages because Next.js was not installing them by itself, thous it depends on them for linting. 🤷 These packages are: eslint-plugin-react and eslint-plugin-react-hook. This all happened on my second try. On the first one, a stopped after 2hrs and watched Severance. On the next day, I stared from scratch. I've installed a new test project with create-next-app and copied the important ESLint config stuff. Then I stepped my way through my old config. After I solved the major issues, the rest followed effortless. I had eslint-prettier installed, which was easy to put into the new config. And then there were some rules for next-intl, which was also just copy pasta into the new config.

Yesterday evening, I got to bed with a good feeling. Because I was done with the big update and I can now continue on my roadmap to the first public release of the #pelletyze app.

Man, what a huge update post. :) And the first one, completely written while traveling by train. I hope that someone finds it, and it will help to solve some issues on their side.

Now I've earned me some episode of Severance. 😎

13 of #100DaysToOffload
#pelletyze
Thoughts? Discuss...

Today I made good progress. Mostly for code in the background, so I don't really have screenshots besides one.

This will add the current version number to the frontend. First, I thought about a complex idea by adding the version number to an .env file or to a constant hardcoded inside the codebase. Then I thought, why not use the package.json version number? I maintain them with every release, so it is the single of truth. The code is also simple and just works.

import packageJson from "@/package.json";

export function AppVersionNumber() {
  return (
    <p className="flex gap-2 justify-center items-center">
      <small
        className="opacity-50 align-middle"
        title={`App Version: packageJson.version`}
        aria-label={`App Version: packageJson.version`}
      >
        {packageJson.version}
      </small>
    </p>
  );
}

Next on my plate, there were some bugs to fix. One, I saw at the turn of the year and I had it on my list since then. I couldn't really explain how this came together. Luckily, this one resolved itself after I removed the old data and put the new one in. Because the old data was corrupted.

Another bug was a simple fix because it was just a key prop warning. I've added the key prop and everything was fine. 😎

The last Bug was related to the data export to CSV. First I've string.replaced() my way through, but later I found out, this isn't an ideal solution. So I sat down and rewrote some parts. Supabase has its own csv export, right after you fetch your data. Which is nice, but the result was not importable for fast-csv.

Now I run csv.writeToString on my formatted data. The result cuts the file size by half. Which is not relevant because it's under 1kb but still, a good achievement.

  const formattedData = [
    ["bags", "filled_at"],
    ...(data || []).map((row) => [
      row.bags,
      format(row.filled_at, "yyyy-MM-dd"),
    ]),
  ];

  const exportReadyCSV = await csv.writeToString(formattedData, {
    delimiter: ";",
  });

And the last to-do for today was, to update all packages with the patch and minor version updates. If clicked through the application and everything worked, so this was a quick one too. :)

I would say that this was a productive Sunday. :)

I will visit my client from Tuesday to Thursday, and I'm sitting around 12hrs on the Train, so if I'm lazy, I will be watching some series or playing on my Steam Deck. OR I will be productive and work more on my Application. It depends on the mood. So lets see. :)

11 of #100DaysToOffload
#pelletyze
Thoughts? Discuss...

The Bug

There was a bug, where the checkbox was not recognized and the formData I've sent to the server was empty. This feature worked in the past and I don't understand why it broke.

The Fix

Because I use the @radix-ui/react-checkbox and don't handle the state manually, I need to wrap with a @radix-ui/react-form. That's it. 😎

While I was working on the component, I also transformed it into a server component. Which was easily done, by using getTranslation() from next-intl instead of useTranslation and making the component asynchronous.

The bug was the reason I've implemented the delete-all Button. To save me a trip to the Supabase admin page and clear the table.

This was my Sunday contribution to Pelletyze.

10 of #100DaysToOffload
#pelletyze
Thoughts? Discuss...

Here, on the left is the bug and on the right the fixed version.

Sadly, I don't have time for more at the moment. But I think it is better than nothing.

07 of #100DaysToOffload
#TheMonthProject #pelletyze
Thoughts? Discuss...

So, I just did some small clean up tasks. Updating the CHANGELOG.md, and tagging the current commit with the version number v0.5.0-alpine-shepherd-boy. Because I'm a massive fan of the series Better Call Saul, my version names will have the names of episodes from BCS.

And that's it for #TheMonthProject update #3. Furthermore, this is post 5 in the #100DaysToOffload challenge. The pressure to complete round 1 did something to me. I already have 5 posts within the first week. Which makes me happy. Seems like I'm now in some flow of writing blog posts. 🥳

05 of #100DaysToOffload
#TheMonthProject #pelletyze
Thoughts? Discuss...

Today, I've implemented a “delete all” button. To have the opportunity to just delete all entries. This is just a convenient feature so that I don't have to do it directly in Supabase. I don't know if a real user would need this, but it was easy to implement and saves me some steps. Most of the delete logic is already implemented, I just needed to generalize the button and the action. Doing Server Actions in Next.js is straightforward to implement.

The most time was used on the question, where I should put this button. While on it, I also fixed some minor style issues for desktop and mobile.

That's it for today's #TheMonthProject effort. Going +50 min on this simple topic feels a bit long. But anyway, progress is still progress. 👋

04 of #100DaysToOffload
#TheMonthProject #pelletyze
Thoughts? Discuss...