pooberbee (they/she)

Yeah, you would get a runtime error calling that member without checking that it exists.

Javascript and not Coq?

One serving of peanut butter

It’s more like an immovable force vs an unstoppable object

Every day in standup

This was not a case of “I agree with you, but…”, though. “But” is perfectly appropriate here to contrast between the first statement and the second.

If you want to improve your problem solving skills, I’d suggest solving actual problems. Data structures and algorithms can be very satisfying in their own right, but the real value is in taking a real-world problem and translating it into code.

It also depends what you want to do with your knowledge. There are domains that are deeply technical and require a lot of the things you’ve mentioned, but they also tend to be pretty hard to break into. A lot of software is not so deep. Any software project will have need for good domain modeling, architecture, and maintainability. Again, these are things best learned through practice.

I need a ttrpg with a pogs battle mechanic

Armed Bear in the same vein

C shell

Hmm… I admit I didn’t follow the video and who was speaking very well and didn’t notice hostility that others seem to pick up on. I’ve worked with plenty of people who turn childish when a technical discussion doesn’t go their way, and I’ve had the luxury of mostly ignoring them, I guess.

It sounded like he was asking for deeper specification than others were willing or able to provide. That’s a constant stalemate in software development. He’s right to push for better specs, but if there aren’t any then they have to work with what they’ve got.

My first response here was responding to the direct comparison of languages, which is kind of apples and oranges in this context, and I guess the languages involved aren’t even really the issue.

I think most people would agree with you, but that isn’t really the issue. Rather the question is where the threshold for rewriting in Rust vs maintaining in C lies. Rewriting in any language is costly and error-prone, so at what point do the benefits outweigh that cost and risk? For a legacy, battle-tested codebase (possibly one of the most widely tested codebases out there), the benefit is probably on the lower side.

You can make vegan milk at home and it’s way cheaper than cow’s milk. Oat milk is SUPER EASY: 1 cup oats/2 cups water, soak for 15 minutes, blend and strain. Others are similarly easy and there are plenty of recipes online.

My baseless opinion is that having a variety of instances with varying ethoses means that there’s a good home instance for everyone (not just the verysmart, young, white, male, liberal a la Reddit), and federation means that that variety of people are intersecting and interacting a lot more than if instances were completely separate. At the same time, it still feels like a small community, or maybe a bunch of small communities. There seems to be a lot less of the snarky clapbacks and unpopular opinions getting nuked that’s typical of other social media.

Don’t airlines usually charge a bit extra to pick your own seat? I’d imagine/hope that there are enough people selecting the cheaper “whatever” option that they’re going to bump one of those.

I got super sick from this. It probably didn’t help that I was trying soothe my upset stomach with more peanut butter.

I can finally finish my Gyro Zeppeli cosplay

I think your quantifier of “any other language” is the issue. There are certainly languages with far more powerful type systems than Rust, such as Coq or Lean.

This is my perspective on a lot of art and music. If something is universally hated, I want to know why it is and if I can find any redeeming qualities. A lot of my favorite things have that characteristic of doing something very specific extremely well but being generally unlikeable.

Switching to Linux or… maybe?