HN user
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.
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.
Operating Systems: Three Easy Pieces. Very well written read, a fantastic textbook overall.
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.
Does the team use a mono-repo? Or have multiple repos and track changes for that week to review?
I'm very curious. Curious enough to even try it.
I have used Arch Linux for the past 8 years. I've had 3 installations on four different laptops (I migrated one installation to a second laptop).
Your comment would be a really great description of my experience.
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.
I agree. I have had many similar struggles as you have had. With my commute I often came up with interesting ideas or solutions to problems. I've found the online scheduled meetings just are not as effective as inpromtu in person meetings. Idea generation and brainstorming are not as effective at home.
My own experience working from home probably follows this. I've gone back to work now, but I spent 6 months working at home. At the end it took me 12 hours of time to make up an 8 hour work day. It was just not sustainable for me.
Do you have weekly scheduled 1 on 1s? I have a few remote team members and make sure they pair up weekly just to feel connected and present. It's team member to team member, not like a traditional 1 on 1 with a lead. I know it's a very small measure, so I'm very interested in other comments here.
"Go is simple" is the main one and only reason I love Go.
I learned Rust in my spare time, and it took me months to get to the point where I could write anything useful at all. I never did feel like I knew the language. I just don't have the spare time and energy to put in such a monumental effort into learning a language. After 2 weeks of Go I knew nearly all the ins and outs of the language. Once you add in sophisticated and strict linting from golangci-lint you just can't go wrong. Code reviews are a breeze and understanding code is a breeze.
CD is avoided because most software products should not be delivered continuously, as it is inversely correlated to software stability for customers.
This has been shown to be flat out wrong. Stability has been shown to be highly correlated to the capacity to deploy quickly and often.
The answer is in the article itself. It gives you real historical data so you can predict how long the project will take with evidence, rather than just a feeling, hope, or guess.
Velocity is an aggregate measure of tasks completed by a team over time, usually taking into account developers’ own estimates of the relative complexity of each task. It answers questions like, “how much work can this team do in the next two weeks?” The baseline answer is “about as much as they did in the last two weeks,”
If there's one thing the last 50 years of software development has conclusively proven, is that estimating the number of man months (hours) a project will take doesn't work.
The OS must search page tables to allocate them to a processes memory space upon request. Without fixed sized pages the OS has to search for appropriately sized areas to satisfy allocation requests. Fixed sized pages solves this problem.
Edit: you would also then suffer memory fragmentation, not just lookup latency.
For already mapped pages latency would be an issue as you described.
Memory allocated in variable sized chunks has a lot more fragmentation. The OS would have to search around for free areas and keep track of them to be able to give memory out. Although, this is what user space allocators already do.
The book Operating Systems: Three Easy Pieces has a section to answer this very question.
Lisp has been around for decades. Wikipedia says 1958, which predates C by many years. It is indeed functional and favors recursion over loops.
I find I can't watch shows with season+ long arcs at all. It always ends up one way: rage-quiting at 3am on a work night never to watch another episode. All due to the fact that usually the episode boundaries are placed in the most suspenseful places.
However, shows like ST:NG or Stargate SG-1 I enjoyed completely. I'd watch one or two episodes at a time and leave feeling good.