Live data from Hacker News

Viewing profile — jfdk

jfdk

HN member
Joined
Thu, Mar 26, 2015, 11:26 PM UTC
HN karma
91
Public activity
28 items

About jfdk

No profile information was provided.

Recent public activity

  1. story
  2. story
  3. story
  4. comment
    Comment #16053524

    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 T…

  5. story
  6. story
  7. story
  8. story
  9. story
  10. comment
    Comment #12254145

    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 …

  11. comment
    Comment #12144507

    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 patt…

  12. comment
    Comment #12091603

    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 wri…

  13. comment
    Comment #12088452

    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) t…

  14. comment
    Comment #12088392

    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. comment
    Comment #12088374

    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 refac…

  16. comment
    Comment #12088202

    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…

  17. comment
    Comment #12088095

    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…

  18. comment
    Comment #12087746

    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 h…

  19. story
  20. comment
    Comment #11770109

    I think you probably need to read 1984 again. Doublespeak is euphamistic political propaganda language.

  21. comment
    Comment #11722465

    My advice would be don't use all the fancy stuff. You really don't need to. A basic HTML page with a few tags will go a long way. And with browsers supporting most of ES6 (WebKit s…

  22. comment
    Comment #11304432

    What does Runnable allow me to do that I can't on CircleCI?

  23. story
  24. comment
    Comment #10910334

    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…

  25. comment
    Comment #9936745

    Back up!