lgunsch

The somewhat novel part of my workflow, is after Claude has built something out, I have a second fresh Claude session review the code with a set of 16 custom questions. I've discovered that giving Claude questions to ask during code review improves things quite a bit. The questions mirror the exact things I would have asked myself about a pull request when reviewing it. I found this to be a real game changer.

The code comes out quite a bit better, and I would suspect that it uses less tokens in the long run. Simpler cleaner code I would suspect uses less tokens.

I've been using -R for many years. I've had people ask why, and it's simply because some tools don't have -r, but all had -R. So, I just remembered that -R works everywhere. Perhaps it's not as true anymore. At this point, I've been doing it for more than 15 years, so I don't even remember which tools don't have -r off the top of my head.

I took my Seiko 5 in for service mid last year, and after that it kept time well. I don't loose more than a minute over a week or more. But, I specifically sought out a mechanical watch because they're interesting to me. As a software developer, I feel like I don't need another computer strapped to my arm. I appreciate the intricate mechanics.

If IPv6 was going to be successful, it would have been successful years ago. It seems, people are just more comfortable with layers of NAT than native IPv6 everywhere. I'd guess that it should have been more backwards compatible. Similar to UTF-8 and ASCII.

Some of the other practices of CI are also important. Not explicitly mentioned by the article, but perhaps implied. CI is a lot more than just running tests on pull request. It's a whole suite of practices enabling teams to perform and ship better. Some of which include keeping branches short lived by merging back to main early and often. Keeping code ready for deployment at any time by using strategies like feature switches. This keeps the cost of shipping a feature as low as possible, avoiding issues like spending lots of time rebasing and merging long lived feature branches.

I was also going to mention this reminds me of Vala, which I haven't seen or heard from in 10+ years.

I've been using JetBrains IDEs for the last 11 years. Before that I used Emacs and Sublime Text. I've tried VSCode, Zed, and others. There's just no comparison on the code insights and code manipulation tools. LSP is far behind what JetBrains can do, although it's slowly catching up these days. I still use VSCode from time to time for other languages like Zig.

I've never experienced sluggishness, but, I also keep track of how much memory it's using and ensure I don't run low. It's clearly a huge resource hog, but I'm also glad for that. It's using all of my computers resources to analyze the code in amazing ways which help me develop fast. Emacs, Sublime Text, and others were all about typing speed. Fast development goes far beyond just typing speed.

I'm happy I switched to Colemak around 13 years ago. Mostly due to elbow pain. I do find it made a difference there.

In general, I do type faster than before, and faster than many people around me. That's likely only because I actually had to practice.

I've seen a number of ESP32 IoT devices here on HN, and I haven't heard many of them use firmware encryption with an eFuse.

In this case, it would have been pretty hard to create a certificate if you couldn't read the firmware.

But, also pretty impressed at the same time. I think this is the first Hacker News article I've read about an ESP32 IoT device which has any encryption at all.

He talks about it in one of his videos. The zip directory was a product of a side hustle of his, which Microsoft then bought out. In the video he comments how much easier it was to integrate when he had access to more internal apis.

I haven't checked in many months, but in the past it never has. It kind of semi-works but it's pretty buggy. I use Chrome for teams.

I'm on Arch Linux.

Years ago I used a very simple bash script font-end for Duplicity called Duply. It worked very well for the half-dozen years or so I used it.

This is my most favorite font to date. I've tried lots of others, but I've enjoyed this one the most. 100% worth the purchase.