I saw the video a few days ago. It uses some napkin math but the author does at least use a spreadsheet / toy model to arrive at their conclusions.

Ohhh okay ty "throwaway920102" will take your word for this.

Ray is a reasonably well-known current/former professional city planner who does look at data to make his content.

The videos he makes do sometimes use napkin math but in the way a city planner does napkin math - with data.

They also don’t claim to be a comprehensive study and each video is accompanied by a pretty thorough disclaimer on what methods are being used.

Odd and unfortunate that this one was taken down.

Was trying to be at least a little helpful "irl_zebra", not to suggest the video was sufficient evidence.

An AI slop assembly line, nice work!

I get the concern. The aim isn’t to produce slop, but to help creators streamline real work.

Hard to believe when the page literally says

> Create a viral Reel in just 2 clicks

well yet it's true

Offer to trade your teams engineers to work on a product/feature/roadmap item of their choice in exchange for them doing your thing.

I think this is good advice, I'm adding it to my bag of tricks, thanks.

I have to ask a follow-up - there are cases, where the teams don't see any value in security at all, so they don't want anything that I'm selling. I think I know the answer to this one (namely, you need to build relationships with and convince the leads). But I am still looking for an alternative as the above is hard in all cases and impossible in some.

Sometimes it works to find a solution which makes the life of teams easier and comes with an additional gain in security. That can potentially be sold more easily to the team then, as you are solving a problem the team actually experiences.

Because Gleam compiles to Erlang, it can seamlessly integrate with the larger BEAM ecosystem, including existing Erlang and Elixir OTP applications and libraries.

@external decorator: This escape hatch allows Gleam code to call functions defined in Erlang or Elixir modules. While it bypasses Gleam's type checks for the function call, it provides a powerful way to leverage the full capabilities of the existing OTP ecosystem.

I believe the biggest reason it's hard to replicate OTP fully and quickly is Gleam's type system (but I could be wrong).

Go Generics provides all of this. Prior to generics, you could have filter, map, reduce etc but you needed to implement them yourself once in a library/pkg and do it for each type.

After Go added generics in version 1.18, you can just import someone else's generic implementations of whatever of these functions you want and use them all throughout your code and never think about it. It's no longer a problem.

The language might permit it now, but it isn't designed for it. I think if the Go designers had intended for map, filter, et al to replace most for loops, they would have designed a more concise syntax for anonymous functions. Something more along the lines of:

    colors := items.Filter(_.age > 20).Map(_.color)

Instead of

    colors := items.Filter(func(x Item){ return x.age > 20 }).Map(func(x Item){ return x.color })

which as best as I can tell is how you'd express the same thing in Go if you had a container type with Map and Filter defined.

pretty much all economists and commentators state that the replacement will be a basket of currencies not a single currency, where each countries' basket will be weighted by the typical trade volume they have with other countries (more trade with Country X, then hold more of Country X's currency) plus some factor for stability/volatility/currency risk etc.

This, incidentally, is exactly how the value of the Singapore dollar is managed.

This sounds like fodder for a really interesting blog post tbh. I would read it.

I would argue logging options to be more of an exception than the rule. Compare the actual language features of Go to something like Rust or Javascript and you'll see what I mean. As a new developer to the language (especially for juniors), you can learn all the features of Go much faster. It's made to be picked up quickly and for everyone's code to look the same, rather than expressing a personal style.

PVC is considered as the most environmentally damaging plastic and one of the most toxic substances for inhabitants of our planet. From cradle to grave, the PVC lifecycle (production, use, and disposal) results in the release of toxic, chlorine-based chemicals, and it is one of the world's largest dioxin sources.

https://www.ncbi.nlm.nih.gov/pmc/articles/PMC10779931/#:~:te....

> they don't want to deal with GDPR

or cannot afford to. add in DSA and DMA as additional burdens.