jfdk

6 ms·

1.
Tech Ethics: Addictive technology(joshdover.com)
1 points by jfdk 8y ago|0 comments
2.
Tech's Ethical Negligence(joshdover.com)
2 points by jfdk 8y ago|0 comments
3.
My first six months as an engineering lead(joshdover.com)
2 points by jfdk 9y ago|0 comments
4.
by jfdk 9y ago
I built the guts of this about a year ago to help keep on top of my team's tasks, track sprint planning, and keep on top of pending code reviews. Definitely targeted more towards Tech Leads and Product Managers. I found it useful to us
5.
Show HN: Gitdash - GitHub dashboards for staying on top your projects(gitdash.pro)
2 points by jfdk 9y ago|1 comments
6.
Show HN: Redux-star, redux middleware for easy-to-read, async action creators(github.com)
4 points by jfdk 9y ago|1 comments
7.
Adding Run Length Coding Support to Pilosa(pilosa.com)
10 points by jfdk 9y ago|0 comments
8.
Why the Basecamp way of product management doesn't work for us(medium.com)
1 points by jfdk 9y ago|0 comments
9.
The human side of writing good software(medium.com)
2 points by jfdk 10y ago|0 comments
10.
by jfdk 10y ago
I think this largely depends on how much money you are chasing and your aspirations. I care about money not because I want to have lots of things but because I want the freedom to work on my own ideas (without selling my soul to a VC). A ce
11.
by jfdk 10y ago
This is actually pretty huge. #1 complaint/barrier/hate with getting started with React is all the tooling to do it "the right way" Kudos to React team for bringing a superior pattern and making it actually practical to
12.
by jfdk 10y ago
I've found beforeEach breaks down super quickly as soon as you need to change the input props. Keeping things as purely functional as possible also helps manage complexity when writing tests in a large suite. You don't have to tra
13.
by jfdk 10y ago
If your application has few or very simple interactions then this may make sense. If it does have complex interactions (I consider a text input updating a model field as complex) then I think tests are necessary, especially if working with
14.
by jfdk 10y ago
Good to know, will update the examples when I have time. Not sure I'm a big fan of it though, doesn't seem as clear to a React noob what is going on with ref?
15.
by jfdk 10y ago
JS tests like this are so stupid cheap that we still write them for even the most basic test. Not sure I'm convinced it's worth it yet and I might regret it the first time we refactor a larger reducer.
16.
by jfdk 10y ago
Agree 100%. However if you are using component state you will need to test how interactions impact rendering output on the next render pass. I wouldn't consider that implementation detail since you are only asserting against render out
17.
by jfdk 10y ago
What I should have said is "minimize tools when it makes sense" rather than "when possible." There are some tools that are more trouble than they're worth (for example, I feel this strongly about Jest). Enzyme isn&#
18.
by jfdk 10y ago
We haven't tried Enzyme, but we tend to prefer not adding more JS tools when we don't need to. JS is already a land of wayyyy too many tools and minimizing when possible can be a huge advantage when onboarding new devs onto a proj
19.
Idiomatic React Testing Patterns(gist.github.com)
64 points by jfdk 10y ago|25 comments
20.
by jfdk 10y ago
I think you probably need to read 1984 again. Doublespeak is euphamistic political propaganda language.
21.
by jfdk 10y ago
My advice would be don't use all the fancy stuff. You really don't need to. A basic HTML page with a few <script> tags will go a long way. And with browsers supporting most of ES6 (WebKit supports all of it) you can use all
22.
by jfdk 11y ago
What does Runnable allow me to do that I can't on CircleCI?
23.
President Obama's Keynote at SXSW Live Stream(sxsw.com)
2 points by jfdk 11y ago|0 comments
24.
by jfdk 11y ago
I've always had issues with Mac WMs in the past. They either promise too many features and end up being buggy (because they didn't take the time to solve the problems that Swindler does first) or they're too simple and don&#x
25.
by jfdk 11y ago
Back up!
26.
by jfdk 11y ago
While I think there is some grandiose and hype that gets attached to these fields by the media, you have to recognize that these names represent the end goal of the field, not the current status of where we are today. No, computer vision re
27.
by jfdk 11y ago
I really like the author's analogy to a "communal sausage." Working at a company where our main backend is built on Rails / Ruby, security can always be a bit scary (though has gotten much better in recent history). I&#x
28.
by jfdk 11y ago
http://phabricator.org is actually really great. It started in-house at Facebook. We've been using for the better part of year and I absolutely love it's code and design review tools. It also has a really nice CLI for