🔥The 9th Round of Easy Loan, Earn $40 Reward is in progress❗️ ⏰ Promotion Period: January 15th - Feburary 15th, 2025 👉 Register now and check more details at gate.io/campaigns/358

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.

The problem with supply chain security in a nutshell.

This is obviously stupid (and not even a timely stupid prediction anymore?), but the most amusing thing to me is how game studies has been warning about 'playbour' for nearly 20 years now. five.fibreculturejournal.org/fcj-025-precar…

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 github.com/boyter/cs and view here asciinema.org/a/589640

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)

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

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 did not see this coming newsroom.squarespace.com/blog/googledom…

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

Corey Quinn Google Cloud 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??

One of the things I'm most proud of at Rewind 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? 👇

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

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*.

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

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

Simone Margaritelli