HNHacker News
TopNewBestAskShowJobs

MiyamotoAkira

91 karma · joined October 19, 2017

submissionscomments
MiyamotoAkira··on Cannabis use produces persistent cognitive impairments: meta review
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 partner dancing)
MiyamotoAkira··on Why Zulip will stand the test of time
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

MiyamotoAkira··on Microsoft REST API Guidelines
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 REST. That is because you create the documents on the fly. They can be linked or not to things that you store on the datastore. Allows you to easily change around as needed because the URL is not the API. The hyperlinks are the API. The URL is like a memory pointer. You shouldn't care about it.

MiyamotoAkira··on Mercurial RFC of a new extension to directly operate on Git repositories
>> 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.

MiyamotoAkira··on Birds Are Vanishing from North America
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 scale.
MiyamotoAkira··on Software Architecture Guide
2015: https://www.martinfowler.com/bliki/MonolithFirst.html
MiyamotoAkira··on What Makes .NET Core So Special?
Sorry, could you please link to the announcement?

Agree about the Windows licenses.

MiyamotoAkira··on 2018 Desktop Linux Platform Issues
As a user with a HiDPI laptop that needs to connect to non-HiDPI external monitors, Xorg is not reasonable. macOS is way ahead.
MiyamotoAkira··on Unit testing anti-patterns: Structural Inspection
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 while testing.

Once I learned how to test properly, TDD has been helpful, never a hindrance.

In case you haven't read them `Test Driven Development By Example` by Kent Beck and `Growing Object-Oriented Software Guided by Tests` by Steve Freeman and Nat Pryce are great books

MiyamotoAkira··on Slack outage: Connectivity issues affecting all workspaces
What productivity? I am here on HN
MiyamotoAkira··on Never edit a method, always rewrite it?
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.
MiyamotoAkira··on Functional calisthenics
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.
MiyamotoAkira··on Functional calisthenics
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.
MiyamotoAkira··on Functional calisthenics
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 into production code, you can discard them, but with knowledge that it will not be because your OOP skills take over, but conscious decisions.
MiyamotoAkira··on Functional calisthenics
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
MiyamotoAkira··on Functional calisthenics
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 objectives of the write up was to put down those reasons). Explicit recursion did take a while. The reasoning we came with is to learn to use map/reduce functions (do take into account that our group has an ecletic knowdledge of FP and hybrid languages: Clojure, Haskel, Elixir, Scala, F#, ...). Can that binary search tree be converted into a linear search if you rearrange the tree into a list? Yes. Now you can use map /reduce. Is it performant? Most probably not. Are there other ways? Time to discover. Interestingly, most of the katas/exercises on which we are practicing these rules are not heavily algorithmic in nature. Maybe we do need to add some to understand better and modify the "rules" with the new knowledge.
MiyamotoAkira··on Functional calisthenics
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 decisions that you think more convenient. As an example, if you want certain performance gains on F# you do go to mutable state (Phil Trelford did a talk about it). Doesn't matter how pretty/OO/pure is the code if your application doesn't do what is supposed to ;-)
← PreviousPage 2 of 2