bsandert
Joined 11 years ago
Karma
355
Submissions
29
Member since
Sep 29
Recent submissions
Comment · 8 years ago
Comment · 8 years ago
In my experience, knowing when work on some functionality will _start_ plus a rough estimate on effort (talking hours/days/weeks level) is quite acceptable for most stakeholders. It is also far easier to provide, and less likely to be off by an order of magnitude, which some low-level estimates may suffer from.
Comment · 8 years ago
it('sends an email to the user', ...)Comment · 9 years ago
One I've been looking forward to for a while: native notifications on OSX!
Comment · 9 years ago
Vendor lock-in.
Comment · 9 years ago
Please don't fall into the Dunning-Kruger[0] trap by assuming a straightforward task is also easy to perform. These things may very well be complex and include aspects that are not immediately obvious. And even if they don't, even simple code executing simple tasks can be vulnerable to bugs or flawed reasoning without the authors (or tooling) being stupid or naive.
[0]: https://en.wikipedia.org/wiki/Dunning%E2%80%93Kruger_effect
Comment · 10 years ago
Feature-wise it's great but the .com version can be really slow. A simple git push of a few small commits took me about 50 seconds earlier this week.
Comment · 10 years ago
> It's super powerful because word dropping cost nothing to produce and cost a lot to dismiss with proper arguments.
Sounds like you may be referring to the Bullshit Asymmetry Priciple: https://en.wikipedia.org/wiki/Bullshit#Bullshit_asymmetry_pr...
Comment · 10 years ago
This also reminds me of a talk by Maxim Februari at the most recent TEDx Amsterdam[0]. From the description:
The infrastructure of connected things [..] imposes norms on citizens. Not in the form of written laws: the norms are hidden in the design of things. Citizens can’t protest the new laws, or change them, because they do not know them. And because decisions are made automatically, the laws can’t even be violated [..]
[0]: https://youtu.be/qIVTKBeiabI (skip to 2:30 to get to the meat directly)
Comment · 10 years ago
Git only started really clicking with me when I started thinking of most of my actions as graph building and traversals. It also helps to realize that for most intents and purposes, commits in git are immutable and "destructive" actions such as rebase don't _actually_ rewrite history, but rather create a new path in the graph and moves your branch pointer to it, leaving all previous commits intact (though potentially hard to reach and subject to garbage collection).
Comment · 10 years ago
https://en.wikipedia.org/wiki/List_of_eponymous_laws
Which contains (apart from the obvious Murphy's law and Occam's razor) such pearls as the Peter Principle, the Dunning-Kruger effect, and Hofstadter's Law. 20+ tabs guaranteed!
Comment · 10 years ago
Not specifically about this prediction, but he touched on the uncertainty factor in the latest Model Talk podcast episode: http://fivethirtyeight.com/features/how-much-uncertainty-is-...
Comment · 10 years ago
That one and the Christmas Special were the two episodes that kept me up at night.
Comment · 10 years ago
What also floats on water?
Comment · 10 years ago
To me this is a form of the Dunning-Kruger effect[0], where only somewhat informed people estimate the cost of a "0.1" (or POC) release without considering the famous "unknown unknowns" which may involve scaling, billing, 3rd party integrations, etc.
[0]: https://en.wikipedia.org/wiki/Dunning%E2%80%93Kruger_effect
https://github.com/lodash/lodash/issues