I feel like this poem isn't really about soldering, but if anyone is actually bothered by it, there are some options.
Unleaded solder and a decent fume extractor make the process cleaner. A decent soldering iron and solder wire with good-quality flux (e.g. Kester) makes it faster.
If you'd rather not deal with the iron, you can manually apply solder paste and use a hot air rework tool or even a heat gun (careful!) to melt it. (A proper reflow oven is better, of course, but that's pricey.) This makes working with surface-mount components much easier.
If you'd rather not deal with it at all, have a PCB assembled somewhere else. JLC is pretty cheap, especially on simpler boards.
>A proper reflow oven is better, of course, but that's pricey.
You can do a lot worse than a $55 temperature controlled hot plate. Plus you can watch the magic happen. Of course that only works for single sided boards. I've been very impressed with the results.
Anthropomorphizing LLMs is something that happens in the design stage, when they're given human names and trained to emit first-person sentences. If AI companies and developers stop anthropomorphizing them, users won't be misled in the first place.
This reminds me a bit of the ending of In the Beginning Was the Command Line:
> The people who brought us this operating system would have to provide templates and wizards, giving us a few default lives that we could use as starting places for designing our own. Chances are that these default lives would actually look pretty damn good to most people, good enough, anyway, that they'd be reluctant to tear them open and mess around with them for fear of making them worse. So after a few releases the software would begin to look even simpler: you would boot it up and it would present you with a dialog box with a single large button in the middle labeled: LIVE. Once you had clicked that button, your life would begin. If anything got out of whack, or failed to meet your expectations, you could complain about it to Microsoft's Customer Support Department. If you got a flack on the line, he or she would tell you that your life was actually fine, that there was not a thing wrong with it, and in any event it would be a lot better after the next upgrade was rolled out. But if you persisted, and identified yourself as Advanced, you might get through to an actual engineer.
> What would the engineer say, after you had explained your problem, and enumerated all of the dissatisfactions in your life? He would probably tell you that life is a very hard and complicated thing; that no interface can change that; that anyone who believes otherwise is a sucker; and that if you don't like having choices made for you, you should start making your own.
> Get rid of sales tax, property tax, exemptions, IRAs, 401ks, short capital gains, long capital gains, medicare, state, all of that bullcrap. Annualized, non-annualized, credits for having an EV on the 4th day of the second Tuesday while being a fisherman, married and single filing differences, end all of that.
I agree with your overall point of simplifying taxes by merging more things into income tax, but some of the taxes you mentioned are levied by local governments to fund themselves. The United States has a federal system; it would be a much bigger change to centralize all of the funding.
Well, local governments (cities and towns) also have expenses -- police, fire departments, trash collection, water and sewage, roads, public works. Schools are partially funded locally. That has to be paid for.
It's theoretically possible for a local government to levy an income tax, but a lot would need to change -- much more than just changing tax rates. Employers and banks report income to the federal government (and states, I suppose, but I live and work in Texas so I don't know much about that). They would have to report that information to towns and cities too. There's also the problem of granularity -- how does an employer or bank know where someone actually lives? If you have a P.O. box in a town, do you have to pay taxes in that town? If you work in a different municipality (not uncommon!), do you have to pay taxes there too? If you have a home in one town, work in another, but spend most of your free time hanging out in a third, are you completely off the hook for supporting the third town?
You could have the federal government collect all the money and then allocate it to state and local governments, but that's a massive change in how American society works, and I'm not sure it's any less complex in the end. Some of the complexity in the tax code (e.g. different levels of capital gains tax) is a policy choice, but some of it reflects the complexity of the real world.
Fair enough. I was thinking of local governments unilaterally deciding to impose income taxes. The impression I got was that existing local income taxes are effectively state funding for municipalities collected and distributed by state governments, which doesn't seem like quite the same thing, but perhaps I'm splitting hairs.
Existing local income taxes are imposed by local authorities. Because states (unlike the federal government) have general police powers, there generally must be authority for the local agency to do so in state law, but this is not the same as state taxes which are redistributed to local governments (which also exist.) Some states include in their laws allowing local jurisdictions to impose income taxes provisions for collection and distribution to the taxing authority by the state tax agency alongside state income taxes, to avoid the expense of duplicated administrative function, but I don't see how that changes the essential local character of the tax.
I tend to agree with this. The logic should be the same with different rate tables for each taxing body. What I don't want though is the Fed govt being the collector and distributor of all the funds. They already weld too much power with their various funding influences for transportation, healthcare, etc. The states and local govts shouldn't need to pander so heavily to the federal govt for funds.
It seems efficient and simple that way. But you don't want federal politics playing that much of a part of your local life. And you don't want your local politicians to have to pander to the federal levels just to get what they need or what is theirs. I think this would result in disaster as the federal politicians are too out of touch with local needs.
If we had a single formula for taxes, then each taxing body could have their own rate table to apply to it, but still collect it directly - then I think that would be a better approach.
For simplicity sake, take income tax at flat rates. Federal may be 20%, your state might be 10%, city might be 5%. Maybe my state rate is only 5% and you might want to move here, but nationally we all pay the Federal 20% rate.
By definition, a federal system does prevent a single point of collection and distribution. If states could not or did not collect taxes on their own authority, it would not be a federal system. States would just be adjuncts of a national government.
Which misses the point. If the point is to reduce the number of taxes, having the federal government collect 10 different types of taxes instead of state governments collecting 7 types of taxes won't change all the different taxes we have.
There is no singular place we can change how many different taxes you pay. There's... thousands? Tens of thousands? Once you factor in city, county, state, federal, special districts, etc.
Just used this to make a couple quick diagrams. It's easy to use and the diagrams export well. A couple suggestions for improvement:
1. When working with small rectangles, I had trouble getting the rectangle to move instead of enlarge. It looks like holding down the mouse button for a second makes moving more reliable. The UI should make it clearer what I'm actually doing.
2. If I open MonoSketch in another tab, I can't make a second diagram at the same time as the first -- there seems to be one shared context between tabs. I would like to be able to make a new diagram separate from my current one.
Some background for those who aren't familiar: "Romanization" refers to converting Japanese sounds into the Latin (Roman) alphabet. In Japanese, these sounds are written with phonetic characters called kana. (There are two types of kana; I'm only going to talk about hiragana here.) Each kana represents either a vowel or a consonant followed by a vowel. For example: あ (a), こ (ko), ね (ne). Aside from a terminating n/m sound (ん), there are no characters for standalone consonants. There are five vowels (a i u e o).
The kana are usually written in a table where each row is a vowel and each column is a consonant, like on Wikipedia[1]. Most columns of the table have five characters, each representing the same consonant combined with one of the vowels. For example: か/き/く/け/こ ka/ki/ku/ke/ko, ま/み/む/め/も ma/mi/mu/me/mo. Some columns have "missing" sounds (や/ゆ/よ ya/yu/yo); but what's important for our purposes is that some columns have irregular sounds: さ/し/す/せ/そ sa/shi/su/se/so and た/ち/つ/て/と ta/chi/tsu/te/to. There are no si, ti, or tu sounds in standard Japanese; they have shi, chi, and tsu instead.
Using diacritic markings gets you more consonants. Most of these are made by adding a couple tick marks to the corner of the character, which makes the consonant voiced instead of unvoiced. For example: か ka -> が ga, と to -> ど do, ひ hi -> び bi. But the irregular sounds stay irregular: し shi -> じ ji instead of zi, ち chi -> ぢ ji (again) instead of di, and つ tsu -> づ zu instead of du. (す su -> ず zu gives the same sound but in a regular way.)
You can also combine i-vowel characters with y-consonant characters to get sounds with consonant clusters: き ki + や ya = きゃ kya, み mi + よ yo = みょ myo, etc. The irregular sounds remain irregular: し shi + ゆ yu = しゅ shu (instead of syu), ち chi + や ya = ちゃ cha (instead of tya), じ ji + よ yo = じょ jo (instead of zyo). There's a Reddit post with a nice table showing all the available sounds[2].
Now the problem for romanization is this: Should the romanization reflect the irregular sounds in the spoken language? Or should it reflect the regular groupings of the kana characters? づ and ず might both be pronounced "zu", but they come from different linguistic origins, just as "bear" and "bare" do in English. The Hepburn system uses spellings that match the sounds, while the current standard (Kunrei-shiki) uses spellings that match the kana grouping: し si (instead of shi), ち ti (instead of chi), じ zi (instead of ji), つ tu (instead of tsu), じょ syo (instead of sho), etc.
The Hepburn system tells you how to pronounce the word[3] at the cost of being a lossy encoding. For anyone familiar with the Latin alphabet, that's almost always the better choice, and it's nearly universal in the Western world. Kunrei-shiki does better reflect the underlying structure of the Japanese language and its native writing system, which is probably why the Japanese government preferred it. But anyone who wants to learn the language is going to learn the kana almost immediately (it's just a few hours with flash cards), so IMHO that's pretty small advantage.
I deliberately didn't talk about long vowels, glottal stops, the differences between hiragana and katakana, different pronunciations of ん (n), or how to handle ん (n) followed by a vowel, but if you're curious about Japanese romanization those topics may also be of interest to you. I can try to explain more if anyone's curious.
To me, the valuable comments are the ones that share the writer's expertise and experiences (as opposed to opinions and hypothesizing) or the ones that ask interesting questions. LLMs have no experience and no real expertise, and nobody seems to be posting "I asked an LLM for questions and it said...". Thus, LLM-written comments (whether of the form "I asked ChatGPT..." or not) have no value to me.
I'm not sure a full ban is possible, but LLM-written comments should at least be strongly discouraged.
When Quake(world) was released, it was common to play games on dial-up modems, where 250+ milliseconds was a normal ping time. If you played on a distant server, you could easily get over 500 milliseconds or even much worse.
reply