bmilleare

I remember having to do this every few hours 25 years ago when working at a store part-time as a student.

Having networked telemetry seems like a good idea, just not sure why they would need remote control too - that seems far more dangerous than necessary.

I'm not sure why the article picks these 3 options as if that's it.

An RPC API can happily exist over plain old HTTP/1 (no protobuf required) and it also doesn't mention the primary benefit of RPC over REST/RESTish (IMO) - and that's the ability to stack multiple RPC calls into a single request.

De-anonymization would take monitoring over a period of time, but it could definitely work. Take this scenario for example: a person of interest is in the area of New York on Jan 1. On Jan 4 they travel to the UK. On Jan 7 they travel to Germany. On Jan 21 they travel back to the US.

The list of suspects would be fairly small when US officials cross-check individuals that travelled US-UK on Jan 4 and Germany-US on Jan 21.

For the previous 20 years I had no real routine other than wake>commute>work or wake>work if wfh, but over the last 2 years I've been more focused on my health. Every weekday I get up around 06:00 and am at the pool by 06:40. I swim 1500m then have a 15min sauna and 4min cold plunge. Normally I'm back at my desk by around 08:20. I drink 1L of water with electrolytes while at the pool and then have a light breakfast and espresso when I get home.

I'm in better shape than I was throughout my 30s, have more muscle, better posture and generally feel more energetic and alert through the day.

While at the pool I listen to Audible books (wearing Shokz), so get through a new book every couple of weeks also.

I also hit the CloudFlare verification merry-go-round several times per day using Ubuntu / Chrome.

Putting the central in decentral since '22.

I had no idea this was a thing. How cold are we talking for this to be something that happens often?

Automating such a narrow edge-case seems totally pointless. A much more likely scenario is that your battery dies while you're out, in which case you're still screwed.

A better tried-and-tested real world solution that covers all scenarios is a simple key safe.

While the breaking change in a Mongoid minor release is particularly egregious, let's face it - the real failure here is lack of sufficient tests. I would be very surprised if this was the only place they used or() in their app so it should have made their test suite light up like a Christmas tree.

It would be more interesting to see those numbers in square footage and not straight counts. I would expect the majority of the 'empty' homes are the £10M+ ones in Knightsbridge, Chelsea, Kensington etc.

We use wkhtmltopdf on AWS Lambda and have had zero issues in production for the last ~2 years. We're generating internal owned documents (invoices, letters, paged forms, etc) so I wouldn't necessarily trust it with untested input HTML but it really has been bulletproof for our use-case.

At some point we'll likely move to chrome/puppeteer but in most of our tests the templates required modifications to mimic the existing PDFs so it's something we've been putting off.

NZ is there if you make your browser viewport big enough.

The benefit of something like Ring is that criminals will know what they are and that somebody has very likely just been alerted to their presence.

I speak from experience when I say they tend not to care about traditional 'dumb' cameras as, generally, nobody is going to be watching them until after the act.

> 10) understand that “good enough” sometimes is all you need (still try to fix it later :) )

This is something most CS grads don't really grasp immediately, but in the real World business and time constraints normally trump perfection.

Technical debt is fine as long as it's fully understood and managed properly.

The bigger issue is insurance. If you have stuff stolen and there's no sign of forced entry (home or vehicle) then your insurance company will likely be asking questions about how exactly the thieves gained access.

Exactly this. If sticker cost is your leading factor then these kinds of services can seem crazy, but when you factor in the real cost of self-hosting then it quickly becomes a no-brainer.

We're more interested in what happens when things break (and who's responsibility it is) than minor cost savings in calm waters.

A tonne of our (enterprise-ey) customers had such trouble trying to integrate into our S3 flow that we started launching VPS for each that abstracted it away into simple SFTP upload/download, which they were used to.

Although this is much more expensive than Lightsail, the man hours saved will make it worthwhile.

Money laundering will likely be the main use case of this app.

It's really interesting to see $100M+ exits that have resulted in trivial sums for founders and early employees after multiple rounds of dilution and/or VCs with preferred shares taking home the spoils.

I have always optimised for salary although I can see why a young engineer with no dependants might opt for the gamble of a big payday instead, likely without really understanding their true chances.

Too much industry focus is heaped on 'unicorns' when these kind of companies really are a drop in the ocean.

As others have pointed out, connecting to RDS from Lambda is actually pretty trivial by having them run in the same VPC. We actually came up against an issue where our Lambda function needed access to RDS but also to the outside World which meant some extra hurdles to jump [1] but overall our experience with Lambda has been a positive one.

I don't think we'll be considering a fully serverless architecture anytime soon due to cold-start times, but it's awesome for anything outside of the user request/response loop or internal microservices where response time is perhaps not such of a problem.

[1] https://aws.amazon.com/premiumsupport/knowledge-center/inter...

I submitted this post back in 2015 and it's no less impressive now - I'd love to see some updated analysis now that automated trading is even more prevalent in btc.

...and yes I clearly should have written this in machine code and deployed to a Gibson. Thanks for the tips.

No I still have the code, just no commit history.

Just to clarify - I wasn't paying full instance prices. I was using spot instances which worked out around $7/mo each at the time.

10/10, would agree again.

That's from the AWS EC2 console

Oh hai, OP here.

Firstly - my first HN front-page, yay!

So, this was a little unexpected to say the least. As has already been pointed out, this post was written about 14 months ago now, and yes details are a little light. I'll ignore the usual HN hospitality and answer a couple of the more pressing questions:

1. this was a very early MVP at the time, it was not a production-ready piece of enterprise software, so no it was not built for out and out speed in the first instance.

2. yes there were probably much better options than c1.medium on AWS, but see (1).

3. yes it uses off-the-shelf libs, see (1).

4. no the website is not meant to work, I never got round to finishing it up, see (1).

5. sadly, I don't have the original git commit to reference (I was at my private repo limit and removed it) but yes, it was essentially a simple 1-line optimisation. IIRC it was something being evaluated in a loop that didn't need to be. Very mundane indeed. No tools used to identify it, I just knew it was being called a lot.

Ironically, the post was meant as a linkbait to drum up a bit of interest in the tool and see if it was worth developing (hence the tabloid title). It didn't get any traction and so the project kinda halted.

This looks cool. Any plans to add support for posted HTML (as opposed to a target URL) too?

The reason I ask is that sometimes I need to screenshot pages that I've crawled - but you might not see exactly the same page I did at the time.

Out of curiosity, how much did you buy at $4/BTC?