Live data from Hacker News

Viewing profile — genericsteele

genericsteele

HN member
Joined
Sat, Mar 05, 2011, 9:00 PM UTC
HN karma
73
Public activity
33 items

About genericsteele

Web contractor. http://iamericsteele.come

Recent public activity

  1. comment
    Comment #7617124

    But then how could I monetize it? I don't think I could run adverts on someone else's service?

  2. comment
    Comment #7617097

    Yes, but I think it would be fun to gamify it somehow.

  3. comment
    Comment #7617079

    Idea: StackOverflow for comebacks I've always had a hard time coming up with a good comeback in conversations. It would be great to have a site where I could post a situation and h…

  4. comment
    Comment #7617021

    Idea: A paid, members-only app where people can post and discuss their ideas.

  5. comment
    Comment #7511133

    SEEKING WORK - Rails MVP and Testing Consulting | Philadelphia, PA | Remote http://iamericsteele.com hi@iamericstele.com ----------------------------------------- MVP Ruby on Rails…

  6. comment
    Comment #7380926

    That's the best of both worlds. I'm going to give this a try.

  7. story
  8. comment
    Comment #7324516

    SEEKING WORK - Rails MVP and Testing Consulting | Philadelphia, PA | Remote http://iamericsteele.com hi@iamericstele.com ----------------------------------------- MVP Ruby on Rails…

  9. comment
  10. comment
    Comment #7018931

    1) is pretty hard, but I'm tackling some basic strategies to adding tests to an untested mass of code. 2) is the entire reason why I'm writing the book. Building a testing habit is…

  11. comment
    Comment #7018715

    Yeah I did. 1) Inheriting someone else's bad code and habits is a huge reason to throw testing out the window. It's really frustrating and always comes with a "We'll write tests in…

  12. comment
    Comment #7018237

    A year ago, I would have agreed with you. There's nothing stopping you from building a successful product without writing tests. Since I built the habit of writing tests, though, I…

  13. story
  14. comment
  15. story
  16. comment
    Comment #5419647

    Sorry about that. It lazily checked for two characters before the @ instead of one. It should work now: http://whatdoitest.com/

  17. comment
    Comment #5419054

    Fixed. Thanks.

  18. comment
    Comment #5418875

    Yes! Michael Hardt's tutorial is the culprit for me as well.

  19. comment
    Comment #5418753

    Computers don't understand english very well. It's easier for us to learn to talk to them, than to teach them how to understand us. DSLs are helpful for some, but sometimes they ge…

  20. comment
    Comment #5418674

    "For me it was a simple decision: If I want community support, I need to be using the tool the community is actually supporting." Truth. And the community is really split on this o…

  21. comment
    Comment #5418627

    My theory is that new Rails developers spend more time learning how to test than what to test. This article isn't necessarily about which framework is better, but more about which …

  22. comment
    Comment #5418448

    OP here. MiniTest::Spec is great, and knocks out two of my complaints in the article: * Expectations are readable and writable * The docs are very easy to digest: http://bfts.rubyf…

  23. story
  24. story
  25. comment
    Comment #5338138

    This is great. Two weekends ago I did the same type of migration using Linode and Capistrano. Heroku taught us what we should expect from a platform, and it seems like, as a commun…