The grandparent says it’s easier to teach by saying ichidan and godan actually mean “one-step” and “five-step”. That’s exactly what I’m teaching so it can’t be an argument against my article. This is something I not only say, but explicitly show visually with a table — as I have just quoted. From this I conclude the grandparent hasn’t read the article, and is commenting on vibes.
Then the grandparent says something I agree with (don’t force the language into another language) but I don’t think it’s a fair description of what I’m doing. It sure looks like that’s what I’m doing, but I strongly believe that learning conjugation is primarily phonetical (it’s about how it sounds, not kana itself) and therefore romaji is just a better pedagogical choice for someone not already fluent with kana. And no, I don’t buy that you have to put being fluent in kana as a prerequisite. The whole conceit of the article is basically that you can learn almost the entire conjugation system in one evening with zero prior knowledge of the language. That alone justifies the small shortcut I took to get there.
I figured it was alluding to more conventional approaches to learning them. Reads like you’re making assumptions and defending instead of engaging with criticism in good faith.
“Don’t want to sound negative […] I much prefer” reads to me like a comment phrased against the article’s approach. Otherwise why would it “sound negative”? And what I’m saying is that it matches the article’s approach. Thus, the assumption. Where am I wrong or uncharitable?
https://tenki.so is a tabular representation of the 7-day weather forecast across Japan, which I made for traveling opportunistically.
After the JMA updated their 7-day forecast to be harder to read at a glance, I started pulling and processing the data hourly using Cloudflare workers and trying to present it densely and intuitively using Flareact. It’s been fun exercising the limits of workers (streaming XML at first), organizing the data effectively, and playing with visualization… as well as having a great way to pick a destination when a spell of dark weather is approaching home.
Mega thanks for making and posting this. I've been searching for a tool to "destructure" exactly this way... not necessarily down to radicals, but to any part that has meaning by itself.
Thank you for citing your sources too. As others have mentioned, much of the fun of learning is developing the tools, and this thread helps fill a gaping hole in mine.
How is viewing Chernobyl from that angle useful in this context?
The Houston Ship Channel has the potential to become an environmental disaster similar to Chernobyl, but affecting the fourth-largest population and economic center in the US.
It's not hyperbole -- if you drive down 225 and 146 from Houston to Galveston, it feels like you're in the Sonic the Hedgehog Chemical Plant Zone... it just goes on and on at an unbelievable scale. It self-perpetuates partially because expanding existing petrochemical complexes seems to meet less opposition than building new ones.
Representing time with colored spaces decreases information density. Green & red blocks aren't enough -- the primary data, the numbers, are still required labels, and are made smaller to accommodate the new elements.
Shrinking the primary data decreases visibility, so you, with decent eyesight, need to be closer. My grandmother will have an even harder time resolving it.
Visibility hasn't been addressed, but deserves to be in any conversation about signage.
Wcd's quality (most recordings are posted in multiple formats including FLAC and 320 & v0 mp3) is assured -- the community is serious and self-policing about encoding. Is the same true of Soulseek?
UX isn't about who did what first. It's about doing what makes sense for the user, then reapplying it in every scenario that works. Pull to refresh on the iPhone was utter genius and everyone adopted it. No one is saying, "Well Tweetie did that first!"
Also, it seems like a "no brainer" now, but during the development it's easy for these no brainer things to either be ignored or written off as a waste of valuable engineering time.
Same here. When writing instructions about how to install the historious bookmarklet, I had to take screenshots of all the browsers, including the iPhone. I don't think of it as a nice touch, it's integral to people's understanding of how to install it.
I haven't had a single request for additional instructions, ever.
I was surprised that the author was assuming everyone would guess the grid view would do better. It seems completely obvious to me that a list view is better.
