Annalee

@gnomon I recently joked to my team that shit-talking floating point math is two drink minimum comedy Which is of course absurd It's 2.000193 drink minimum comedy

And of course access to health care goes hand-in-hand with other social safety nets. Turns out people are healthier when they are food and housing secure, have better labor protections, have better support in early childhood and better support as parents of young children, etc. The thing is that those things rather by definition are not consumer products that can be sold in the US market, so they don't get media campaigns and catchy headlines about how you can buy them for $20.

Right so this thread is getting some "well actually it's the thing you just said," and a metric fuckton of "well actually it's my personal pet cause," so time to mute. Enjoy arguing about bike infrastructure, processed foods, sugar, and breast milk amongst yourselves (it's still access to health care and a strong social safety net but y'all have fun). Really wish we had an option to close/limit replies; comes in real handy when a post goes viral.

Next time I'll pick a bone with floating point math It hasn't got enough detractors (Probably because if you detract from it you won't get the correct answer, badum-CLANG)

Anyway I was reminded of that stupid auto industry propaganda on my way into work this morning, when a driver of an SUV camped out in a crosswalk, forcing everyone to walk into traffic to get around their car, and then *made eye contact with me* before pulling directly into my path so I had to pull up short to not get hit. Yes, I yelled at them, and no, I'm not sorry. Phones don't kill pedestrians. Drivers do. Never let the auto industry tell you otherwise.

@4raylee that's it, thank you!

@rl_dane thanks, found the tool here: https://github.com/obra/Youtube2Webpage And bless you for actually asking instead of assuming a certain level of comfort - I do a lot more managing than coding these days but I know my way around the terminal* *For values of "know my way around" that include "my keyboard shortcut aversion pains pairing partners" but I get by

@jesse I hate ads but am actually happy to directly pay creators of instructional material I find useful, via patreon or their own websites. But man if any of the really good unreal tutorial makers made a habit of actually writing tutorials instead of doing screencasts I'd subscribe so hard I'd pay their phone bill

When trying to get a professional finish, ironing is more pressing* than your actual stitching. After you stitch a seam, ironing re-aligns the weave of the fabric, setting stitches and eliminating warping. But what about before stitching? It's not necessary to iron flat seams before stitching unless the fabric is wrinkled. But for things like darts, a sharp crease makes it much easier to stitch a clean dart that doesn't pucker at the tip. *heh

Also, they distort your fabric, which is bad when ironing and worse when stitching. They also don't really save you time: basting a dart doesn't take much longer than pinning, and you'll make up the time at the ironing board and while sewing, since you don't have to navigate around/remove pins.

@FrugalGamer oops sorry, stray reply deleted. It has been found! https://github.com/obra/Youtube2Webpage

(Why not just cut the seam allowance short and even? Because the extra is there for alterations. If you buy a suit from a premium brand, you'll probably notice that several of the seam allowances are pretty dang wide. That's because the thing was built to be tailored to your exact measurements after the fact. Even when building a one-off garment to my exact measurements to start with--measurements change over time, and leaving room to alter can extend the life of the garment).

Why bother basting? A lot of home patterns omit this step, or if they include it they don't explain *why*, so many home sewers skip it. The main reason is to do with another step a lot of home sewers skip: ironing.

First, they can damage the bottom of your iron, sometimes irreparably. You don't want snags and burrs on your ironing plate. Second, if you pin your seam in place before stitching, you have to pull the pins back out before they reach the needle, which slows you down and makes it harder to stitch nice clean lines. (Sewing right over your pins is a good way to break your needle and lose an eye. Don't do it).

(Which is why, in addition to basting the darts, I also thread-traced the pocket lines). As for pins: They're super handy for draping and fitting. But I encourage anyone who's looking to level up their sewing to get out of the habit of using pins at the machine stitching stage. I know that's a sharp* take and somewhere there is an expert sewist who uses pins constantly when stitching, but you are probably better off without them. *heh

When DO I thread-trace and/or baste a flat seam? When the seam allowances are large or uneven, I generally do one or both--sometimes I'll just mark the seam lines with chalk or fabric pen and then baste. If marks are going to be a problem I'll thread trace and baste instead.

I generally don't bother thread-tracing or basting a seam that lies flat and has a short, even seam allowance (most seams on commercial patterns) because I can just align the pieces by hand while stitching, but basting is also way more effective than pins in keeping stretchy, slippery, or otherwise difficult fabrics aligned.

But what's that got to do with basting? Surely you can just pin the dart and iron it, or line it up by hand? You may notice in the pics at the top of the thread that my tailor's chalk is way more visible before ironing than after. Fabric chalk/markers/crayons are generally designed to disappear when wet or heated. Steam irons do both.

@Deestevens@mastodon.ie forever and always

@mcc indeed — I suspect the real reason C++ is still doing it the C way but with a compiler warning is the backwards compatibility issue; one would hope that anyone implementing a switch statement in a language now would follow c#'s pattern (or facilitate fallthrough using a different pattern than a switch statement)

@mermaidchaser found it! https://github.com/obra/Youtube2Webpage

@jesse that's fair! And I think you're right that tooling is half of the problem. Videos may be easier to monetize but screencasts are just plain easier to *make,* which is why it's so hard to find traditional illustrated instructions. I actually think the main challenge is that speaking for dictation is different than speaking for video - tutorial makers would have to learn to do the former to make the posts work Or else make the goal a slide deck?

@thedeadlands@wandering.shop welcome! We're glad you're here!