harpiaharpyja

Or you know, you can read it and then evaluate your sense of what it's worth based on the actual content.

(Presumably you mean the guy affected by the decision?)

I think it's for the best to just accept that retaining control over your machine is just incompatible with the competitive online gaming, and that's fine. There is plenty of gaming to be had that isn't competitive, and/or isn't online.

And in fact there are many online games that are competitive not in the narrow sense used above, but in a more general sense where people don't cheat because they choose not to, usually because a sense of community does exist among players of such games.

To add to that, my advice is to look for LED lights where the AC-to-DC conversion is done by a power brick separate from the lights. Not only does that mean you can replace them separately, but generally these will be much more robust as the power electronics won't be as constrained by size.

I wish it caught on to have LED lights powered by a barrel jack DC plug like you have for most electronics. It would be a huge win for longevity. Sure it's not backwards compatible with fixtures designed for light bulbs, but the cases we're discussing here are complete light fixture replacements anyways... The fixture could have a barrel plug that you connect to an inexpensive commodity DC power brick which you then hide away in the ceiling.

It's funny how popular it is to take an extremely durable and long-lived light-generating technology and pair it with the cheapest short-lived power electronics.

Or to bring it back to the original context... Reducing volatility would be reducing the impact of bad weather on your harvest, absorbing volatility is finding someone to cover your losses. (presumably by giving up some profits on the good years. It's like a financial low pass filter)

With all the attention on the link between compression and intelligence lately it is neat to have this example of how creating a encoding scheme naturally allows you to create new (likely) never before seen flags.

Thanks, that was insightful.

Personally, I think the main legitimate use of the ticket pattern is when dealing with hardware. In which case your global hidden state is actually the physical world and can't be eliminated.

Otherwise, I think you have a good point.

Pastimes are in fact incredibly valuable. And it's possible the motivations that led to the creation of this artifact wasn't just all about the end product.

Maybe the Korean live stream map will depict it as a Korean territory

Exactly right? Why would anyone expect a competent security outfit to tell the reporters anything?

I've been introducing rust to our embedded projects at work for the past few years and I can really empathize with this.

The rust embedded ecosystem seems to have way too much focus on ownership and safe handling of peripherals. Exactly as you say there's not many of them, you're limited to what's in the hardware. These are not things that you are dynamically spinning up and tearing down dozens of instances all the time but the HALs I've seen all treat them that way. The result is a lot of abstraction that creates a ton of needless boilerplate.

I would rather these things just get out of the way and let me focus on building abstraction in the business logic where it's needed.

Except when it's that same someone else's money being spent.

This notion that `git rebase -i` is some scary unusual thing is totally alien to me. Doing some minor cleanup on local history with rebase is a *basic* operation that I would have thought everyone would be using regularly.

They didn't copy any hold/hover states which is too bad, those are an integral part of a button IMO

It doesn't have to be mutually exclusive.

I find the "EMBEDDED MALWARE DESTROYED MONTHS OF WORK" issue opened on the jqwik repo to be baffling. Do they not use source control? And if not, what are they doing on GitHub

Compare is broken, always produces "not found"

As a customer of DropBox since ~2011 I would say they've been an outstanding success.

Maybe it's time we redefine what success means.

I don't think it's clearly established that 10,000 Shahed drones would actually be a threat to an aircraft carrier though.

Remember that 10k drones can't just be conjured into the air all at once or act with perfect coordination. There are operational limitations that prevent effectiveness from scaling up past a certain point.

...did you read TFA?

Equally dogmatic take. A lot of scarcity is artificial.

I'm only partway through, but I believe one of the foundational blocks is that computation is fundamentally an interpretation of physical events, not something that can just exist by itself.

It's funny how often my brain gets redirected to German Shepard Dogs when reading conversations about AI. And I still can't remember what the other meaning of GSD is supposed to be without an Internet search.

I would love to see a model of Mythras/Runequest

Do these companies that are buying up all the supply actually need all that RAM right now? Or are they buying it all up in anticipation of future need? If the latter, honestly this might be a case where some kind of regulation really ought to step in.

I think a lot of people (especially those who are only peripherally involved in development, like management) don't really consider performance regressions at all when thinking about how to get software to go faster.

Meanwhile my experience has been that whenever there has been a performance issue severe enough to actually matter, it's often been the result of some kind of performance bug, not so much language, runtime, or even algorithm choices for that matter.

Hence whenever the topic of how to improve performance comes up, I always, always insist that we profile first.

  The old dragon Kalessin looked at him from one long, awful, golden eye. 
  There were ages beyond ages in the depths of that eye; the morning of the world was deep in it. 
  Though Arren did not look into it, he knew that it looked upon him with profound and mild hilarity."

---

I recently had a high-level meeting with Kalessin, a legacy leader in the space. (dragon emoji)

Looking into that golden eye was a masterclass in long-term vision. We’re talking ages of experience and "day one" mentality combined.

Even without direct eye contact, the synergy was real. There’s something to be said for leadership that approaches challenges with profound, mild hilarity.

Key takeaways: 1. Experience matters. 2. Perspective is everything. 3. Don't forget to find the joy in the grind.

#Leadership #Visionary #Legacy #GrowthMindset #Networking

When documentation is lacking, if the 3rd party library is source-available then reading the source code is my next step. This almost never fails me. Source code is usually understandable, generally speaking many brilliant people have put in decades of effort to make source code and the tools we use that way. I've long considered that the ability to understand source code by sitting down and reading as the most important asset a developer could have. Given that, I wonder how the latest trend seemingly against understanding source code will turn out. Maybe it will turn out to be less important, who knows. But it is really weird to live through.

The article was essentially, "you should hate Anthropic" followed by a poorly explained timeline and some insubstantial arguments.

If there was a point there the article did not make it easy to find.