joekrill

OK, this is all well and good, and may be accurate... But this article is talking exclusively about the shape the butter is formed into. It doesn't have anything at all to do how it's made, or what ingredients it uses, or where it comes from.

I honestly can't fathom how you could possibly make it through the entire game with hardly any bugs. When I played on my PS4 it crashed quite regularly (hourly, probably). It was only slightly better on my PS5. And bugs were everywhere. I don't see how you could play this game for 5 minutes and not at least encounter numerous visual glitches (T-poses, NPCs walking into and through walls or 5 feet in the air). Most bugs weren't game-breaking (though I ran into some of those). But they were certainly plentiful and unavoidable.

How? Luck, really. I think we give way too much credit to people for being "visionary" or talented when really the large part of their success is just luck (particularly around timing). For example, I think the situation with Peleton would look very different if it hadn't been for the pandemic.

It's stealing either way! If I come to your house, take your car, and leave a pile of cash equal to the car's fair market value in it's place, are you going to be cool with that? I think we'd all agree that's theft. It's no different with a Margarita, regardless of what it costs.

> so I nabbed 2 margaritas off the drink mat and left a $20.

Stealing two drinks because you couldn't get your way doesn't really strike me as acceptable behavior in any way. Just because you left a 20 doesn't make it any better.

Philadelphia has done this recently, to some extent: https://billypenn.com/2022/01/24/philadelphia-marijuana-empl...

The article says

> It was last inspected in September

So hopefully that's been addressed by now?

I always wonder how they can be so sure what these things are. In this case, for example, it's described as a "carved grid" and "is hewn into the stone slightly clumsily". Perhaps it was made for storing some specific small item? Or maybe it was used to keep track of something (i.e. move the pebble to the next grid space every time X happens). Or maybe it was just someone bored and carving a design?

The underlying problem is they are asking you to trust Drata implicitly, sight-unseen, and give them unfettered access to their laptop. There is nothing preventing Drata from changing their minds and altering how their agent works or what it collects.

Then there's the unintentional aspect. There is, of course, no guarantee their agent is bug-free. Data leaks and compromises happen all the time, by every facet of company (large, small, respected, hated, etc).

This is really a huge risk IMO. If anything, it's being downplayed and far from "nonsense".

Maybe they are big fans of Newsradio (one of my all-time favorite shows) https://www.youtube.com/watch?v=3JpwjnMFlJI

It's completely self-hostable. You just need to provide a database (PostgreSQL, MySQL, CockroachDB). My impression is Ory Cloud is a hosted instance you can pay for instead of running it yourself (like using a hosted database solution instead of running your own, for example).

For those looking for a comparison, this is like an alternative to KeyCloak, except you have to "bring your own UI" - which I see as a pro, not a con. I've been evaluating Kratos for some time now, implementing it in a React/Redux/RTK Query app, and I've been really impressed with it. It's still not on parity with the massive feature-set and customize-ability of KeyCloak, but it's getting there pretty quickly. As of the latest release I think it's finally in a state where it can be used in production with little friction. But I'm really looking forward to what the future holds.

Thanks, I'll evaluate Flagsmith as well!

Not totally sure Flipper is in the same category - that's more a Ruby-specific library, no? I know they have a cloud offering, but that isn't open source.

One more I found: https://github.com/checkr/flagr

I've been looking into using Unleash (https://www.getunleash.io/) for this sort of thing. Seems like that would be a better option than rolling-your-own, particularly if you have the infrastructure for it. I haven't actually gotten too deep into it to know what limitations might come with using it. Does anyone have any experience with it?

A little pet-peeve I have is when an obscure(ish) acronym is used and never defined. Is SERP a well-known acronym? Perhaps this is a niche blog and I'm not the intended audience.

All of these product management processes seem to assume there's no underlying maintenance or tech debt that needs some level of attention. And there almost always is, but it's really hard to measure impact because it's usually "hidden" (that is, it's not a direct impact, but it ultimately affects velocity, on-boarding, developer happiness, etc). So with "tricks" like this they get relegated to "low impact", while "high impact" (typically "user facing features") get prioritized.

And there's lots of other things that have hidden or very difficult to measure impacts. These often revolve around developer happiness and growth. For example, ignoring a complex, bugging and/or aging codebase can affect attrition (among other things), which will quickly get _very_ expensive: as a team starts losing developers, the remaining developers have to carve out more and more time to interview and onboard. Not to mention the direct company costs of turning over employees. And trying to find quality employees who are willing to work with in that codebase.

And maybe this sort of thing should be addressed "out of band" - ancillary to the product management lifecycle. But that's really hard to maintain in most orgs.

Actually Roku started as a "Netflix Box" meant to stream Netflix content, and funded by Netflix.

Did you read the emails, though? They certainly don't sound like simply asking about "where they are on the mDL standard". They are asking for NDAs to be signed - why is that necessary if this is just about the progress of implementing an ISO standard?

And there's this from CA:

> The agreement I've been provided goes beyond a POC and appears to create more of a long term relationship.

It seems like it should be objective, but it isn't. Because you get people writing ridiculous "clever" one-liners that are difficult to parse and understand. That clever one-liner could be re-written to do the exact same thing and be much more clear and readable, but it would take, say, 8 lines instead of 1.

Then there's the subjectiveness of what you actually consider a "line".

This is horrible advice.

Just because something has been done a certain way for a long time does not mean it's something we should continue. In a lot of cases it just means we didn't have the knowledge that it was so bad for you. And that's exactly where alcohol fits in. We know alcohol is bad for us in just about every way. So there's really no such thing as "under drinking".

Cigarettes. Cocaine. Tanning. Not wearing seat belts. Not wearing helmets. Beating kids as punishment. Bloodletting. X-rays. I mean the list is just endless.

Folks should do as they please. I'm not suggesting everyone needs to stop drinking or anything. But to suggest that "perhaps also be cautious of under drinking as well" is just downright wrong.

100%. I use RhymeZone and Wordnik more than I care to admit during development work.

You can't match up the product with an actual user or person in any way.

What conclusions did you come to?

What a cool project! Really enjoyed reading about the recovery. Crazy how well that thing held up.

I've tried really, _really_ hard to like Bitwarden. But I ran into 2 huge issues, that ended up being blockers for me:

1. Sharing is super-confusing. I was trying to organize things for my mom, as well for my wife and I. And you have to create these "organizations". And they makes things really confusing for a variety of reasons. They are a different pricing/SKU. And the UX around them is not good. It's not clear where things are being created a lot of the time, and who may or may not have access. It just was a really bad experience.

2. It was outrageously slow for me. I use Enpass otherwise, and it comes up right away, and searching is relatively fast. But Bitwarden always had this delay. And it was a huge pain point because it wasn't clear immediately if there were just no results, or if I just had to wait a few seconds. And sometimes things would pop up unexpectedly.

So I've continued using Enpass. It has _by far_ been my favorite password manager. It's no open source, but it uses Sqlite and SqlCipher under-the-hood, and I have full control over where it syncs my data to. Sharing is still a problem (mainly because of the architecture decisions - there is no "central server"), but everything else is so great that I'm fine making that tradeoff.

The guy that's arguably the impetus behind this whole GME thing gives a compelling story in a 5 minute youtube video: https://www.youtube.com/watch?v=alntJzg0Um4

* I don't own GME or have an interest in this whole thing one way or the other, nor do I have an opinion on Roaring Kitty's research. I just find this all very interesting to follow.

Clearly not everyone thinks that's the state of affairs. Roaring Kitty has clearly done quite a bit of research and thinks GME is undervalued. And if you believe that many of the folks on /r/wallstreetbets are being genuine, then they feel similarly. Time will tell. But there's certainly no guarantee that this is a "once in a lifetime overpriced valuation".

In that case they could most definitely inform their investors directly and there's absolutely no need to make a public statement about it.

It's not mentioned specifically, but I think this very much falls into the "Accidental complexity" bucket. In the same way he describes someone choosing to use Mathematica for solving a problem - a developer choosing an obscure technology or writing poor code is just more accidental complexity.

I think the best point in the article is this:

> ReScript, as with other statically typed functional languages, aims at changing the way code is approached at a fundamental level.

We currently have a project written in ReScript and it's an absolute nightmare. Most of our stack is JavaScript/TypeScript/Flow, so no one can just jump in and work on it very easily - they first have to learn ReScript and all of it's different concepts, approaches, and nuances (or refresh themselves if they've done that but haven't worked on the project in a while). It's a HUGE context switch. At least TypeScript is a superset of JavaScript so it's very easy to get up to speed on for a JavaScript developer, and switch between.

For a side project this is fun. But I would never consider this for a "real-world" project (i.e. something you get paid for). At least not anytime soon. Maybe in a few years if there's wider adoption, but that's a long way off.