nick0garvey

Awesome. If you are not in touch with Maker Nexus (based out of Sunnyvale) already, please reach out! Would love to put you in touch with the administrators there on what they learned about successfully running a non-profit maker space.

The final Greenhouse link doesn't work in this listing

> Pipelined replication: the sequencer assigns a sequence number immediately and ships the event to replicas in parallel. Matching doesn't wait for the replicas to acknowledge.

How is this avoiding data loss if the lead sequencer goes down after acking but without the replica receiving the write?

It says "PAID ONLY BY A RELATED FOR-PROFIT", which looks to be the Mozilla Corporation. Donations are not directly paying the CEO, although I agree more of the profits from the Corporation could flow into the non-profit.

Hold the lock and write a row with timestamp at the time you read.

That row indicates you are the one processing the data and no one else should. When reading, abort the read if someone else wrote that row first.

When you are finished processing, hold the lock and update the row you added before to indicate processing is complete.

The timestamp can be used to timeout the request.

I'm not quite following. His argument appears to be: The replication system requires a backwards seek, Postgres does not support that operation, things break when that operation is attempted.

I don't understand why replication would need a backwards seek - are you saying it doesn't and he is mistaken on that?

I took a Udacity class by Norvig [1] and my abilities as a programmer clearly were improved afterward.

His code here demonstrates why. It is both shorter and much easier to understand than anything the LLMs generated. It is not always as efficient as the LLMs (who often skip the third loop by calculating the last factor), but it is definitely the code I would prefer to work with in most situations.

[1] https://www.udacity.com/course/design-of-computer-programs--...

Morphy, one of the greatest players of all time, is famous for this.

"The ability to play chess is the sign of a gentleman. The ability to play chess well is the sign of a wasted life."

There is also the deleteRecords API specifically for this. It's easier than the retention shrink -> increase dance, as it is a single API call and retention does not kick in immediately. The log segment must roll for retention to apply, either due to size or time.

https://kafka.apache.org/11/javadoc/org/apache/kafka/clients...

I use this for everything at my house. I haven't add any issues.

I use NetworkX to build the graphs and Gephi to visualize them. No need to pick a single tool.

I also started to write a finite state machine for part 2 but found it too tedious to craft by hand. How did you do it?

His book "The Datacenter as a Computer: An Introduction to the Design of Warehouse-Scale Machines" was immensely valuable to me as I moved into datacenter management as a new-grad. RIP.

https://research.google/pubs/pub41606/

This isn't unreasonable. ML workloads benefit from more computational time per request. Lower QPS = better results.

Can someone explain why the "no free lunch theorem" does not cause problems here?

https://en.wikipedia.org/wiki/No_free_lunch_theorem

A lot of people in this thread point at motivation or mental health issues. The issue is likely not so complicated.

You have forgotten how to focus. We live in a world where we are constantly distracted. This is forced on us. The apps we use compete over our attention, our workplace expects quick replies over Slack, our free time is always accompanied by a smart phone pushing us notifications.

These effects are getting stronger. Technology evolves new attention taking techniques. Our remote work culture expects faster replies as you are, in theory, always at your desk.

You can address this focus deficiency, but it isn't easy. Put your phone always on Do Not Disturb. Use site blocking extensions to limit time wasters (yes, even Hacker News). Stop being so responsive at work.

The first few weeks will hurt. You won't instantly be able to focus, and you will feel less productive due to the lower response time. But after some time, you will be able to do work others cannot. You can complete the big work you are struggling to right now. Relearn how to focus.

If Solano county votes this down, it dies. They need to sell it this way.

They show the benchmarks in the original post, a few pages down

Most of the attacks I see on Nordic devices are power based attacks, where cutting the power for a brief instant causes protection instructions not to run.

This one is entirely different, and attacks the initialization code directly. This code has no restrictions on its ability to access memory, allowing a full dump.

Great method.

You say "don't suggest to buy some old Dell Optiplex from eBay" but I did exactly this.

I spent $43.97 (which included shipping) for the Optiplex, added a 2 port NIC for $16.37, and it's been running my house great since then.

Aluminum alloys are also generally stronger than magnesium alloys.

Airplanes fit a more people into the same space than they used to.

I wouldn't say this is the most boring. In Python it is certainly an empty file.

It was interesting to see the author work through the major obstacles one by one when writing a quine. Glad they didn't take the actual boring route!

I don't agree. A subset of high performance applications in a datacenter can use a new protocol while still supporting TCP for other applications. I'm not saying this is easy, or even worth it, but it isn't all or nothing.

This took me 14:02 on the first try. Definitely got faster as time went on but I found myself getting stuck on a few squares for no good reason. Starting from the destination and working toward the source helped.

Dating has a large emotional aspect. Using heavyweight management software for this kind of thing is ridiculous. If you need CRM to remind yourself of the emotional impact you had on a date, then some part of this process has gone horribly wrong.

I use the Run window for this same thing

Cloud services do go down and it's out of your control when they do. If something must work, you need redundancy.

Kafka is often used for financial applications that must not miss events, so having a backup buffer is a reasonable strategy for those use cases. Things like tracking data is likely not worth backing up due to high data volume and low external visibility when data is dropped.

Interesting one liner but would like to see the colors it generates

I make heavy use of Soulver. Really quick way to do some quick calculations with good unit conversion.

e.g. I can write hosts = 100; disk_space_used = 10MiB/s * hosts * 3 days as TiB

And it works as expected. Powerful tool when doing capacity planning or other load calculations.