mushishi

10 ms·

61.
by mushishi 6y ago
FWIW, I recently left a project with quite a lot of Angular (2+) code (not massive project but good chunk of code for three developers), and mostly it was a real pleasure as most of the stuff was strictly typed. One extra reason that smoot
62.
by mushishi 6y ago
I would say they help to scope a part of a discussion that clarifies some detail or maybe when giving a link elsewhere, without derailing the mainline of the discussion. It's useful when people arrive in the discussion at different tim
63.
by mushishi 6y ago
This might be a different kind of route you'll want, but if you want to read from the source, look up "Songwriters On Songwriting: Revised And Expanded" which has personal in-depth interviews, including a variety of pop histo
64.
by mushishi 6y ago
Hi, I like this, and found your project at Github. Could you add licence to your project, please! https://github.com/sjvasquez/handwriting-synthesis
65.
by mushishi 6y ago
Could you give me a pointer to a discussion of type soudness in Rust? I recently watched perhaps 3 years old video about Rust where Simon Peyton-Jones asked about this, and Niko Matsakis answered it was ongoing work back then. Couldn't
66.
by mushishi 6y ago
Thank you for writing it. Never really had a glimpse of networking debugging process.
67.
by mushishi 7y ago
Also 8 bit music theory has very solid video essays on varying compositional concepts that are reflected using game music. I actually find his work most consistently satisfying. Neely and Beato are great but lower s/n ratio. Nahre not
68.
by mushishi 7y ago
I didn't notice actual design ideas (apart from the philosophy which sounded good to me). Do you have things on your mind on what kind of actions user can do? The list of what already works seems just the same as in Vim. I'm just
69.
by mushishi 7y ago
If you are curious how databases are implemented, here is a simplistic implementation in clear abstractions https://github.com/komu/ahwen It's a good idea to familiarise with the code in bottom-up order of layers.
70.
by mushishi 8y ago
This seems to be article that gives more information: A Theory of How Columns in the Neocortex Enable Learning the Structure of the World: https://www.ncbi.nlm.nih.gov/pmc/articles/PMC5661005/ Excerpt: A sim
71.
by mushishi 8y ago
Those are great channels. Though my goto channel is Rick Beato's. For orchestral composing Samuel Andreyev's.
72.
by mushishi 8y ago
Yes but it's mind-boggling how complex you can get quite a straightforward system by just piling new requirement changes on top of old without maintaining proper data-model in application, even if database is fine-ish, this results in
73.
by mushishi 8y ago
This demo page is sluggish on a year old Macbook (Chrome). https://dynalist.io/demo/4kpmt51ULD2RgJlcb8IZLZai
74.
by mushishi 8y ago
Our stack is Typescript and Kotlin, and I find handling of null simple and safe, especially in Kotlin there is decent supporting functionality https://kotlinlang.org/docs/reference/null-safety.html With Java we us
75.
by mushishi 8y ago
If you post a video, please let me know, thank you!
76.
by mushishi 9y ago
I'm currently reading "Story: Style, Structure, Substance, and the Principles of Screenwriting" https://mckeestory.com/ I think it agrees on your point.
77.
by mushishi 9y ago
Nice, first time I used a VST. Thank you!
78.
by mushishi 9y ago
You made my day, thank you! I've been using Ableton Live's warping mechanism with Complex Pro settings, and this seems really promising alternative.
79.
by mushishi 9y ago
I liked this explanation of harmony using different levels of musical comprehension (by Jacob Collier, featuring Herbie Hancock) https://www.youtube.com/watch?v=eRkgK4jfi6M
80.
My Life as a Tech Transfer Monad by Erik Meijer (KotlinConf)(youtube.com)
2 points by mushishi 9y ago|0 comments
81.
by mushishi 9y ago
I don't know about mathematical domain, so this might be off-topic but in some cases a legacy code base that works perfectly can be brittle and full of holes and bugs that never manifested themselves because the code not directly inter
82.
by mushishi 9y ago
Thank you for saying that, I'll try not to.
83.
by mushishi 9y ago
Oh, that's informative to know--verifies my own perception--and makes me happy! I appreciate your support. Thank you.
84.
by mushishi 9y ago
That is heartwarming to hear :) You're welcome!
85.
by mushishi 9y ago
Author here. The tutorial succeeds if it gets people to have a superficial comprehension what Vim is about -- especially for those that have been putting off trying it out in a terminal. That's it. It doesn't really try to make yo
86.
by mushishi 9y ago
If by "test suites" you mean automatic testing, then I probably don't agree. The flow goes like this for me: - Make small amount of new code backed by tests in a feature branch - Run some tests locally (not all) - Push to t
87.
by mushishi 9y ago
I don't know people who like verbosity per se. But I can symphatize with people who think that if removal of verbosity introduces other burdens that possibly affect the understandability or refactorability of the code, it is not clear-
88.
by mushishi 9y ago
Logical duplication tends to be bad. But code duplication -- that is not logical duplication (business rules, etc) -- might not be.
89.
by mushishi 10y ago
It is a different language to be sure but why would you say it is better? Isn't there such a many ways to look at the strengths/weaknesses of a language that simply valuing one language over another does not make much sense? (In t
90.
by mushishi 10y ago
What is the reason the MIR was not a part of the compiler right from the start?

More ›