Am I the only one unhappy with mechanical keyboards? I find them all tactily unpleasant, plus what's with the stripped down layouts? Basic $10 office keyboards with all the keys and the classic layout are my go to. Keep the chopped down, squished down, expensive keyboards.
Unlike rubber dome keyboards which trigger at the bottom of the stroke, mechanical keyboards trigger mid-stroke. You don't have to bottom out the keys, which reduces shock loading of your fingers. If you actually want to bottom out the keys, you can approximate the rubber dome feeling by using a linear keyswitch modded with a soft o-ring around the stem to cushion the impact.
There are all kinds of mechanical keyboards. Not every one is going to suit everyone's tastes.
> plus what's with the stripped down layouts?
The most common kind of 'squished down' is because it's "small like a laptop keyboard". The common sentiment seems to be: "I don't use those keys often, so I don't need them on the keyboard".
Though there's another kind of small keyboard: small keyboards with multiple thumb keys. Multiple thumb keys then allow the thumbs to do much more than a typical keyboard, & so allow bringing the full functionality of the keyboard to within reach of the hands on home row.
>There is a federal law that prohibits people from communicating with dolphins.
>It’s called the Marine Mammal Protection Act. Signed in 1972 by President Richard Nixon, the federal law was created to protect marine mammals from being hunted, harassed, captured or killed.
>In a sense, talking to or communicating with dolphins could qualify as harassment under the Marine Mammal Protection Act.
>There are two levels of harassment, according to the National Oceanic and Atmospheric Administration. Harassment at one level is considered “any act of pursuit, torment, or annoyance that has the potential to injure a marine mammal or marine mammal stock in the wild.”
>On another level, harassment is defined by the NOAA as “acts having the potential to disturb (but not injure) a marine mammal or marine mammal stock in the wild by disrupting behavioral patterns, including, but not limited to, migration, breathing, nursing, breeding, feeding, or sheltering.”
How do you learn to share what you do, when you're not used to sharing at all? Should one accept that noone will read 99% of what one shares and just use sharing as a way to record and reflect on own process?
> Should one accept that noone will read 99% of what one shares and just use sharing as a way to record and reflect on own process?
Yes, 100%. Almost no one has found either my public code or my writing useful, but the process of writing and documenting has been tremendously useful to help me clarify what I _actually believe_ at that point in time. This is the primary benefit.
That said, a few projects have taken off unexpectedly and clearly helped some folks, and I've received a few cold emails from folks who somehow ended up on my blog, and all have been pleasant conversations!
One thing I recommend is trying to lower the threshold of what is acceptable to publish. Publish scraps, publish "today I learned", publish "look at this stupid thing I discovered" stuff. Gradually your threshold will rise, but one mistake I see people making is the belief that they have to publish finished projects and novel-quality writing in order for it to be worth it. Nothing could be further from the truth.
Yes, and and it might help to have a second stream for those smaller things -- a microblog, notes, or TIL section of your site (I call mine nuggets).
It helps relieve the pressure from full-length blog posts. A place to let yourself drop below a certain level of quality/polish/length. Anything to move beyond a stagnant blog / writer's block!
Just the fact that my Github repos are 99% public forces me to be diligent in what I commit (no secrets, nothing private)
I have like one project with over 10 stars and a bunch of forks, but that's about it. I build stuff for me, not for others. If someone can look at my crap and get inspiration, it's cool but not essential to my happiness.
Some people on the other hand LOVE the "community" bit of it, every single brain fart of them has a fancy landing page, 15 posts about it on different subreddits and substacks and it's basically a yt-dlp wrapper or something. That's not for me.
Yes. The very act of sharing is a form of "rubber ducking" [32] which will help, even if you're Truman and nobody else exists.
And even if nobody else exists, you do [99] and can later look back at your sharing and glean insights, even if "wow look how little I knew and how far I've come".
I think if you make the sharing intentional to specific groups or specific people with high quality work, people will be interested.
So you can biforcate your sharing somewhat. 99% of your content of sharing will not be watched initially, but if you trim it and edit it intentionally well for an audience who care, people will come to see more of what you have.
Many "influencers" share a lot on twitch and then cut up the best part of their stream into a 2 minute video byte for youtube. As an example.
I do exactly the second part of this. Nobody is going to read what I write, so I just write about what I did, how I did it and what I was thinking when I did it. Not everything has to be written as a perfectly cited essay, but often just noting down what you did can be helpful in the long run. Sometimes I've thought of something, remembered that I did something useful and related in the past and dug out an old article to consult my previous thoughts
1. "Nobody" will likely read it. Don't overthink, don't be shy.
2. If you don't post you won't put the effort in to make it good. Finish your thoughts, fix your grammar, add headers and bullets and tags and pictures.
I heard it argued that Germany didn't have the raw resources and production capacity to go for quantity. Especially later in the war. So quality it was.
I suggest reading Len Deighton's Blitzkrieg (among other WW2 books by him) because it goes into unusual detail on the industrial design and resource allocation decisions that went into tank production leading up to WW2.
Except that the "quality" of their tanks was not exactly top notch, worse they used a lot of resources.
At that point it was just a desperate gamble: "if we can make an invincible tank, then it won't matter how few we have", we both know it did not pay off, not even close.
That's not true. They could have standardized on a few rugged platforms -- and in fact, some in Nazi Germany advocated for that -- but their industry and engineering were generally self-sabotaging and a mess.
They actually did standardize pretty quickly. Panzer III and Panzer IV were the workhorses in Russia, paired up with the StuG (which used the Pz III chassis). I think that it's arguable that no production strategy could have led to German success. Had they tried to produce T-34 or Sherman type tanks (and the Panther was kind of intended to be that tank), they still would have been overwhelmed by the sheer number of tanks built buy the Allies. The Soviets at their peak year produced over 29K tanks, with the US contributing around 21K. The Germans maxed out at around 8k.
IMHO, the Soviets alone could have eventually defeated Germany, thought at much greater cost (as if over 20m casualties wasn't already incredible).
Agreed that arguably no strategy could have helped them against the Soviet Union, it was a major blunder going to war with them.
But the Nazis self-sabotaged constantly. The Panzer IV and the Stug III (with the outdated Panzer III chassis) were arguably the closest standard for armor, but they were constantly diverting effort to alternative platforms that were too complex to mass produce and maintain. And the same for other weapons.
Not really, the tanks were both inefficient to operate and inefficient to build (lack of standardization, constantly changing plans, have to redesign every single part..)
Sad to hear about people getting stuck in weak ecosystems.
By the way, I switched from Jellyfin to plain SMB + Nova Player (Android), which has basically the same interface, but no user profiles, and works over SMB, obviously. No transcoding, best format support, and best performance for large files I've found yet for my TCL Android TV.
I mean, for my TV at home where everything is connected with a gigabit LAN, I usually use Kodi on a Pi4, over SMB, with a Logitech KT400 to drive it from wherever I feel like sitting.
It's silent, reasonably self-contained, and is appliance-like to get going (just dump OpenELEC onto an SD card, plug everything in, and then simply begin using it).
Plus, there's two HDMI outputs: One that connects directly to the the dumb TV and sends only video, while the other sends only lossless PCM audio to the once-rather-high-end AV receiver (that gets choked up on more-modern HDMI bitrates).
And that's great for me at my house, with my pile of gear, and with my technical proclivities.
But I'm not my mom, and this isn't my mom's house. :)
WW2 produced some diplomatically-brilliant world leaders. I think you could say that any situation that's headed in an unsustainable direction is being affected by accelerationism. In fact, the old observation "a fool will become a master if he perseveres in his folly" is much about the same thing.
I think accelerationism specifically refers to doing it on purpose. I doubt many of the decision-makers in WW2 were driven by a desire to elevate and support corrupt institutions as much as possible in the hopes that the corruption inherent in the system would lead to a collapse and people would have no choice but to cooperate towards a brighter and more progressive tomorrow.
And anyone that wants to use WW2 as a model for their theory of change is also (I hope) glossing over the abominable death toll. "Once sufficient 10s of millions of people die, everyone will be so horrified and traumatized by the widespread death and destruction that they'll be have no choice but to collaborate to enact the better world I'm picturing," beyond relying on an n of 1 and ignoring the decades of cold war that ensued, is also...hard to argue is worth it.
https://share.google/eQk4xJAJmeVnbLnjz
reply