OneCardboardBox @ OneCardboardBox @lemmy.sdf.org

Posts

15

Comments

228

Joined

2 yr. ago

Yeah, apparently it's the wand from a Rancilio Silvia: https://m.youtube.com/watch?v=5AOTa3bEpYM

Ahh, sorry. Our prior emails accidentally got sent to a family of 4 on their way to a birthday party. We promise our next job offer won't miss!

Everyone's gotta start somewhere. I do know that it's not easy for trans men to get a well-fitting suit. I'm familiar with one case where the tailor sent the suit back without any alterations, because they thought the body proportions given by the shop were a mistake. That was rather infuriating to see, but it worked out in the end. I guess what I'm saying is that you should give yourself plenty of time in advance to get your next suit. It may not be the "come back in a week for pickup" that most men are used to.

Hell, I know a cis guy who had to visit 8 different places to find a suit that fit him. He's a normal looking guy, but the proportions between his hips and waist was somehow an outlier for 99% of the pants he tried on.

Got a secondhand Delonghi Dedica because I had similar concerns over how much I'd use it. Previous owner installed an aftermarket steam wand, which has been a joy.

Overall, it comes and goes in waves for me. Some weeks I pull shots every afternoon, sometimes it sits unused for a month. I enjoy taking some time to step away from the home office and prep coffee, so espresso is nice for that. I'd probably use it even more if we were more of a milk drinking household. I like my steamed milk drinks, but we don't reliably keep milk in our fridge.

I'm also very lazy about dialing in shots. We like to buy a variety of beans for our morning French press, so the coffee available for espresso might vary week-to-week. I'm not willing to waste coffee dialing in on a 16oz bag of beans that'll be gone in a few days, so the quality of my espresso suffers. Do most people generally keep one kind of bean around specifically for their espresso?

Reminds me of an early Uni project where we had to operate on data in an array of 5 elements, but because "I didn't teach it to everyone yet" we couldn't use loops. It was going to be a tedious amount of copy-paste.

I think I got around it by making a function called "not_loop" that applied a functor argument to each element of the array in serial. Professor forgot to ban that.

I needed to find large directories on disk the other week, and found the tool btdu to be quite useful.

https://github.com/CyberShadow/btdu

In this context, orphaned doesn't always mean you should remove it. It just means that nobody in AUR is taking responsibility to keep it updated. You still might have other packages from the AUR that depend on this one.

Since it is unmaintained, basically anyone can now claim ownership of that package in the AUR and push updates for it. Theoretically, someone could try to distribute malware in this way.

This is why it's important to check the diffs of your AUR updates.

It could be a firmware update. I noticed on my machine that there was always one update in the discover program that appeared as ready but never got installed.

Turns out I had to manually run fwupdmgr update to install it.

He'd rather have a GNU contributor take a diarrhea dump on his pull request.

Consider SW Michigan. 2h drive/train to Chicago, proximity to large bodies of water for summer enjoyment, and if you live in a reasonably-sized town they're probably good at clearing roads when it snows.

Besides, our winters get milder each year. There's a couple of big snow/ice events, but the trick is to not be on the road while the heavy stuff is coming down. Wait a few hours for it to ease up and for the snow plows to do their thing.

These days, it's not actually a blanket ban on anyone who used cannabis. To join the FBI, you need to be cannabis-free for 1 year before applying for a job.

https://fbijobs.gov/sites/default/files/2023-04/guide_eligibility.pdf

Reverts work because users have equal write access to all the data. You can mess things up in the codebase, and even if you die of a heart attack 10m later, my revert is just as valid as your commit.

It's not really the same when every user has "sovereignty" over their address in the ledger. A bad actor has to consent to pushing a revert transaction onto the chain, or they have to consent to using a blockchain system where 3rd-party reversion is possible (which exists on some systems, but also defeats the concept of true sovereignty over your address).

Sounds rough. My fiancé does security, and from what I've gathered from him, the best time for security to get involved is at the design stage. They look over the proposal, give their input, and then nobody's surprised at release time, and teams can follow agile practices. Obviously there's still a review of the final product, but that can be done asynchronously after the fact to confirm that best-practices were followed.

Easy to say, hard to put into practice. Certainly depends on the kind of service your business provides.

I don’t think the security people would like that idea very much

Why not? How do your feature flags work?

Small releases, on a regular cadence.

How do you ensure that you're not releasing features before they're ready? Kinda depends on the application, but you might use feature flags. A system for turning features on and off without deploying the application. It could be a Boolean in a redis cache that your app looks for, or a DB entry, or another API. The point is for you to be able to flick a switch to turn it on instantly, and then if if breaks things in prod you can just as easily turn it off again.

And just a word of advice: Consider the performance impact of your feature flag's implementation. We had a team tank their service's performance because it was checking hundreds of feature flags in different DBs on every API call. Some kind of in-app caching layer with a short refresh period might help.

...and of course Duck Game never got released on GoG

Fuck this greedy bullshit

"What's up dog turds?"

"How's it hanging, dingleberry?"

"Nice job, Captain Hazelwood!"

I do actually know someone who speaks like this.

I know that your question is about tasting basics, and I think the answers here will get you on the right path.

There's a lot that goes into coffee tasting on the advanced end. Ever wonder who decides that a coffee tastes like "raspberry" and "chocolate"? A few years ago, I found a local roaster that runs barista classes, and I got tickets to their coffee tasting session. It's really interesting to learn about all the process and procedure that goes in to tasting coffee. They take something as subjective as taste and turn it into (somewhat) objective and quantifiable data. I also learned how coffee beans are graded, and how roasters source their beans.

The official term for this process is "cupping", so if you're interested, look in your area for cupping classes. I had a great time!

He shunts all your long running jobs to the slowest hardware on the rack.

You are not in the sudoers file. This incident has been reported and your account suspended.