Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
ralferoo
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
13 ms
·
151.
▲
by
ralferoo
4mo ago
I'd argue that "correlation" is an accurate description of what you're doing with Gold codes - you're testing the known sequence of the output of a PRNG against the received signal, and only accepting it when the da
152.
▲
by
ralferoo
4mo ago
You should shout at your project managers then. The data in the ticket system should be considered important as it's the primary interface through which developers, QA and design share information.
153.
▲
by
ralferoo
4mo ago
Personal preference I guess, but to me all of those commit messages are way too wordy. I'd probably have: [PRJ-123] Refactor Foo out from Bar [PRJ-123] Include Foo data in BazClient [PRJ-456] Null-guard on Foo ID to avoid dat
154.
▲
by
ralferoo
4mo ago
I buy flights on credit card, and other one-off purchases like house and car insurance, and often my Costco purchases (because the credit card lives in a different wallet where I normally keep my membership card). My day-to-day wallet just
155.
▲
by
ralferoo
4mo ago
Most of the things I pay on the government website (except vehicle tax renewal), so basically tax, I've been pushed towards a one-off direct debit each time instead of a card payment.
156.
▲
by
ralferoo
4mo ago
Yeah, the thing that really concerns me about the other indices is the minimum free float in calculations, so not only will SpaceX appear in the index way too early, they'll be artificially giving it a massive boost, meaning that passi
157.
▲
by
ralferoo
4mo ago
The last part is easy to answer. Commit messages are solely for developers IMHO. The communication between developer and customer / product manager should be via the ticket system. That said, knowing the commit ID something is fixed in
158.
▲
by
ralferoo
4mo ago
Absolutely not. Commit messages should never be automatically passed through to the end-customer. I also worked in a place that tried it once and it was a disaster. Sure, a list of commit messages can be a useful start as a list of things t
159.
▲
by
ralferoo
4mo ago
That isn't true though. It's very easy to export your data from JIRA. From your board, go to the List tab, filter the items to whatever you want, and then click ... and you can export the data in various different formats. Exporti
160.
▲
by
ralferoo
4mo ago
You can trivially export your data from JIRA. If the parent experienced a situation where valuable information was lost because the instance was deactivated, that's not JIRA's fault.
161.
▲
by
ralferoo
4mo ago
Respectfully, I disagree. A good commit message to me is something like: [PRJ-123] Changed blah to foo Blah didn't handle the wangle flange properly in some cases, foo is a better fit for customer requirements. The "why" that
162.
▲
by
ralferoo
4mo ago
The real takeaway is that different projects have different requirements. In over 30 years of using source control, I've never once worked on something where it's useful to include the component (article calls it scope) in the des
163.
▲
by
ralferoo
4mo ago
Personally, I'm not a great fan of IPv6, but this says more about your provider than anything else. Assuming you mean for a VPS, the majority of providers provide IPv6, and a good many would advertise your IPv6 prefix and route it to y
164.
▲
by
ralferoo
4mo ago
> One question I would have about the comms theory is whether the amount of power being used would be reasonable for that use-case. Jamming tends to be much higher power than just communicating, but also GNSS signals are very low bandwid
165.
▲
by
ralferoo
4mo ago
Firstly, I think 0.15% might be significantly lowballing. Other commenters I've read trying to low ball it suggested 0.5%, which matches up with my calculations - this IPO is allegedly $1.5T on the total amount, and 25% is up for sale,
166.
▲
by
ralferoo
4mo ago
That would be true IF the stock was already being traded. All we have at the moment is just Elon saying "I think this is worth $1.5T, convincing a small subset of people to buy shares, and then because of this change, market following
167.
▲
by
ralferoo
4mo ago
https://archive.is/LE41W
168.
▲
by
ralferoo
4mo ago
I turned off "smart features" in the setting months ago, and I've never seen any of the things the author complains about.
169.
▲
by
ralferoo
4mo ago
Not sure if you're talking about cron or systemd, but cron definitely has that in /etc/cron.d where you can have arbitrary crontabs, or /etc/cron.{hourly|daily|weekly|monthly} where you can just place arbitrary scri
170.
▲
by
ralferoo
5mo ago
The more likely risk with a 6845 is creating a way out of spec vertical sync that can cause the monitor's frame flyback transformer to fail. Although how you describe the PET monitor's beam being "parked" suggests it
171.
▲
by
ralferoo
5mo ago
FWIW there's a good chance your fridge does more than that without you realising it if it's a fridge freezer. A lot of fridge freezers now have an anti-frost system that about once a week or so actually heats up the freezer so tha
172.
▲
by
ralferoo
5mo ago
https://archive.is/ILx0w
173.
▲
by
ralferoo
5mo ago
That policy itself seems wrong though. It seems to imply that anything someone claims about themselves on a personal blog doesn't need verification. People often have a vested interest to lie about themselves, and often people may not
174.
▲
by
ralferoo
5mo ago
I was surprised to see in Taiwan last year several instances of people walking into a cafe and leaving their phone on the table to indicate the table was occupied and then going up to the counter to order.
175.
▲
by
ralferoo
5mo ago
I answered this in another HN topic just the other day: https://news.ycombinator.com/item?id=48061098 But essentially, using UUID v7 you actually have less risk of collisions than with UUID v4. Because of the birthday parad
176.
▲
by
ralferoo
5mo ago
Something I use on my own distributed system (where I wanted 64-bit IDs), is use 32 bits for the time in seconds (with an epoch from 2020, so good until 2088), 8 bits for the device ID and 24 bits for a serial number (resets to 0 every time
177.
▲
by
ralferoo
5mo ago
I kind of addressed this in https://news.ycombinator.com/item?id=48060549 Actually, because the birthday paradox has k^2 as a term, this is actually less true than you might think. Having a time component actually reduces t
178.
▲
by
ralferoo
5mo ago
BTW I realised I didn't address why those bits are necessary - actually, while it might seem you are increasing randomness with more bits and so reducing the risk of collisions, that's not necessarily true. The old schemes generat
179.
▲
by
ralferoo
5mo ago
Yeah, in practice the 6 bits you lose aren't important. Redoing his calculations with 122 bits and a quadrillion generated IDs (that's a million billion), the probability of a collision is 9.4 x 10^-8 (or one in 10 million) using
180.
▲
by
ralferoo
5mo ago
It basically makes no odds, unless you consider applying a constant AND and constant OR operator complicated - as UUID v4 is just 122 random bits and 6 bits fixed. UUID v7 is a 48 bit timestamp, 74 random bits and 6 bits fixed. Sure, this i
More ›