Recent submissions

Comment · 2 days ago
The Senate can hold people in contempt with a 50% vote. So they could do something to reign in the fascists starting January, but I'm not holding my breath. And that's still a long road.
Comment · 9 days ago
Ah you're right. I was taking it very late from Munich to Garhing and it felt that long!
Comment · 15 days ago
The trains around Munich, Germany were fantastic for that effect. 15+ cars long with wide, open pivots.
Comment · 1 month ago
Mostly the spooky action at a distance. Gitignore expressions and inheritance of the ignore expressions can exclude files you actually need to include, and you basically lose sight of those -- admittedly those are probably safer bugs than including things that shouldn't be included. But if a file (or even specific lines) shouldn't be included, I would prefer the file/lines have a marker that says it shouldn't be included.

I run the same presubmits on pre-receive and merge requests, so you wouldn't get too far shooting your own foot. But yeah, if you're not using the feature then it wouldn't save you so it's not foolproof. I also run tools for scanning for credentials, etc.

Comment · 1 month ago
I prefer a presubmit check for DO NOT SUBMIT and also disable Git smart commits. And then I have those floating around as needed. Seems to avoid all the foot guns I'm reading about, and makes it obvious and easy for other people to use as well. I guess it still shows in my diff tree, but /shrug I still prefer seeing them.
Comment · 1 month ago
That's like asking why senior/staff engineers tend to review more code than write themselves. In certain environments there's a scaling constraint, and you can generally have wider impact through oversite than typing at a keyboard yourself. That's not to say one is more worthy of your time or not, just that it's not unique to AI.

Generally though, you are also investing your time into leveling up junior engineers to take over responsibilities from you. I just never really see that happening with AI. Even as it gets "better" technically, there's no real growth pattern to its work and it doesn't understand ownership or responsibility.

But if scaling isn't a problem, then sure just write it yourself.

Comment · 1 month ago
Reverse proxy to additional endpoints.
Comment · 5 months ago
I was being interviewed by two owners of a small engineer firm. They asked, "tell us where you see yourself in 5 years". I rambled for ~30 seconds about marrying my girlfriend and other personal details. I still remember their faces; super awkward, and then they slowly clarified: "we meant professionally" hahaha. It ended up fine in the end, but I feel like there's probably some missing education on social culture of interviewing somewhere and you just have to have those experiences at some point to understand.
Comment · 6 months ago
I went to school with a guy that dropped a $100k-200k VNA at Apple during an internship. He didn't get a full-time offer despite their investment :P
Comment · 8 months ago
I was looking at running [versitygw](https://github.com/versity/versitygw) but filestash looks pretty sweet! Any chance you're familiar with Versity and how the S3 proxy may differ?
Comment · 1 year ago
Is Govee the down-cone style? Or are there also others doing that? There's been a couple of houses that have this and I wasn't sure what they are using, but it's the only one that I would consider doing whole house exterior. Many others look too sharp.
Comment · 1 year ago
Seems fairly simple to have a smart contract do a DNS validation to unlock funds. For example, someone sends to a contract "$1 to example.com". Then the URL owner publishes either a TXT file or DNS record that has a list of crypto wallet addresses. Contract then forwards the payments. You could even make the keys just the ISO codes for each currency.

It's as good of a proof for TLS certs, but it's susceptible to DNS hijacking, etc. Make the contract immutable to meet tornado.cash standard. There are already oracles for DNS lookups so this contract might already exist somewhere.

Add in a couple of features:

1. Allow tracking per domain so publishers can know that there is a demand to set it up on their end.

2. Allow refunds in case the publisher never opens it up.

Comment · 1 year ago
There are options, however just saying anything is going to get you labeled as a shill heh. You're right that any new crypto is indistinguishable, but that is part of the risk in trying to outlast the rest. Some crypto that have survived should be worth more for hitting some of these milestones, but unfortunately that still isn't reflected in the top 10/20/100 because people are so desperate they throw cash at anything that moves.

The convenience of the scamming is partly why it _is_ a solution to this problem: people can transfer value as fast as they desire, and it works. There is also just a problem off on and off-boarding where you get hit by Visa/Mastercard level of fees. So is it really solving the problem at that point?

One area I would like to see is some kind of governed/regulated profit sharing. Basically giving your votes to content/production and this puts it on the books for some fraction of payment. You get X shares to distribute to content regularly. It would also be helpful if our government would provide support for independent producers where there's a clear trackable benefit (e.g. open source libraries that a ton of people rely on and a business can say "yes I need this, help them keep doing it").

Comment · 3 years ago
Would you consider this a competitive replacement of Busybox? Curious if you've compared, since they also take liberty in cutting out uncommon functionality.
Comment · 3 years ago
I've never paid a real estate lawyer anywhere near what an agent demands for a fee.

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton