If you're learning to write, I'd recommend looking up the official stroke order. You can just google "Hangul stroke order" and find plenty of guides. And then, just practice writing in a notebook a lot.
2,059 karma · joined July 22, 2010
jon@jonb.org
meet.hn/city/kr-Seoul
Socials:
- x.com/jbaudanza - github.com/jbaudanza
Interests:
AI/ML, Mobile Development, Open Source, Programming, Startups
---
If you're learning to write, I'd recommend looking up the official stroke order. You can just google "Hangul stroke order" and find plenty of guides. And then, just practice writing in a notebook a lot.
I’m sorry about your father. Reproducing his handwriting would be a beautiful project. What kind of samples do you have from him?
PS: I saw your feedback report. 화이팅! :)
Mostly, it was me trying things the naive way, running into problems, and then solving them, usually by copying what Alex Graves did in 2013 (but not always!)
For example, to make things simple I first built the model to simply predict the next x, y direction of the pen. This worked for simple pen strokes, but I noticed the model had a difficult time turning corners.
To fix this, I changed the model to instead predict an Mixture Density Network (Same as Graves). This is explained better in his paper, but essentially, instead of predicting one x, y direction, you predict 10, and then randomly sample one of those predictions. Also instead of predicting scalar x, y values, you predict a parameters for a gaussian distribution, and then sample from that.
It always amazes me how much randomness is involved in intelligence.
> If you get someone to make a few samples and photos, it would be very nice.
I'm in Seoul, if you know anyone who would be interested in collaborating, please send me a note! jon@jonb.org
Adding in some Romanian Deadlifts really forced me to focus on my hamstrings when doing lifts. It helped me breakthrough some plateaus with the conventional deadlift.
I would like to see more language support. For me, I'd like to study Korean
The UX around card navigation needs some work. It took me a long time to figure out that after I chose a smiley face, that I was moving to a new card. This was especially true if the next card is similar to a previous card.
Most devices have noise suppression built in. Do you use RNNoise in tandem with the hardware noise suppression, or do you disable it?
Also, are there any plans to implement this with react-native on mobile? And if so, how would you implement this, since audio worklets and WebAudio aren't available.
I’ve found it’s improved my general recall ability, not just for things I’ve scheduled into a spaced-repetition program.
It’s like the program trains my brain on how to recall things, and then I can use that skill on anything.
I’ve also found that if I slack off my training schedule, my general recall ability gets worse too.
Also, alcohol for sure impacts my memory. I find even one drink will make it harder to recall things
Coinbase, in fact, has made it a rule that all things must be put in useMemo. https://attardi.org/why-we-memo-all-the-things/
Facebook is working on an experimental compiler called React Forget that will transparently memoize everything for you.
https://www.reddit.com/r/reactjs/comments/rcn5ks/react_forge...
Because there's no JIT, Javascript is slow on mobile, especially on Android. I spend a lot of my creative energy trying to optimize the render function. I often times wonder if I should have chosen Flutter instead.
Each framework has its bullshit you don't discover until it's too late. So, I'm sure if I had chosen Flutter I'd be complaining about something else.. but boy am I tired of stuffing things into useMemo, useCallback, and stressing about the identity of things in dependency arrays.
There's some exciting stuff coming up this year with React/React Native: Hermes, React Native "New architecture", react concurrency mode (although I still don't 100% understand what this is). I hope one of these things improves the current situation.
You may rely on useMemo as a performance optimization, not as a semantic guarantee. In the future, React may choose to “forget” some previously memoized values and recalculate them on next render, e.g. to free memory for offscreen components. Write your code so that it still works without useMemo — and then add it to optimize performance.
I think about this section a lot. If they actually changed useMemo to sometimes "forget" values, it would break so many useEffect dependency arrays (including my own).
I don't know anything about construction. But I do know that bureaucrats love to kick the can down the road, rather than deal with things directly. In this case, that would mean forcing some of San Francisco's wealthiest, and most-influential to demolish their luxury homes.
Politically, it sounds great to say, "Make the corporations pay their share!", but who exactly are we targeting with these taxes? Is it the rich executives? Why not just raise taxes on the rich directly?
I suspect in most cases the tax burden is just shifted onto the lower-income workers or the customers somehow.
Then, 6 weeks ago someone stole my laptop from me while sitting in a cafe in San Francisco. Without thinking, I chased him down and was able to wrestle my laptop back from him. Without the BJJ, I probably would have just yelled at him. Anyway, I'm back at the BJJ studio!
I think such a tool would be complicated to implemented. I was thinking maybe of integrating with tagged template literals somehow. Maybe something like:
db.query(sql`SELECT COUNT(*) FROM users`)
And then some tool could parse the AST to find all the SQL and generate types. await db.query("SELECT user_id, COUNT(*) AS count FROM comments GROUP BY user_id");
I would like a TypeScript object that looks like: Array<{ user_id: number, count: number }>I have no idea if this is a good idea or not. I think we'll probably end up fighting about this for a year and then it won't matter anymore. But, the nerd in me is very excited to get a QR code with a JWT with my vaccination records.