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'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'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 use iwd and systemd-networkd. I don't use may applet or gui control. With my setup I just and up ignoring network configuration the majority of the time.
Edit: I've found iwd such a huge improvement over past wireless networking solutions. It's a big improvement.
I've used Roam Research for note taking for the last year. Before that, I spent two months trying out a dozen competitors. Using it the last year has been amazing for me. I definitely can't go without it now.
I've been using Duply as a simple CLI front end to Duplicity (not Duplicati) for years now. It's worked great for me on many servers and personal machines.
Working with the ESP32 is what introduced me to the concept of eFuses. Really neat. Allows you to run encrypted firmware images which cannot be easily decrypted even with full physical access to the hardware.
What alternatives have people come across? I know there is waterfall: months of planning followed by months of implementation, followed by a single deployment at the very end. Then there is the gradient of in-betweens along the line of scrum to waterfall. I've not encountered any other methodologies yet.
Have you ever seen CockroachDB, or Yugabyte? Both are not eventually consistent, but are horizontally scalable. It looks like to me it is a solved problem.