• 0 Posts
  • 878 Comments
Joined 3 years ago
cake
Cake day: July 3rd, 2023

help-circle

  • As a native speaker, I would say “Personally, I think” is pretty redundant, though I wouldn’t really bat an eye if someone said it, either. “Personally…to me” is indeed very redundant and is something that would stick out to a lot of people.

    As for “bad English”, I agree. The commenter is really reaching with that one.





  • Chess is a lifelong study, and not something anyone truly “masters”.

    If you are interested in getting better, I would suggest finding local chess clubs in your area and joining one. There will no doubt be strong players in the club that can help you get started and give you a direction.

    I can recommend the classic book Chess Fundamentals by Capablanca as a great introduction to basic chess principles and ideas. It was one of the first chess books I ever read and got me started.

    Beyond that, I think there’s a lot of value in playing with other people in person and studying your games. You learn a lot that way. Online chess is fun, but honestly, in my experience, not very instructive at lower ratings.




  • Deadlocks aren’t generally too much of an issue with an MVCC DB like Postgres (though it certainly can happen if you use explicit locks and such), but yeah ultimately it’s all about the kind of workload we’re talking about. I honestly think of it much less like a database and more like a high-performance synchronization mechanism that can cross process boundaries. There’s many times where you want to coordinate the behavior of many independent processes (like horizontally-scaled services), such as rate-limiting your requests to an external service. Implementing a distributed rate-limiting algorithm with a RDBMS is a pretty poor choice, because the data used for any synchronization is ephemeral, unimportant, and short-lived (and this, ACID guarantees are pretty irrelevant), and you would incur a lot of contention overhead for shared resources. You might even get bottlenecks that prevent you from achieving the rate you’re trying to limit yourself to. Something like Valkey gives you simple, fast atomic writes with built-in TTL mechanisms, which is perfect for a rate-limiting system. There are many other examples like this where it makes a lot of sense.

    Or consider even something incredibly simple like, I dunno, a realtime user counter. Valkey has an atomic primitive operation for this built-in (INCR). With an RDBMS, this is not trivial as you scale up the number of clients, because either you have to deal with a ton of row-level contention (if the counter is stored in a single row that gets updated), or you end up hammering your disk with increasingly large aggregate operations (if there’s a row-per-user and the total is computed across them, somehow).

    As I said, it’s really just very different workloads where they are valuable.


  • I’m not sure what you mean by “standard DB queue” (perhaps you mean a message queue, I guess?), but yeah Redis (or really, Valkey, now, since Redis tried to change license on everyone) is a very important tool in the toolbox for system design. In-memory databases trade persistence guarantees for raw throughput, and are very well-suited for different workloads than a traditional database is. It’s great for caching, rate-limiting, realtime analytics, leaderboards… Basically anything with ephemeral data or data that can easily be reconstructed from some other source of truth. It’s an optimization tool that can significantly reduce the load on your primary application database for certain workloads (and achieve higher throughput).


  • He has certainly revealed himself to be a shitty person, but Shape of You is actually a pretty good concept for a song. It’s essentially a song about body acceptance created in an era where people (especially women) face constant, coercive pressure to meet impossible, idealized beauty standards. That’s why it was such a popular song. I know a lot of people who struggle with that topic, and the song really resonated with them.

    It’s not like he even wrote the song, either. Pop stars almost never write their own music, and Shape of You is no exception.






  • I write everything the normal way, without LLMs.

    But yeah, it’s really depressing. People that used to be thinking about new ideas, tools, libraries, or methodologies now spend all of their time fiddling with prompts. It just sucks all of the air out of the room. People generate so much shit now that has no business existing, because there’s no friction in doing so. We fundamentally need to struggle with systems in order to understand them enough to make something better. Writing code was never the bottleneck, comprehension was. And struggling to understand is how one acquired comprehension. Now, things are so much worse. Not only are people not spending the necessary time to comprehend systems, but they are producing code at a rate far greater than anyone can comprehend. It’s an ever-increasing mountain of comprehension debt, and it’s poisoned the entire ecosystem. That’s what people just don’t get.



  • expr@programming.devtomemes@lemmy.world•Bad news
    link
    fedilink
    arrow-up
    3
    ·
    1 month ago

    Our interview process has the candidate implement a couple (extremely simplistic) API routes, with the specific approach left up to the candidate. It’s more about having something they can talk through and evolve than it is about us looking for any specific approach.

    Basically it exists as a way for us to have a starting point for talking about scalability topics, asking the candidate how they would evolve their implementation as we scale up the system. Does a pretty good job of giving us an idea of how they think through system design problems.


  • I was not talking about your specific lawsuit, or TLS.

    Companies trust other companies all the time, and it’s foundational to most all SLA/SLOs. Any time I’ve voiced concerns around how AI companies are using the data we are giving them (like giving them access to our codebase), it’s brushed off as “we have an agreement with them”. It’s just a load of hogwash. They can and will abuse all data they have access to, just as they have done thus far.

    In this particular case, we are talking about a data center, and it is not at all reasonable to assume that the data that flows to said data center is in any way protected, especially one run by Musk.