Category Archives: _Twitter Archive ๐ค
My audio development journey
Wrote a thread about it:
“Menu reference” shaped solutions
I get asked why I’m into C++ and not Rust.
I get asked why I’m into C++ and not Rust.
Above all, it’s pragmatic. C++ is simply what’s used for the work I aspire to do, and I don’t have time for both.
Beyond that, I still think there’s at least one reason to learn C++ today: out of respect for where it’s gotten us. A lot of lessons to learn from something that powers the world, flaws and all.
And when you do learn Rust, you’ll understand it better. The C++ context will give you a deeper & more intuitive appreciation for why it’s like it is.ย
Rust wouldn’t be what it is without C++. ๐ค
tweet:
git diff can natively detect code movement
An actionable framework for yearly goal planning
Evergreen tweets
Twitter’s length limit is deceptive. At a glance, it suggests that writing tweets should be easy and quick. This is true for superficial tweets, but does not mean all tweets are written quickly and with little effort.
Twitter is actually a platform for concise writing, and writing concisely is harder than writing verbosely. There are certain tweets I spend a lot of time on and it’s shame to have them get lost in my feed. So I’m storing them here.
Continue readingTips for reading the Linux kernel
Tips for effective technical presentations
Wrote a twitter thread about this:
Don’t confuse std::move and std::forward
This was a pretty interesting buggy scenario I found while reading the clang-tidy checks. If you’re writing a function that takes a forwarding reference (what looks like an rvalue reference, but whose type is a template argument), you need to be careful to not call std::move
on it. You need to make sure to call std::forward
instead. Otherwise, you might accidentally trigger a move on an object passed by a caller! This would be confusing, since their object would be moved from, and they never explicitly called std::move
on it.