MiyamotoAkira

11 ms·

31.
by MiyamotoAkira 5y ago
I only like doing exercise where my brain is active all the time. So sports where there is competition (I play squash), or where i need to keep thinking about it (swimming so I don't drown), or one that doubles as social activity (like
32.
by MiyamotoAkira 5y ago
Love Zulip. Structured conversations are possible, which is what i want for a business setting. Topics are a great implementation. Code syntax highlighting and code playgrounds are nifty
33.
by MiyamotoAkira 7y ago
This keeps bothering me: >7.1 URL structure >Humans SHOULD be able to easily read and construct URLs. >This facilitates discovery and eases adoption on platforms >without a well-supported client library. The URL is ephemeral on
34.
by MiyamotoAkira 7y ago
>> more direct mapping onto manipulating a DAG of commits That would be a leaky abstraction. The fact that is using DAG should be irrelevant. If they find a better way of doing the work, that shouldn't really affect the ux.
35.
by MiyamotoAkira 7y ago
Wait, that says it took around 0.3 billion years, and when there was only single cell life, we have no clue about the biodiversity at that point in time. It cannot compare in time scale, and we have no clue if it can compare on biodiversity
36.
by MiyamotoAkira 7y ago
2015: https://www.martinfowler.com/bliki/MonolithFirst.html
37.
by MiyamotoAkira 8y ago
Sorry, could you please link to the announcement? Agree about the Windows licenses.
38.
by MiyamotoAkira 8y ago
As a user with a HiDPI laptop that needs to connect to non-HiDPI external monitors, Xorg is not reasonable. macOS is way ahead.
39.
by MiyamotoAkira 8y ago
The same that that structural test creates unnecessary coupling there will be other tests that create that coupling as well. It is a learning phase. You will realize that there are things that you can do and things that you can't do wh
40.
by MiyamotoAkira 8y ago
What productivity? I am here on HN
41.
by MiyamotoAkira 9y ago
Furthermore to Klathmon, there is an opportunity cost. Because you don't have the test, changing that method in the future becomes problematic. Is not the bug reappearing, is the refactoring that cannot longer take place.
42.
by MiyamotoAkira 9y ago
I would say that only Haskell (and derivatives) force you to follow most of these rules. Neither Clojure, nor F#, nor Elixir force you into most.
43.
by MiyamotoAkira 9y ago
SOLD!!!!! I will have to add this to my kata collection. That also reminds me of the 8-queen problem. The last solution that I created (C#) years ago did use recursion.
44.
by MiyamotoAkira 9y ago
You are right. If you don't follow most of those rules, you are not doing pure FP. My interest on them was because I was writing production code that felt procedural. The rules are there so you can practice with purpose. Once you go in
45.
by MiyamotoAkira 9y ago
In fact, a colleague that is reading SICP at the moment is the one that basically put the idea forward, as he was going through the whole idea of fold/map/unfold on the book exercises
46.
by MiyamotoAkira 9y ago
The people that talked about the rules at Codurance was none of the people that defined the original rules. We had to "reverse engineer" the thinking, find reasons and then discard, change or let as they were (one of the objective
47.
by MiyamotoAkira 9y ago
Author here. A few have mentioned already, but this is to practice, to force you to understand what FP brings to the table, and lead you in path of discovery. When it comes to production code, you apply what you have learned, and make the d