I'd say that simply being able to read the Francophone news (this is Canada) would give a very different interpretation of how things are seen politically. Total mastery (able to pass for a native speaker) isn't the only valid outcome.
171 karma · joined September 9, 2021
I'd say that simply being able to read the Francophone news (this is Canada) would give a very different interpretation of how things are seen politically. Total mastery (able to pass for a native speaker) isn't the only valid outcome.
"Like all the teachers I spoke to, Zimotti sees Duolingo as supplemental to the kind of deep immersion that language learning requires. But, in his opinion, the time most people spend on Duolingo is time they would otherwise spend on TikTok or watching television, not learning a second language in some more optimal way."
It has got me to the point of being able to look at https://www.nachrichtenleicht.de/ and get someplace. I've had two other efforts at language that never got that far. (Granted that was mostly pre-internet so finding that sort of resource wasn't a fraction as easy.)
Example: 'That’s right. Want to sell stickers with “Rust” on it? T-Shirts? Posters? No sir.'
Realistically, if you depict an old railway spike, nobody will come after you. But if you are profiting off someone else's reputation (via logos, etc), that's a problem; I don't see why that shouldn't be restricted.
I expect that a lot of the motivation for this is to have the ability to close down various kinds of bad actors (not just ankle-biter freeloading with amusement park midway merch). Rust is now big enough and important enough that I see this as a valid concern.
In the NP case, that means access to front-line medical care that might otherwise be inaccessible, vs possibly less capable care.
That doesn't require a lot of training to resolve, I think: mostly along the line of making sure that the NP is professional about knowing when to pass the case on.
The hard part may be creating a culture where this is considered a sign of competence, not the lack of it.
There could be a counterargument, in cross-subsidy: the business of seeing a lot of patients, most with minor and easily dealt with issues, compensates/conserves/cross-subsidizes both the financial and the cognitive load for the one on Tuesday at 11.45 with something nasty.
So these tennis tires, vs what's on that bike now, perform
- worse now when good
- worse than now four weeks out (noted elsewhere, tennis balls decay fast, but
- better than now with punctures today.
Now, this is a 'clever' way to solve that. The long term solution might be 'thorn-resistant tires' (wish we'd known up front -- but they say 'resistant' not 'proof' for a reason), but if you can live with the performance hit in favour of the failure tolerance ('oops, gotta replace six balls today, not like two yesterday), I can see use cases where that's a go.
Yup, should have had a full set of spare tubes. Know that, got spares, but I don't expect three of four tires to go flat on the same day.
I guess the takeaway is, tire innovation still has some fruit to pick.
I disagree that this is (only) about keeping you using the app. When I studied piano, it was critical to work through pieces slowly and in small snippets that you could play. If that meant a quarter the speed marked, so be it (if slower than that, you'd bitten off more than you could chew). Otherwise, you weren't practicing the music, you were practicing your own mistakes. So a 95+ success is really about practicing reading and producing the language correctly as it is about playing games (the games may help ease the conscious boredom of the same thing over and over while the reflexes build).
Also, something like 'the owl' and 'the mouse' may seem trivial and logo-ed, but the language angle is 'le hibou' vs 'la souris' (masculine vs feminine gender) and these don't follow across different languages ('die Eule, die Maus' - both feminine) so repeating this along with exercises that flesh this out has value. I do think that the exercises don't often enough provide the opportunity to get it wrong, but that may be the 95% thing.
I would have expected that the discussion here should be taking that as a given. No paying business is required to take on all suggestions from all customers [1] [2], why would anyone be expected to do that for free?
[1] Paying businesses have whole departments dedicated to translating "tell them to go f--k themselves" to "Dear Sir/Madam: We would like to extend our deepest sympathy for your concerns with our product ... ".
[2] Another popular HN topic is "the client from hell". Would be interesting to have a thread to discuss this thread in that context.
Solution to this is "Tolerance is not a moral precept, it's a peace treaty".
Link below. Quick search, this doesn't look like where this was originally published.
https://extranewsfeed.com/tolerance-is-not-a-moral-precept-1...
Almost every bit of music cataloguing software seems to be CFU for classical. It's built around the "album of tracks" model, without any notion of subgroupings (like a filesystem with no subdirectories), or a notion of multiple performers involved.
Now that being said, cataloguing classical recordings is a pain. The least worst way seems to be by ensemble type, for most "reasonable" collections that gets you most of the way. Not to say other genres aren't, just that you often have dumb things that hinder discoverability, eg., the 'filler' piece that screws up the obvious one place to file the disc.
There's a reason why librarianship is a discipline.
Since when is it the business of US CBP to decide who can work in Canada? That should be up to the Canadian immigration authorities.
So:
1) Default times are required to be randomly dispersed over a 15 minute interval.
This should be entirely non-controversial: If you don't override the default then you really don't care.
2) Selected times are required to be offered as randomly dispersed over a 15 minute interval, with an option to say "no, dammit, do what I said".
This is not too controversial: If the dialog box says "Picking this time instead helps keep your hydro bill low", then a lot of people will say "ok". Uptake doesn't need to be 100%. Controversy will likely be for the device providers, who will have to implement the UI.
Option would be to allow "shift by 5 minutes" (or some such) that still preserves some randomness.
It's a bit eerie that my phone alarm at 0600 is completely synchronized with "This is the World at Six" news intro. I'd hate to be the power utility facing a 20% demand bump over a period of 5 seconds.
That being said, I've seen the same sort of useless results elsewhere (so maybe someone saw this particular case and intervened). I have been told that part of the SEO industry works like "take this sample post and rephrase it with the following keywords and product links". So you get the same warmed-over results on the topic, and it's hard to find the posts that drill deeper.
Correct. However, the intent of Rust is that the code will not fail [1] due to some silly machine thing below your current level of abstraction.
As an example, I'd point to one thing that Rust does that solves a lot of problems: the Vector. This gives you:
- a buffer to load as needed - bounded memory usage ( no more than 2x what's actually needed, and the ability to tailor it) - automatic resizing as needed
IOW, eliminates 'C programmers disease' (eg: #define BUFFERSIZE 1024 // big enough for anything :-) )
I am sick and tired of writing either the tedious resizing stuff by hand, or using a linked list [2] (which in today's world isn't performant: a self-resizing array will deal with locality-of-reference issues much better).
Disclaimer: I've only peripherally used Rust professionally (ie., corporate innovation sessions, self-contained utilities). I have done enough 'fitness exercise' stuff that I'm confident to comment.
[1] "Fail" as in, do something random like start a cryptominer at root-level-privilege. "Fail to compile" is fine, "panic at runtime" is not fine but not worst case.
[2] Opinion: the reason why linked-lists are an example of something hard to do in Rust is because Vectors make them irrelevant, so why bother?
Interesting... I was using one of the Project Euler problems as an exercise for learning Rust; I found that Rc actually improved performance (guess: by eliminating a lot of copies/moves as things went in and out of scope).
My experience is, you don't have a full range of things to rate, and not a lot of actual choices. You may be constrained geographically. So two alternatives: this is what sticks out: "40% of district is parkland, arts and crafts culture, two expensive ferry rides to any kind of significant shopping" vs "retirement community of newcomers, great local hospital, significant unhoused population"... these are the things that stick out, but no common axis to rate them on.
So the questions one are faced with when "shopping for a home town" often look like the ones this site poses.
At the same time, it forces you to make tradeoffs: Cold winter and good restaurants vs MOR politics and walkability. IE, how do I make this decision, doesn't make upfront sense, but I have to. Classic case of "you don't get what you want, but you do get to reject what you don't want".
We (me + SO) recently went on the city-shopping game, the questions here seemed very much the same as the ones we found ourselves confronting.
The questions at the end seemed to be converging on this.
Be nice to (a) give the top ten, not just the top, and (b) for the questionnaire-ee (is that a word) specify upfront "Only in $jurisdiction" (so , .CAN, .US.CA, .EU.FR, etc). I assume this is a constraint on the underlying data...?
- QA is from a problem domain background
- Dev is from a CS/math background
In that case, you can have:
- QA/Dev riff off each other, and collaborate
- The few individuals in the org that have both become the co-ordinators
If it's a collective "we learned from this", that's good.
If it's seriously and organizationally adversarial, that's bad.
A developer's job is to make QA's jobs boring. A QA's job is to catch developers making themselves look stupid. As a developer, I'm happy that QA is better at the job than the developers.
Playing this game in a way that all can laugh over lunch is good for the culture as well as the business.
- way more comfort with 'situational awareness'
- more preference for the e-bike ...
... until I got my regular ("analog" vs "digital") bike kitted out with a mirror too.
Interesting that you like a 'special' (ie., not vanilla symmetric cheap'n'cheerful thing) mouse. I have not yet figured out (after [mumble] years) whether I want a keyboard/mouse setup that fits like a custom glove (the perfect mouse, the perfect keyboard with the perfect layout (colemak or some such), foot pedals for the shift keys, etc (haven't tried that, yet)) or a setup that I can make work for me at any kiosk... or some middle position between those two. Currently I'm at "make it work".
A theremin emulator would make sense, curious about 'standard' applications.
- if it's someone else's machine, it's rude to change the settings
- if it's a public machine, it may also be impossible to change the settings.
- regardless, it's easier to just move it than to mess with the settings as well.
Also, for the front-line staff, the key is to be able to say "don't crab at me, it's the law. Take it up with your MLA".
Personal experience is that I love "Can I talk to your boss". Never lost that one!