This is going to read like I'm shilling but: I was so impressed with Bose QC headphones that i stocked up and gave out 7 pairs to my closest friends and family this year for christmas
Thee noise cancellation was unmatched several years ago. I picked up mine because we were spending hours in the data center. Suddenly we could work and take calls in that hell. I still have those, but the AirPods have taken their place on flights. It’s just less to bring with me.
I'm with you on everything except "it was terrible" :) The only problem with 300+ping, at the time, was when those damn LPBs connected
In-match comms between teammates is my favorite memory. The ease of voice chat in MP games since then is underappreciated. Feeling like a dinosaur writing this but...
... before discord/mumble/ventrilo/teamspeak, the only choice to gain an edge in competitive online gaming was to be physically in the same space or team text chat binds. The binds would cover 10-15 common situations so we could communicate while playing.. In hindsight, when things got hectic, reading the team chat text spam hindered us more than helped us. But we had good intentions with those binds and boy we had a blast competing. And let's be real, that's all that really matters.
Better? Hard to say. Different? Yes. Worth evaluating? Absolutely. Using it for 30 minutes will answer your question better than any reply here. I think you'll answer your own question quickly.
I've been coding seriously for about 15 years. No single tool has changed how I code more than claude code and I'm including non-"AI" tooling/services. This sounds like I'm shilling but I am not affiliated. It's played a large part in injecting my passion back into building stuff.
I read a lot of the posts at the little blog here and, uh, every single one sounds like a complete amateur making a cloud configuration mistake. I haven't found one that is the provider's fault or the fault of "serverless"
I would be embarrassed to put my name on these posts admitting I can't handle my configs while blaming everyone but myself.
Serverless isn't a horror, serverlesshorrors poster. You are the horror. You suck at architecting efficient & secure systems using this technology, you suck at handling cloud spend, and you suck at taking responsibility when your "bug" causes a 10,000x discrepancy between your expected cost and your actual bill.
Just because you don't understand it doesn't mean it sucks
You're not wrong about cloud configuration mistakes, but a tool that lets you increase costs 10000x (without even letting you set a safety) is a hell of a chainsaw.
I'm more worried about the overconfident SRE that doesn't stay up at night worrying about these.
Consider this analogy: Instead of using a root command shell, it is wise to use an account with appropriately restricted capabilities, to limit the downsides of mistakes. Cloud services support the notion of access control, but not the notion of network resource usage limits. It's an architectural flaw.
Or do you always log in as root, like a real man, relying purely on your experience and competence to avoid fat-finger mistakes?
That being said, the cloud providers could do a better job explaining to new/naive users that great power comes with great responsibility and there is no hand holding. Someone might be more hesitant to willy nilly spin up something if a wizard estimates that the maximum cost could be $X per month.
reply