HN user

thruflo22

173 karma

8cc6b7ca17a8fe1af84baca379111e91abe4642806aefbd3f8aa1d74a52f799a

Posts4
Comments78
View on HN

Electric DB | London and Istria | Remote | Full time and part time | https://electricdb.net

Electric DB is developing a next generation global database.

We’re hiring product engineers, database engineers and a developer advocate.

Our challenge is (1) to deliver a world class developer experience for a managed geo-distributed database service whilst (2) pushing the CAP theorem and latency <> consistency trade-offs to their limits.

If you care about both (or specialise in one and are intrigued by the other), have relevant craft skills and the mindset to join an early stage startup then we’d love to chat.

I’m the CEO. Email me on thruflo at.

I think to keep it hosted will require tending to the bitrot. We don’t know how the web and computers will change but we do know they will change.

So a succession of people (or, later, robots) need to be incentivised and resourced to maintain it.

A foundation is one idea. But I quite like a viral clause in your will. So, to inherit, your heir needs to (a) maintain your digital legacy and (b) put an equivalent clause in their will, and so on. Maybe it depends on the value of the inheritance but it might be a way to secure a few generations.

Then you could also stipulate that they should do anything they can to use the resources of their time to further secure the digital legacy. You could also make the responsibility always joint and several across all children / heirs.

This is very interesting and it strikes me that things could be more balanced if pro-rata rights decayed if the investor is not active.

So similar to vesting for rights — a founder / employee needs to continue to be active to continue to vest. Ideally an investor could continue to be active to continue to exercise pro-rata.

It’s pretty hard to enforce / codify “active” for an investor though and could just result in time wasting by pretending to be involved helpful when just coasting. Was that intro genuine or just designed to protect the pro-rata?

RTK GPS is used as a second factor to vision in these machines. It’s just not good enough to target with as a sole / primary factor in the real world though. Bit of drift and whoops, $30,000 of crop gone.

Lasers are not used because they’re expensive and dangerous. And Co2 lasers (as per the machine in the article) are powerful but super fragile.

Water shooting around at high pressure is in no way efficient or easy to handle.

Compressed light is the technology that’s actually going to be used for precision weeding. It has the speed, power and simplicity of lasers, without the cost and danger: https://www.linkedin.com/feed/update/activity:67899797724715...

Supabase’s realtime library consumes the logical WAL and provides a Phoenix channel + JavaScript API to subscribe to matching events from it: https://github.com/supabase/realtime

Under the hood, the core implementation was copied (with credit / attribution) from: https://github.com/cainophile/cainophile

I happened to do a similar thing but I adapted cainophile into an Elixir “OffBroadway” producer: https://github.com/integratedb/integrate/blob/main/lib/integ...

These approaches rely on acking the WAL to confirm data has been processed. It’s simpler than running Debezium / Kafka for “zookept” CDC. However, they are “at least once” at best and it’s easy to shoot yourself in the foot so think twice before relying on this kind of thing for a real application.

Materialize is nice — TAIL is a lovely abstraction and their data ingest uses Debezium under the hood. That said, I believe their Postgres binlog source is still alpha / under active community dev.

GitHub is a “social coding” platform that provides collaboration features (access control, issues, etc) on top of Git.

This is a social coding tool that provides collaboration features on top of Git.

It provides a desktop app because it’s peer to peer. That’s an advantage over a web UI for developers looking to avoid a dependency on a centralised third party.

You are free to continue to play in walled gardens but this is very much an alternative to that.

I moved recently from the UK, where my home and office both had fiber, to live in a tiny picturesque village in the Istrian hills in Croatia.

Initially, my 4g router was getting a signal strength of -110 to -120db, corresponding to two bars and zoom video not working. Spent €90 on an outdoor aerial. Plugged it into the router. Signal now averages -85, four to five bars on the router, zero issues with video calls.

My point being: there’s more than one way to skin a cat and you can often improve your mobile signal if you want to.

Yeah, CRUD is a solved problem but you still have to do it.

Mapping state to the database is to web dev what applying paint to the canvas is to painting. It’s how you do it that counts. Saying otherwise is overly reductionist.

Frameworks exist that abstract CRUD away. But you end up sacrificing UX and / or flexibility.

Looked into this in detail recently.

There is no volume of applications atm but it is possible.

Can connect you to a colleague who did the research —- thruflo at gmail.

I’m not sure of the relative timing but the Google policy of “we support the last two major releases of the main browsers” also really helped.

As a web developer at the time, I could put that in my proposals, saying “it’s the standard Google browser support policy”. At which point clients signed off on not needing legacy browser support.

Rebrand as a data scientist.

Data science is eating the world. Everyone wants data scientists.

You’re a microbiologist. It’s hugely credible that you’ve done some crazy data crunching for your science work. Spin that into an increasing interest in the pure data science.

Voila, you’re writing python for a living at the top of the market with a hugely valued differentiated skill set.

Firebase hosting is good for static hosting with server side functions.

For a real backend, Phoenix (Elixir) is the new Rails / Django. Google App Engine Elixir is a good place to deploy it.