I found this bit and wanted to share it.

»HTML’s Best Kept Secret — The Tag: Every developer knows . It’s the workhorse of the web. But ? Most have never touched it. Some don’t even know it exists. […]« — by @denodell

🧑‍💻 https://denodell.com/blog/html-best-kept-secret-output-tag

96 of #100DaysToOffload
#log #dev
Thoughts? Discuss...

Now with a much more profound understanding of AI and much, much better models, the changes I made here would have been done in minutes. I guess. 😅

The Resume-Project: https://github.com/danbruegge/resume

I have never written about it. This is one of my projects that had a low priority in the past and doesn’t get the love it deserves. But eventually, this is one that saves me a lot of work, and I need to adjust only a JSON entry after I’m done with a client.

Changes

Completed ✅

1. Outputs docx format, besides pdf.
   • I got the question from recruiters a lot if I could provide a docx file instead of a pdf.
   • After a lot of back and forth with some tools, I finally found a suitable solution.
2. PDF export is working again, now with Puppeteer.
   • wkhtmltopdf got deprecated.
   • It wasn’t installable via Homebrew anymore.
   • Now there is a modern solution where also the PDF looks better; wkhtmltopdf had problems rendering modern CSS.
3. Update to Next.js v15.5.
4. Update to Tailwind v4.

Planned 🏗️

• Design update.
• Update ESLint to v9.
• General update of all other applications.

Completing the HTML to DOCX conversion is a massive milestone for me. One that I thought would never be done. Because I did not see the use for it AND .docx is a shitty format. 🙃

I should invest more time in it. But if the clients provide long contracts, the need is not so high, so I constantly forget about it.

92 of #100DaysToOffload
#log #dev #resume
Thoughts? Discuss...

After a bit of research, I found nothing that resonated with me. Nothing that looked like a good fit. While researching, I found out that there were Sudokus for kids with shapes on paper. We tried them, and he liked it. Then it clicked, and I fired up Jippity. We talked and created a plan for an MVP game in React Native. Thanks to my #AdventOfProgress, I already had experience with React Native and a base from where we can start.

There were points that made the implementation easy. For example: offline first and no auth, so no Supabase or backend dependency is needed and less complexity. A clear and simple scope. No game engine is needed because of the missing game loop and simple graphics.

I had a lot of fun, and it was difficult to stop. After the initial MVP was complete, I kept adding features. AND it is the first project I started without having a domain name first. 🎉

The finishing line is in sight. There is a little bit of work left on the landing page that needs to be done and smaller visual issues inside the app that I need to address. Also preparing all the data for the stores, for example, taking screenshots for each language and adding marketing texts, needs a lot of work. It will be my first release of an app in the stores. It should at least look a bit polished. 😅

87 of #100DaysToOffload
#log #dev #game #kids #ai #claude
Thoughts? Discuss...

Recently, I saw Clawd.bot, which is a personal AI assistant and looks promising. Let's see what use cases I can find here.

84 of #100DaysToOffload
#log #ai #claude #dev
Thoughts? Discuss...

Since then, I've improved it a bit. I introduced the YOLO mode --dangerously-skip-permissions as default when I open CC, and I need to split the window pane on my desktop monitor to 1/3 and on my laptop monitor to ½.

The split introduced a new function, which is called on keypress.

local function split_for_claude()
	local screen = wezterm.gui and wezterm.gui.screens().active.name or ""
	local percent = 50

	if screen == EXTERNAL_MONITOR then
		percent = 33
	end

	return act.SplitPane({
		direction = "Right",
		command = { args = { "bash", "-lc", "claude --dangerously-skip-permissions" } },
		size = { Percent = percent },
	})
end

EXTERNAL_MONITOR is the name of the external monitor. The name you will get from opening the Debug Overlay and calling wezterm.gui.screens().

And the key settings are:

config.keys = {
  -- ...
	{
		key = "Enter",
		mods = "LEADER",
		action = wezterm.action_callback(function(window, pane)
			window:perform_action(split_for_claude(), pane)
		end),
	},
  -- ...
}

Now I hit leader+enter and CC opens in a 1/3 or ½ split depending on the display. :)

57 of #100DaysToOffload
#log #wezterm #code #dev
Thoughts? Discuss...

Last weekend, I wanted to try it out for a task where I didn't want to sit next to Claude, watch it, and prevent it from failing. So I’ve made a new attempt. “We” planned the task together; I tried to be as precise as I could be with the prompt and got a first draft as a result. Then we iterated and refined the plan until I was confident with it.

On the weekend, we had planned some family time. It was the best opportunity to let Claude go wild with the planned task. Later in the evening when I was back with the family, I was a little excited about how it worked out. I took a first look, and Claude had completed the task. The result was working, and the tests were green. So this looked promising. I peeked at some files, and it looked good.

After I did a full review on the next day, I was quite happy with the result. There were some small adjustments where Claude was not following the rules exactly, but this is ok. Like checking a PR from another colleague.

Maybe I should try this more. One idea would be that after a finished workday, I go into yolo mode with Claude and review the results on the next day. But before I can do this with confidence, I need to refine my Claude settings. The settings are there, but I never touched them, really. There is potential here. :)

50 of #100DaysToOffload
#log #dev #claude
Thoughts? Discuss...

Why is that so?

A simple explanation could be that in bigger teams, there are often people who are quite dominant, talk a lot, and usually know more than me. Maybe this influences me subconsciously. I’m not a dominant or submissive person. So I typically withdraw then and let the others be dominant. And say something if I have to or need to.

Perhaps it also has something to do with me not really being a speaker. I typically can talk a lot in a space where I’m confident. Most in small groups or 1-to-1. One example is presentations in school. I hated them. Preparing them was easy. But actually standing up in front of more than 5 people made me nervous. And I hated that feeling. Not the good part of feeling nervous.

What can I do with this new insight? I don't know. 🤷 I have to think about it, and I'm happy that I now have something I can work with. For the future, it would be best to get rid of this limiting behaviour.

46 of #100DaysToOffload
#log #dev
_Thoughts? Discuss...

For simple components, it works well. But if they are not just styled, for example, if they need to render a different element, it gets verbose. <MyComponent as=“section” /> now needs the asChild prop and then the section element as a child. It’s not that bad, but I think it’s ugly.

<MyComponent asChild>
  <section>{children}</section>
</MyComponent>

As someone who also uses many Radix components, I’m familiar with it. So it is ok, but it still looks ugly.

For variants of the same element, I migrated to react-twc with cva. Which gives a clean look and makes clear what needs to be used.

And for the rest, for example, labels and inputs, I kept them as is, for now. The label and inputs are wrapped with a div. Also, I need to pass down the Radix Form elements with the as prop.

Thoughts

For some components, I have to refactor the code. At the current state, I don't know whether it's worth using react-twc or not. For simple components, I think it is awesome. Furthermore, for components with plenty of variants, by using CVA. But for a complex one, I have to think about it and work out something that fits.

44 of #100DaysToOffload
#log #dev
Thoughts? Discuss...

The problem is that most of the time, no matter how much I’m into a task, I forget plenty of things. I don’t know why. So I came up with a simple structure and Obsidian.md as a tool. On how I can express my thoughts on such topics and also save them for later.

The flow is that I make a personal refinement for the task. Write a short text on what I understand and what needs to be done. After this, I'll work on a numbered to-do list, starting with the first step and so on. In this to-do list, I really write each tiny point down. Mostly to visualize the tasks, which helps to go into more detail. My brain's cache seems not that big. 😅

After I'm done with the ticket, I write a short summary and make a small internal retro with myself.

This costs a bit of time and mostly discipline to get it done, but I think the benefit is bigger than the effort it takes.

Bonus: if the ticket comes back to you, for whatever reason, you have all the information stored and can argue about decisions I made or just check on what went wrong.

Sure, I could do the stuff also inside the ticket itself to document everything. But, for me, it feels like not the right place to do it there. Important stuff related to the ticket still goes into the ticket. 👋

42 of #100DaysToOffload
#log #dev
Thoughts? Discuss...

Writing with CC is like writing with an elaborate sane person, who really knows more than you. (Most of the time.)

When writing a prompt to either of them, I have this mindset above for each in my head, and this is how my prompts look. Maybe this is the reason why my outcome on cursor is not as good as in cc?

Nevertheless is gain something from both of them, so the current state is ok for me.

41 of #100DaysToOffload
#log #dev #claude
Thoughts? Discuss...