Maybe because acknowledging flaws in "y" is not necessarily "anti-y"? In fact, it is often "pro-y". I want to improve things I care about. A critical part of that is identifying flaws so they can be learned from and sometimes fixed.
1,755 karma · joined July 4, 2021
Maybe because acknowledging flaws in "y" is not necessarily "anti-y"? In fact, it is often "pro-y". I want to improve things I care about. A critical part of that is identifying flaws so they can be learned from and sometimes fixed.
That doesn't work well in mountainous areas, which are often rural. There are three towers within a couple of miles of my house, but nothing close to line of sight to any of them. ~1/4 mile away I can get full service, but I have none at all at home.
Luckily Comcast / Xfinity rewired our little town a few years ago so we don't have to rely on satellite (not great during the heavy snowstorms and thunderstorms we get). I'd love to use cellular as a backup as we have 3~20 full days of blackouts per year (most of us have generators and/or batteries) and Xfinity goes down 80-90 minutes after a blackout starts.
Many bugs come from writing something that does not match intent. For example, someone writes most of their code in another language where `sleep` takes milliseconds, they meant to check the docs when they wrote it in this language, but the alarm for the annual fire drill went off just as they were about to check. So it went in as `sleep 1000` in a branch of the code that only runs occasionally. Years later, did they really mean 16 minutes and 40 seconds, or did they mean 1 second?
Leaving clues about intent helps detect such issues in review and helps debug the problems that slip through review. Comments are better than nothing, but they are easier to ignore than variable names.
I have an n305 with the CPU thermally bonded to its small aluminum case with a quiet 80 mm Noctua fan screwed into the fins of the case. The manufacturer on Ali Express said the fan is optional, but it can get to ~85°F in the room where the computer is, so I want to be careful. At idle, the CPU reports 5-10°F above the room's temperature.
It has 10 TB spread across 3 SSDs and 2 x 10 TB spinning drives attached. It's a Time Machine target for a handful of Macs and a Borg Backup target for several machines, including some across the internet using Tailscale. It's also running Home Assistant with AppDaemon (with dozens of little apps), Frigate (object detection for 3 Ethernet-connected cameras using a Google Coral TPU over USB), Paperless-ngx (15 GB of PDFs), LibrePhotos (1.2 TB of photos), Syncthing, Tiny Tiny RSS, a UniFi Controller, distinct PostgreSQL instances for various of those, and more. I count 21 Docker containers running right now, and not everything is containerized.
The spinning drives are powered down with a smart plug for all but 1-2 hours at night for backups. With those off, the thing sips power... 10-15 W most of the time with occasional spikes up to ~30 W when LibrePhotos is doing facial recognition or Paperless-ngx is updating its ML models. It never feels slow. I've been running one or more servers at home for 30+ years, and this single machine handles everything so much better than any combination of machines I've had.
Marimo notebooks are easy to diff when committing to git. Plus you get AI coding assistants in the notebook, a reactive UI framework, the ability to run in the browser with Pyodide on WASM, and more. It will also translate your old Jupyter notebooks for you.
For me, what uv is to package managers, marimo is to notebooks.
AI is great when it's the right tool. But the rate at which features are shipping at these companies is plummeting because so many features would be cheaper, easier, and better without AI. It feels like self-gaslighting on a scale that I haven't seen since the dot com days. And I see engineers and their managers struggling to maintain their sanity as they try to improve their products within the constraints of these policies.
Tools (or pick another word that illustrates this distinction) like encryption, hammers, etc. do not contain our information. They are fairly straightforward to reproduce. And therefore nearly impossible to contain. Bad actors will have encryption and hammers, whether we want them to or not. The only question is whether good actors will also have them, or if they will be restricted by laws. This, for example, can make it easier for datasets to fall into the wrong hands, because they are less likely to be encrypted.
I'd say that one thing inherently different about datasets is that they are continually used badly, including by well-meaning actors. Data is frequently misinterpreted, with good intent, to draw bad conclusions.
You might hit your thumb with a hammer. That hurts! People would be a lot more careful if misinterpreting data had such clear, immediate effects on them.
Also, there are many different groups with different passionate opinions in any community as large as this one.
For some types of problems, identifying worst-case behavior is straightforward. For example, in a hash table lookup the worst-case is when all keys hash to the same value. To me, it seems like overkill to think in terms of an intelligent adversary in that case.
But in the problem described here, the worst-case is harder to construct. Especially while exploring the solution space given that slight tweaks to the solution can significantly change the nature of the worst-case. Thinking of it as adversarial implies thinking in terms of algorithms that dynamically produce the worst-case rather than trying to just identify a static worst-case that is specific to one solution. I can imagine that approach significantly speeding up the search for more optimal solutions.
We have whole-house backup batteries, which we can charge with a generator for longer outages (we also have solar in summer, but the sun doesn't get above the trees in the winter). The batteries/generator would have to be much bigger to replace that furnace with a heat pump. They will power the propane furnace (mainly the forced-air part). About 1/3 of our heating is firewood, but during deep cold spells, it's hard to keep it above ~55°F in rooms other than the one with the fireplace without help from the furnace.
We do plan to install a mini-split system before too long, and use that when we do have electricity, relegating the central propane furnace to power outages. We already use an evaporative cooler for cooling, which uses far less electricity than AC. We'll only use the AC function of the mini-splits when we have a lot of smoke from wildfires in the area (evaporative coolers blow in lots of outside air).
https://x.com/zackfreedman/status/1650629770156326912#m
or for those allergic to X:
https://lightbrd.com/zackfreedman/status/1650629770156326912...
I'm with you on this. Software engineers talk about being in the flow when they are at their most productive. For me, the telltale sign of being in the flow is that I'm no longer thinking in English, but I'm somehow navigating the problem / solution space more intuitively. The same thing happens in many other domains. We learn to walk long before we have the language for all the cognitive processes required. I don't think we deeply understand what's going in these situations, so how are we going to build something to emulate it? I certainly don't consciously predict the next token, especially when I'm in the flow.
And why would we try to emulate how we do it? I'd much rather have technology that complements. I want different failure modes and different abilities so that we can achieve more with these tools than we could by just adding subservient humans. The good news is that everything we've built so far is succeeding at this!
We'll know that society is finally starting to understand these technologies and how to apply them when we are able to get away from using science fiction tropes to talk about them. The people I know who develop LLMs for a living, and the others I know that are creating the most interesting applications of them, already talk about them as tools without any need to anthropomorphize. It's sad to watch their frustration as they are slowed down every time a person in power shows up with a vision based on assumptions of human-like qualities rather than a vision informed by the actual qualities of the technology.
Maybe I'm being too harsh or impatient? I suppose we had to slowly come to understand the unique qualities of a "car" before we could stop limiting our thinking by referring to it as a "horseless carriage".
I live in a rural area and it would bankrupt our county if we had to maintain all the miles of road (far more per taxpayer than urban areas) if the state wasn't doing so much of it. The state uses expensive machines to do much of that work efficiently. It wouldn't make sense for our county to buy that equipment and have it sit unused much of the time. So the county would be less efficient at it. And that's before we get to things like duplication of administrative roles around that work.
Sometimes that means urban areas are helping fund some of my local roads. And sometimes that means I'm helping fund their public transport. When done well, we all get far more for less tax money.
Yeah, it feels like a lot of these stories are the new version of the methodology / database / framework hype we've seen for so many years... with our new tool, you can write Reddit / Yelp / Wikipedia / S3 / etc. in a week. Sure, you can write a prototype that kind of replicates the surface level functionality. How about the actual hard part? Things like scaling, optimization of computing resources across large fleets, evolution of the system to attract more customers, fighting spam, increasingly complicated integrations with 3rd parties, maintenance, etc.
So much of this will turn out like all those things we've seen before. It will take skilled engineers doing a lot of thinking to figure out the right way to leverage the tools to make better systems for less.
There is no home mail delivery at all in our town, nor in much of our county. Each affected home gets a free PO Box.
I've found this to be very true. A trick I found that made this easier for me is to leave a trivial task to start tomorrow with, often with notes to remind myself what to do. Ideally the trivial task is on the way to something bigger, not finishing something. That gets me into my editor, gets me running the code / tests / etc., and gives me a trivially easy way to get moving. Then the motivation kicks in and I can start moving for real.
The same approach helps me with tasks outside of software development, and even outside of work.
His argument is that safety equipment makes people complacent, especially when they are experienced enough to move quickly. If you have bare feet / legs, you are much more aware of the dangers and hence more careful. He still has all his limbs and the fingers / toes at the ends of them. Too many of his former coworkers do not. He is nearly deaf, so using hearing protection might have been better.
That's all anecdotal at best, but experts often disagree on the safest approach for themselves vs. others. And what's best for experts is often not what's best for novices, and vice versa.
- the one that came with your laptop no longer works
- you use your laptop at home and office, and don't want to carry the charger back and forth every day
- you travel a lot and want something smaller/lighter than your stock charger that can charge your laptop and phone at the same time, both at high speed
"I need to figure out what brand of paints and brushes this painter used so I can paint like this."
Of course not! It's the painter that determines the quality of the painting and not the maker of the tools. A great painter (or filmmaker or cook or software engineer or ...) will understand the unique attributes of the tools available and leverage those to do great work, whether that's in oil or water, black & white or color, Python or Rust. A difference between experts and non-experts is that experts will find opportunity in the constraints of the tools they have available, and not only frustration.
I believe this extends to engineering managers. I want managers who are good at spotting the unique advantages of each person on the team and are good at structuring the roadmap and individual projects to let the team get the most out of those advantages. And I want them to spot where advantages and disadvantages can be paired to enable learning. All this helps teams see how valuable their teammates can be and how much they can learn from each other. I've seen it result in teams achieving remarkable outcomes while having a ton of fun doing it.
Scaling this up further... I want senior management that is in tune with the unique advantages of different parts of the org, and who then use that knowledge to make better decisions about direction. We can go in direction A, B, or C... that group over there is great at A, so let's pick that and give it to that group. Some see Conway's Law as a sort of "doom", but I've seen it used to the org's advantage with this kind of thinking.
In practical settings, the way to characterize performance will be more clear from context, often giving one (-ish) clear metric for each dimension you care about. For example, if an endpoint has a hard timeout of 100 ms, then it's pretty interesting to look at the percentage of real world requests that are faster than 100 ms. If the same solution is also used in a setting where throughput is more important than latency, then an additional metric is probably needed for that use case. Multiple metrics are needed for multiple use cases to capture trade-offs being made between those use cases.