godisdad

exorbitant costs of rail construction in the United States mean that many such projects never get off the drawing board. In cities such as Austin, Atlanta, New York, and Philadelphia, enormous projected costs have resulted in rail projects being canceled or scaled back significantly.7 And it’s not only rail infrastructure. Road tunnels, highway bridges, and roadways are all more expensive to build in the United States than in major European countries.8 A study by economists Zach Liscow and Leah Brooks found that the inflation-adjusted cost of American highway construction tripled between the 1960s and the 1980s

Copy aside I think the approach is similar to https://turbopuffer.com/blog/object-storage-queue

The quiet improvements to S3 over the last 3 years like conditional puts unlocked a lot of use cases not previously feasible

Overview DBM (Database Manager) is a concept of libraries to store an associative array on a permanent storage. In other words, DBM allows an application program to store key-value pairs in a file and reuse them later. Each of keys and values is a string or a sequence of bytes. The key of each record must be unique within the database and a value is associated to it. You can retrieve a stored record with its key very quickly. Thanks to simple structure of DBM, its performance can be extremely high.

Tkrzw is a C++ library implementing DBM with various algorithms. It features high degrees of performance, concurrency, scalability and durability.

You can’t post the GTA “here we go again” gif in HN or I would

The vagaries of the dual licensing discourages a lot of teams working on commercial projects from kicking the tires on CodeQL and generally hinders adoption for private projects as well: are there any plans to change the licensing in the future?

The Jenkins vitriol is also puzzling to me, I think the security model, reliability and backup/restore story has gotten seismically better in the intervening decade people wrote it off

Respectfully, neither of these docs strike me as really sufficient to debug live running systems in the critical path for paying users. The first seems to be related to the inner development loop and local the second is again how to attach gdb to debug something in a controlled environment

Crash reporting, telemetry, useful queuing/saturation measures or a Rosetta Stone of “we look at X today in system and app level telemetry, in the <unikernel system> world we look at Y (or don’t need X for reason Z) would be more in the spirit of parity

Systems are often somewhat “hands off” in more change control sensitive environments too, these guides presume full access, line of sight connectivity and a expert operator which are three unsafe assumptions in larger production systems IMO

Looking forward to the AI enabled subscription version

I was able to setup SigNoz on the order of five minutes to view traces in my Dagger builds locally just by exporting the right env vars — it was nice to not have to run and orchestrate three+ tools together

> As JSON is such an important part of the web nowadays, it deserves to be treated with more care.

There is a case to be made here but Corba, SOAP and XML-RPC likely looked similarly sticky and eternal in the past

MongoDB Atlas is a multi-cloud developer data platform that simplifies how developers work with data.

We’re hiring a Site Reliability Engineer to join our Developer Infrastructure team. Our team supports the broader SRE organization by:

- Building and maintaining container images, OS packages, and infrastructure tooling - Creating self-service Terraform workflows - Handling cloud resource provisioning across AWS, GCP, and Azure

This is a full-time, remote role for candidates based in the four continental US timezones. Prior familiarity with Bazel, Go, Terraform, Argo workflows and GitHub Actions would be helpful.

If you’re interested, apply at https://www.mongodb.com/careers/jobs/6711510

MongoDB | Site Reliability Engineer | Full-time | Remote (US-based)

MongoDB Atlas is a multi-cloud developer data platform that simplifies how developers work with data.

We’re hiring a Site Reliability Engineer to join our Developer Infrastructure team. Our team supports the broader SRE organization by:

- Building and maintaining container images, OS packages, and infrastructure tooling - Managing internal Terraform workflows - Handling cloud resource provisioning across AWS, GCP, and Azure

This is a full-time, remote role for candidates based in the US. Prior familiarity with bazel, Go, Terraform, Argo and GitHub Actions would be helpful.

If you’re interested, apply at https://www.mongodb.com/careers/jobs/6168913 (ignore JD and mention your interest in the "SRE DevInfra" team in your cover letter/note and the talent partner will route it to the team)

There are other roles in the same organization listed here if you search for 'New York': https://www.mongodb.com/company/careers/teams/engineering

Kaiser in Oakland is without exaggeration the best medical care I’ve ever experienced. Aligning incentives between the care provider and the insurer, vertically integrating care and putting it all on a walkable campus (even with a pharmacy!!) was such an efficient and pleasant process.

I was never healthier. The other Kaisers in Oregon aren’t geographically collocated so there’s less of an effect and they’re far away from me so I don’t use them anymore, sadly

OP here.

I visited their clinics for my daughter several times when she was a toddler for ear aches and other ailments— I found the experience refreshing: instant online booking, no BS registration and online communication with staff was seamless. Very sad to see them go so abruptly.

Up until this morning when I was told they were gone, I had no idea they were YC or otherwise VC funded. Just came here to pour one out for a genuinely helpful and pleasant medical company.

Modulo things like compliance where all changes must be traced back to an auditable review, abandoning the assumption that Pull Requests are necessary to keep the default branch working is an experiment everyone should try.

Having worked on projects where pairing replaced PRs it's virtually unheard of in many shops to trust individuals to this level. But it works just fine in many circumstances because for larger changes you eventually end up using PRs as something more than a rubber stamp.

It is both.

The story of Lookout Records being basically kept afloat by selling Kerplunk their first album after they left and blew up is also tragic/hilarious

If the post were C++ focused instead of Rust would it make the same, more or less sense?

A systems language with a high cognitive barrier to entry, compile times and less than a decade of wide adoption can’t reasonably be expected to compete with something like Rails in terms of approachability

Shoutout to the GCP apologists: your faith in the face of overwhelming evidence contradicting the stability of the offering will be remembered heroically by history

Five clicks in to a visualization tool’s website I don’t see any diagrams or screenshots makes it challenging to want to kick the tires on this

It's about.... time

No.

Dope. Reminds me of far.exe