rvillanueva

Relay does a good job of automatically partitioning money, though you still need to manually execute external payments. Gives you a little extra interest on money allocated for taxes too

https://relayfi.com/

I worked at a company that did interactive retail signage and wrote the platform to remotely deploy software to the screens. Can confirm it was a giant pain in the ass. A couple random thoughts:

1) Internet access was extremely unreliable on site, as was our ability to get useful assistance from retail staff. Queueing inbound and outbound signals was key, as was locally storing any content.

2) Our primary customer was non-technical marketing/creative folks. They bought us because it allowed them to deploy novel signage formats without knowing how to code. (In case that’s a useful pain point to pursue.)

Hope that’s helpful!

Millions of years of evolution has trained the biological LLM in our brains to be good at fine tuning those concepts.

That’s the second of two items he lists. The first is: “1. it could easily break in a future update to the app”

“Oh man the guy who made the Space Exploration mod is gonna be pissed they’re copying him”

“Oh wait it’s the same guy”

Like others here are saying, you can never be 100% sure. But that doesn’t mean there’s nothing you can do.

If you’re worried about the impact to your broader organization (which is what most of the sophisticated threats tend to target), you should think about risk mitigation through the Swiss Cheese defense model. Each system is inevitably going to have holes, but layering them on top of one another will incrementally improve your coverage.

For instance:

- Your team should be trained about phishing attacks. But inevitably some will get through, so…

- You should implement 2FA in case a password is compromised. But a threat actor may be able to capture a 2FA-passed SSO session token, so…

- Production access should be limited to a small number of individuals. But even they might get compromised, so…

- You should programmatically rotate credentials to make old leaked credentials useless. But a newer one might be captured, so…

- Data should be sufficiently encrypted at rest and in transit, and…

- Your team should have an incident management system and culture in place to quickly respond to customer reported incidents and escalate it to the right level and…

- Audit logs should be tracked to understand the blast radius in case of compromise - and so forth

When you look at incidents like CircleCI and LastPass, a good security organization will understand that there was more than just one point of failure and should talk in detail about how they are shoring up each level.

The joy of a whodunit is being given just enough clues to feel like we could have solved it ourselves by the end. If the Cassandra/Helen twist had been the reveal, I would agree it felt like cheating. But because it's halfway through, it just becomes another layer of clues given to us so that we can figure out, along with Leblanc, that the real twist is that this entire film is about how stupid and simple everything has been all along.

I spent a month trying to get Elastic Beanstalk to work elegantly and it was still a slog understanding failed deploys and managing the nuances of networking and the headache of waiting for the system to get to a manageable state.

We ended up switching to https://render.com and I got everything I needed spun up in 3 days. You don’t have the same access to underlying resources in AWS but you get everything EB is supposed to do but faster and more user-friendly. It is much more actively maintained than Heroku’s current zombie state.