pooberbee (any)

One serving of peanut butter

Every day in standup

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.

Having tasted a few dog foods and treats, I agree.

I’m guessing the pumpkin spice isn’t too strong either, but dried pumpkin is the first “flavorful” ingredient, at least.

But these do have pumpkin in them.

My dog goes nuts for pumpkin puree, but hates greenies, so I dunno

I loved the controller except for the long pull on the shoulder buttons.

Either #2 or #3. /usr/bin and /usr/local/bin exist for that purpose, but some people prefer to keep personal scripts and such in home, maybe as part of a dotfiles repo or something, and so just add ~/.dotfiles/scripts or something to PATH.