Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
hzhou321
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
14 ms
·
91.
▲
by
hzhou321
7y ago
The work involved in an effective inline reply is to snip out the irrelevant quote yet still leave enough context for what you were replying to. An inline reply with a large amount of irrelevant quotes so that people have to hunt down your
92.
▲
by
hzhou321
7y ago
Promoting MyDef: https://hz2.org/blog/mydef_general.html .
93.
▲
by
hzhou321
7y ago
> Writing the code out-of-order is the whole point. Yes! MyDef, https://github.com/hzhou/MyDef , is such a system.
94.
▲
by
hzhou321
7y ago
You either feel smart by wondering why people don't use rationals, or feel smart by wondering why people use rationals.
95.
▲
by
hzhou321
7y ago
It is not backward. The keywords to a program are like skeletons to a body and highways to a city. While we agree that the organs or even muscles are more meaningful to a body's function and the business inside buildings off the road a
96.
▲
by
hzhou321
7y ago
> As the article says, climate change won't destroy human civilization. It will devastate part of the population. Climate change is just an inevitable change. To cope with the change, certain portion of people will be sacrificed and
97.
▲
by
hzhou321
7y ago
You are right, I just grabbed the words by the sound of it. A better word is subjective and objective. Easy is a subjective word, while simple is an objective one.
98.
▲
by
hzhou321
7y ago
> Performance is not a priority. I like your outlines so far. It is very interesting -- even if it probably will fail eventually. I am only concerned with this quoted guideline. Performance should always be a priority. Your other guideli
99.
▲
by
hzhou321
7y ago
Thanks. I think I understand the background much better now. When we think easy, we always take the "my" and "now" perspective. When we think simple, we often take the wholesome point of view. Thus the need for different
100.
▲
by
hzhou321
7y ago
Your answer makes sense and is illuminating. It is not easy to keep it simple. The problem here is not that "simple is not easy", it is rather "picking partial and sacrificing/neglecting whole". Since one is only pa
101.
▲
by
hzhou321
7y ago
Until you find a good example, I challenge your understanding :) Similar to my response to another comment, I suspect there is a switching of subjects. It starts with a problem, and the subject is a solution to the problem. Simpler solution
102.
▲
by
hzhou321
7y ago
Good luck explaining "simpler" with modules and vectors :). Simple is defined as not to inter-wine. To understand an axiom is to understand how it "inter-wine" with other axioms to prove certain results. So fewer axioms
103.
▲
by
hzhou321
7y ago
I am yet to appreciate Rich Hickey's now famous "Simple Made Easy". While I agree with his points, I don't understand the significance of it. Simpler is easier than complex, right? Even the title said "simple-made-e
104.
▲
by
hzhou321
7y ago
It starts with an interesting description of problem, but I felt that it took a sharp slope and reached into a bizzare conclusion.
105.
▲
by
hzhou321
7y ago
A refactored code and the spaghetti version are two sides of the same code. Just like any complex object requires multiple viewpoints to comprehend, asserting one perspective is superior to the other is missing the picture. It is a pity tha
106.
▲
by
hzhou321
7y ago
I would think there maybe a "command-line" version of GUI design: supply limited default buttons for common options, but allow user customization. For example, I would love to have the button from author's design but tune it
107.
▲
by
hzhou321
7y ago
Never use an unsigned type for numbers.
108.
▲
by
hzhou321
7y ago
When expression is not pure value -- they also can be control structures -- the arguments for "everything is an expression" is being defeated, right? A control structure is for defining the path -- control flow. The values in a co
109.
▲
by
hzhou321
7y ago
> 1. Everything is an expression. I am not sure this argument is given. Immediately, I see there is a mismatch between what I want to program -- an objective, an algorithm, a procedure, a series of side effects that is outside the axio
110.
▲
by
hzhou321
7y ago
Seems that you are agreeing with imagining and use debugger to verify is a lot more efficient. And for verification, print is more direct than orchestrating the breakpoints and then print with debugger's syntax (or gui navigation).
111.
▲
by
hzhou321
7y ago
Did I say "always"? If I did, that is not the point.
112.
▲
by
hzhou321
7y ago
> Some cases where your imagination could be limited are: > - Code that you didn't write. This has become the norm with software written by a team; and to my stress, I find many coders have given up understanding code that other
113.
▲
by
hzhou321
7y ago
Alternative to what? I guess we are implying different objectives here. To convince someone, appeal to authority might be quick effective. But I don't care about convince you or anyone. I care about reasoning. So I show you how I debug
114.
▲
by
hzhou321
7y ago
When you live in the debugger, you understand your code by seeing how your code work. When you live without the debugger, you have to imagine how your code work. The speed of seeing how your code work cannot match the speed of imagining how
115.
▲
by
hzhou321
7y ago
I agree. The post was full of appealing to authority that gives me disgust. And I do not like and use debugger. I am not going to appeal to authority, so I'll describe how I debug. 30% of my debugging is with pencil and scratch paper.
116.
▲
by
hzhou321
8y ago
I see. So the idea of NULL is the idea of sentinel value. And to express the idea of sentinel value is to create a wrapper around the value and have the wrapper always check for sentinel by default. Is this interpretation correct? So I gues
117.
▲
by
hzhou321
8y ago
So how do you express the idea of null when the language doesn't have null?
118.
▲
by
hzhou321
8y ago
I have been wanting to do something like this and been procrastinating hoping someone will do it for me.
119.
▲
by
hzhou321
8y ago
Best practice is to keep it simple. For example, if the Makefile is written in such a way that lazy set or immediate set doesn't matter, then it is not complex at all. But these facilities are there for achieve logic. Complex logics ar
120.
▲
by
hzhou321
8y ago
He is clueless about what makes a good programming language. The entire article seems to be making up straw men and then knock them down.
More ›