pooberbee (any)

One serving of peanut butter

You coud try eating the pellicle from a batch of kombucha.

I’ve been each of these at some point.

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.

Are you implying that sports aren’t popular everywhere or that everywhere is a dictatorship?

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.

My expectation is that a post’s score is upvotes minus downvotes, but I think it should be more like upvotes plus comments with downvotes excluded (or maybe let users filter based on upvote/downvote ratio or something). Maybe count commenters instead of comments.

Actually I have very fond memories of my family’s old Aerostar.

Someone is lying

She donkey on my kong 'til I country

Just the one Falkland, actually.

As a combination back- and side-sleeper, I’ve been considering trying to strap foam blocks to the side of my head so I can always get the right amount of support regardless of position.

I can finally finish my Gyro Zeppeli cosplay

So he’s definitely dead?

“gigging on your dock”?

Me too and meee tooooo. I showed it to my stone-free wife and she didn’t laugh.