@evilsocket

Its probably still to complex, but someone needs to make a way to serve a baseload of predictable traffic to some always on computer (container/vm) while using lambda for traffic spikes. And make that seamless to users and developers.

Nothing beats lambda for handling spikes in traffic, and unpredictable usage. There’s always going to be the crossover point where you have enough predictable traffic to pay by the hour, than by the request (+ms).

The equivalent of a video game requiring you do the tutorial to learn how to look with a mouse and jump.

I’ve been using this, it’s pretty great.

You will NEVER know more about your code than you do in that interval. Which is why that is the moment you are best equipped to find bugs, if you reliably instrument and check your observability. After that, the cost of finding and fixing bugs goes up *exponentially*.

The Rust community appears to be discovering the security implications of proc macros and build scripts in unverified 3rd party crates

One of the things I'm most proud of at @RewindAI is our speed of execution: - We deploy code to production 45 times per week (that's 5.3 times/week/person) - For each pull request, the average development time is 0.89 days and review time is 1.0 days How do we achieve this? 👇

When I say this is an unexpected move, I mean initially purchased https://t.co/2iNxUNjvuO using Google Domains for the irony factor in September 2018. 😂

@QuinnyPig @googlecloud Why on Earth would anyone choose Google Cloud, going forward? Especially if it’s a decision maker whose side project was using Google Domains. Show me another cloud provider that hands off one part of their infra to another company because… oh wait, why, really??

I’m eagerly awaiting the Very Serious Takes that @GoogleCloud isn’t a risky bet. If my cloud provider tells me that for the domain registration part I need to go talk to Squarespace, I’m picking a different cloud because I don’t want to get fired.

...I did not see this coming https://t.co/uJGz2l5x6x

Google doesn't kill all its products, only the ones you love.

We're excited to announce our plan to open source Zed... on Zed! Zed has always been more than just an editor. We're building a communication platform for software engineers, and we're going to use this platform to open source itself! (1/6)

I fully understand this now. If you haven’t yet, spend a few weeks with rust, it’s worth it.

My team also worked on a new library format: mergeable libraries. Mergeable libraries combine the benefits of static and dynamic libraries, providing the best performance without sacrificing development velocity. (1/n)

Finally got around to finishing a command line search tool I have been working on for literally years at this point. You can download here https://t.co/7TRTiyGZpb and view here

The problem with supply chain security in a nutshell.

Understanding how much things cost, and what your normal spend looks like is a critical feedback loop for building cloud software. Services tend to be priced to suit certain types of workloads (that it was designed for). The wrong workload can be slower and more expensive.