1,736 karma · joined October 17, 2014
So I know which I would choose, is what I'm trying to say. Like a band-aid.
If you just do a single lesson braindead as fast as possible so you don't lose your streak, then no, you won't learn a language.
I have to also say that none of the languages I've studied on DL are completely new to me. I have had formal instruction in each at some point in my life. I've noticed certain concepts that would probably not make as much sense to someone who hasn't studied the language or language in general (case, conjugation).
Finally, I have one major complaint about Chinese on DL, which is that after 9 months or so I still see the pinyin full time, which means I never really get a chance to solidify the characters properly. I've already said to myself that I need to practice writing separately. There are other problems, but overall, you're probably getting more out of 10 minutes a day of Duo Lingo than several hours of whatever other mobile timesink you're using.
Edit: I guess I should disclose my comparison, which is a Stihl MS260 that's probably 20-30 years old. Never a problem starting and I'm guessing easier to repair than an electric one.
I always present security as a sliding scale with secure on one side and convenient on the other. Similar to low-cost and convenient streaming services reducing piracy, and then seeing the return of piracy as they become higher cost and less-convenient, any application needs to consider not only how to protect its users and their data, but also how to not drive away users with security measures that encroach into that inconvenient zone.
2FA can definitely approach that zone in a few different ways eg. having to reauthenticate too often, or especially for technical users in situations where account sharing is a reality that isn't going away anytime soon: by not making your secret tokens readily available. It has been evident for years that Twilio was just trying to force vendor lock-in and I've always hated Authy. The desktop app at least gave you some agency (secrets on a device that you own and fully control), but I guess that was too much too ask in the long term.
Aside: there are measures that increase security without affecting convenience (much). Take those first.
Additional Aside to the text file password cowboy: since moving into password managers (first lastpass, now bitwarden) I've found it to be more convenient (usually) and I have a lot more peace of mind about it. Maybe try it?
Nobody wants software quality to be regulated by people who don't know anything about software. So, probably we should be regulating ourselves. It's not an easy problem though. Can you really state a minimum safety standard for software that is quantifiable?
- All tests passing? Not good enough
- 100% test coverage? Not good enough
- AI approved code? ha
I've lived in Georgia for most of my 40 years, and most of these parks I had never heard of until we went there. I think almost every single one has been a really good experience. And it's very affordable for my family of 5. We don't have to go far. They're all a little bit different.
I've seen Yosemite, and the Grand Canyon, and other sites of note in the US. They are really neat, and can be worth the trip. But I'm pretty sure at this point that I'll never even see everything that my home state has to offer in my lifetime, so I'm pretty content to stick to reasonable driving distance.
Adjacent to this issue is the broader issue that rampant capitalism encourages rampant buying of stuff - often stuff that we don't need, and surprisingly often stuff we don't even want. Think Gift Giving culture nowadays. With fewer things to purchase, more effort could go into the important purchases, I would think.
My primary use-case is creating reminders. For this I use (of course), the microphone in the search bar. I guess I'll have to find the next best way. Maybe it will end up being better.
It's also not about writing code. Sure, when using Linux exclusively, sometimes you might have to hack together a little script to make your computer do what you want, but that's really not necessary, especially in the year of our Lord 2023. It's about tooling. So many younger devs that I meet still have irrational fear of the command line. Inability to use built-in documentation (like manpages), and again a fear of trying (because web browsers exist). Worst of all is the lack of understanding that these younger devs have of Unix permissions. We all know the guy who just pastes `chmod -R 777 .` or something from StackExchange. Since most of our production software still lives on Linux, knowing the proper way to configure these environments is valuable (though unfortunately undervalued, in my opinion, since improper configuration can still "work fine").
Using Linux full-time for years will make you more than comfortable. And yes, it probably will take years. You may come to prefer the terminal to most of the GUI wrappers provided in desktop Linux distros. You won't even notice when you come out the other side. You'll realize that everything only seemed like it was 43 commands away because you only knew 2 commands to begin with. Typing the most common commands will be second nature and take less time than moving your hand to the mouse. Anything that does need to be reasoned out and typed slowly you will learn to embed in a script, with comments so you can remember how it works, and that will save you even more time.
Most importantly, in the end you will have the confidence in your abilities to write long, condescending comments on Hacker News. I kid of course, but you will no longer fear tooling (though you may grow weary of it - looking at you nodeJS), and I truly believe that's a more important and difficult skill than reading and writing code of all sorts.
For the article, I'm ok with the message, but the title is just clickbait. You don't need to get offended more, you just need to be aware of when you are and try to figure out why.
If your argument is "your shirt with a picture of Lincoln on it offends me - he was a racist!", then I guess you can just kick rocks or whatever.
P.S. "racist" is lately feeling really close to "communist" of the 50s as far as how effectual it is in describing a person's character. A witch hunt, in other words.
I'm not saying mine is the right answer, but I definitely think it is an answer.
> the intelligence & character of the masses are incomparably lower than the intelligence and character of the few...
I don't think Einstein is comparing the most intelligent individuals to the least (or average) here. Certainly there are individuals who are more intelligent than the average, but I would argue not incomparably so.
I believe he's speaking about the tendency of large groups of people to act more like cattle than people. The intelligence of the mob (and the character, represented by the actions of the mob) are what I see as incomparably lower than that of an individual.
And I think this is indicated by the other shortcomings of 20th century humanity that he passes along. War isn't waged by individuals (or even groups of exclusively idiots and villains). There are a bunch of physiological and sociological variables introduced that make the output of the group stupider and less caring than the output of the individual.
Maybe Xcode makes spectacular use of their own hardware, but do we believe that these optimizations are present in Chrome and Photoshop and Docker and Emacs (hahaha) and whatever NodeJS tooling and probably more that many developers are using at all times? I really, really doubt it. Unless the memory compression discussed here is capable of 50% reduction on average, then it's just a dumb thing to say.
Ultimately your programs all want to have some readily-available bytes in RAM, and most of them don't just cycle out constantly. 8GB is a hard upper bounds on multitasking, and while it might not be our grandpa's 8GB, I really have a hard time believing that it's comparable to 16GB. All this is is beside the point anyway: I switched to desktop like 5 years ago so I could affordably have 64GB and I could never go back. Turns out I don't actually want to take my work home with me, too.
Something that was lost when we moved to modules - the system is still the same, it's just that if you never used the old system (GOPATH) or read the manual, then you might be confused about where things have gone.
Also of note is that vendoring was for a time Go's answer to dependency management and can still easily be done, and is supported by the tooling.