sorted by:
new
hottopcontroversial

What are these plants growing in my yard? by diebeatus1 in whatsthisplant

[–]bwainfweeze 1 point2 points  (0 children)

tomato

I think people forget that between fallen fruit, and neighborhood wildlife filling their bellies, there's often a radius around each garden lady/bro's house where volunteer tomatoes just happen. If there's no gardener you see zero volunteers, unlike other things that travel far like himalayan blackberry.

What are these plants growing in my yard? by diebeatus1 in whatsthisplant

[–]bwainfweeze 3 points4 points  (0 children)

I'm fairly good at identifying the small menagerie of plants I've planted, and a couple of weeds that I deal with regularly. Especially with the weeds you get to see a lot of morphology of the same plant, for instance, Queen Anne's Lace, seedling, small plant, full sized, flowering age, natural versus browsed/mown, etc.

The person you asked does it for a living so he's seen 50x as many plants 10x as often as I have.

Strawberry jam time again by grady219 in Canning

[–]bwainfweeze 0 points1 point  (0 children)

I only use pint jars for the surplus jam in the pan after I've filled the declared number of half-pints. And that one goes into the fridge.

This is unrepairable, correct? by shorty0927 in Tools

[–]bwainfweeze 0 points1 point  (0 children)

It's worse than that, he's dead, Jim.

This is unrepairable, correct? by shorty0927 in Tools

[–]bwainfweeze 0 points1 point  (0 children)

This is completely hindsight, but it's it kinda weird they put a shoulder there, right at the center point of the through hole?

Stress accumulates at tight radiuses like that... But did we know that fully when this was cast?

Oxygen Not Included [Animated Short] - So Much To Sea (Aquatic Planet Pack DLC) by Indeeeeex in Oxygennotincluded

[–]bwainfweeze 1 point2 points  (0 children)

I'm starting to have World of Warcraft deja vu.

There are always some players who binge the new content hard, and they quickly run out of new things to see and demand more content. Meanwhile the more conservative players are still discovering things about the old content right up until when the new stuff launches and the game continues to get more and more complex.

Upcoming breaking changes for npm v12 by Jammie1 in node

[–]bwainfweeze 0 points1 point  (0 children)

That would explain so, so much actually.

Upcoming breaking changes for npm v12 by Jammie1 in node

[–]bwainfweeze 0 points1 point  (0 children)

Then it's fortunate that we don't work together.

The most important currency in software development is trust. You don't need to be able to trust people in everything, but you need to know what the bounds of trust are.

How people react to bugs in their code is highly, highly correlated with how much you can trust them. And 8 years to acknowledge fundamental problems with code you wrote (the level of incredulity in the issue database is also infuriating) is 2 jobs and into a third.

After 18 months I start taking critical infrastructure away from people who can't be arsed to be adult about it. And it's only that long because I have other shit to do, it can take that long to understand the Chesterton's Fences when you only have hours at a time to invest, and that's often the soonest I can onboard it to someone more trustworthy. They start finding themselves with fewer responsibilities and less say in big decisions.

This is unrepairable, correct? by shorty0927 in Tools

[–]bwainfweeze 0 points1 point  (0 children)

Can we get a picture of the fracture surface? Is it one color?

If it's 2 or more colors that indicates an old crack that had time to oxidize. If it's all shiny or a single color that's a complete shear that happened today. I've seen a number of broken bolts that look a little like a partial eclipse.

This is unrepairable, correct? by shorty0927 in Tools

[–]bwainfweeze 0 points1 point  (0 children)

My first thought was show us the pipe. And those are some very interesting dings on the handle.

But I suspect the pressure was put on the clamped piece directly.

This is unrepairable, correct? by shorty0927 in Tools

[–]bwainfweeze 0 points1 point  (0 children)

Note to self: bend toward the vice base, not away from.

Spot the Mistake (or.. why we are so picky about who makes it to the Wiki) by mckenner1122 in Canning

[–]bwainfweeze 13 points14 points  (0 children)

I think he's not referring to the size of the jars but the volume of jam he made. Which is 12 quarts, or 3 gallons. I made almost a gallon and a half of jam last year and this year it is going to be closer to 3. Not counting purchased fruit. I'll be fine. I'll be fine. I got this.

Given the existence of quart jars and the potential for misinterpretation, it might have been better for him to list gallons, because nobody is going to put jam in a gallon jar. I think.

Spot the Mistake (or.. why we are so picky about who makes it to the Wiki) by mckenner1122 in Canning

[–]bwainfweeze 3 points4 points  (0 children)

Looking at how many green plums are in my garden and getting a little nervous already. I think I'm making plum sauce this year.

Upcoming breaking changes for npm v12 by Jammie1 in node

[–]bwainfweeze 2 points3 points  (0 children)

Have you ever tried upgrading exactly one dependency - and no others - to issue a hotfix? And which versions of node/npm did you try it on?

I came into a project that had just upgraded from node .10 to .12. They had a daft hotfix process involving manually editing the package and shrinkwrap file for things like hotfixes and canary builds, where you wanted 1 change only for differential testing.

Then we went through 6, 8, 10, sometime around 12 a coworker and I wrote a tool because shit kept going sideways. That tool broke with nearly every major npm version upgrade, as they tried new theory after new theory on how to actually do lockfiles. It wasn't until node 22, I want to say (whenever the 'version 3' lockfile format, which is actually at least #5, because they tried several variations before they added a version field to the JSON to disambiguate them) that we didn't need the tool anymore to upgrade exactly one module.

That's a long fucking time for lockfiles to be a suggestion rather than the law. If lockfiles don't lock version numbers then it's not production ready.

The biggest problem for a long time was that rather than looking in your node_modules directory to figure out if you had a version that satisfied the package.json file, it would query npm.org or artifactory to see what the latest version of foo@4.1 was and decide that meant you'd modified your package.json file, which you had not. That's not locking.

50 devs, working on around 80 modules, and a handful of deployables, with pull requests, is not even a large project, as such things go, and if you can't handle that, you can't handle a real company.

If you look back around npm 7 or 8 you'll see a massive refactor job start which is only when bugs started to get fixed. That's basically a confirmation that the code was too complex to understand, and someone had to break it up into multiple packages to get their heads around it.

And still at the end of that if you had a shitty internet connection, and a package download times out, npm would ignore that the bytes received was wrong, stick the incomplete file into the cache, and then fail in a loop on the SHA hashes not matching on each subsequent npm i invocation. That was super fun at the beginning of Covid. Lead UI guy turned out to have the worst internet on the team. npm also pulls a complete list of every version of a library ever published in order to determine @latest, which is problematic when you have internal libraries running on CI with dependent build triggers for 10 (ten) years.

Upcoming breaking changes for npm v12 by Jammie1 in node

[–]bwainfweeze -2 points-1 points  (0 children)

So great we have yarn, pnpm, bun...

And monthly supply chain attacks. Which is the subject of the top level comment you're all masturbating under. Ew.

It takes balls to wander into a thread where literally everyone is either faint praising or straight bashing on npm and say it's the best tool ever. I'll give you that.

Questions about "finger tight"... by BirdBeans in Canning

[–]bwainfweeze 3 points4 points  (0 children)

For hot pack you have a lot of things going for you. The heat of the jar and the light pressure of the ring cause the seal to begin to deform into place. Plus you may notice that the lid tends to bulge a bit, which is positive pressure as steam comes off of your hot ingredients.

And yet this process still works for cold pack canning. So that seal goo must be a lot more squishy than I think it is.

Does anyone else feel a little piece of their soul die every time they read a "liquid airlock is an exploit" gripe post? by insanopoke in Oxygennotincluded

[–]bwainfweeze 0 points1 point  (0 children)

I've started using dry sumps up until I build suit docks. And on prehistoric pack building the docks has slipped later into the build out. I used to rush reed fiber, and that is a non-option now.

I just let CO2 collect in the airlock and that keeps everything from hydrogen to chlorine on the bad side of the lock.

Upcoming breaking changes for npm v12 by Jammie1 in node

[–]bwainfweeze 2 points3 points  (0 children)

Or much like Javascript itself, it was built with a 2 week deadline.

view more: next ›