swanson

65 ms·

1. 571.▲
   by swanson 14y ago

   http://www.youtube.com/watch?feature=player_embedded&v=F...
2. 572.▲
   Email Marketing Bootcamp Weekend (patio11, Customer.io, CopyHackers)(emailbootcampforstartups.com)

   2 points by swanson 14y ago|0 comments
3. 573.▲
   by swanson 14y ago

   Keynote -> upload to SpeakerDeck
4. 574.▲
   by swanson 14y ago

   Another data point: I bought shoes, the guy at the running store said to get a new pair in about 500 miles. I marked down my year-to-date distance traveled in my fitbit and got a new pair when I had gone about 600 miles (some padding for wh
5. 575.▲
   by swanson 14y ago

   "Following strict TDD doesn't prevent this" Actually, following strict TDD does prevent this. You must see a test fail before you make it pass. It goes "Red -> Green -> Refactor" not just "Green -> Refactor". Even if a valid tes
6. 576.▲
   by swanson 14y ago

   Regarding your example using default params - this is the same argument ( http://weblog.therealadam.com/2013/01/03/design-for-test-vs-... ) that DHH is addressing in this blog post. Adam's post does raise an interesting point about the "mas
7. 577.▲
   by swanson 14y ago

   It is one of those fuzzy, learn from experience type of concepts. In my experience, taking shortcuts in tests breeds more and more shortcuts (as less experienced developers look to existing tests as reference). As the shortcuts accumulate,
8. 578.▲
   by swanson 14y ago

   "Tests don't have to be held to the same level of reliability as production code" I personally take issue with that statement. If your tests are not reliable and robust, you will stop trusting them. At the point, why even have tests if you
9. 579.▲
   by swanson 14y ago

   There is a camp in Ruby that thinks monkey-patching (extending or modifying behavior at run time) is a great feature and defining characteristic of the language that should be exploited. There is also a camp that thinks it is powerful, but
10. 580.▲
    My Year in Review: 2012(swanson.github.com)

    1 points by swanson 14y ago|0 comments
11. 581.▲
    by swanson 14y ago

    Heroku with 3 unicorn workers + NewRelic uptime pings
12. 582.▲
    by swanson 14y ago

    Thanks for sharing - I love reading these end of the year reviews.
13. 583.▲
    Punk's Not Dead(wired.com)

    2 points by swanson 14y ago|0 comments
14. 584.▲
    by swanson 14y ago

    Romain Guy - http://www.curious-creature.org/category/android/ Tim Bray - http://www.tbray.org/ongoing/What/Technology/Android/ Cyril Mottier - http://android.cyrilmottier.com/ CommonsWare (probably the top StackOverflow Android answe
15. 585.▲
    by swanson 14y ago

    Here's a pretty good starting point: http://gilesbowkett.blogspot.com/2012/12/rails-developers-sh...
16. 586.▲
    by swanson 14y ago

    I really liked the tone of this post. It presented an argument, offered alternative viewpoints, and articulated why the author thinks his approach is better than alternatives (without overly attacking them). Code samples were provided with
17. 587.▲
    by swanson 14y ago

    The referenced AskHN thread: http://news.ycombinator.com/item?id=4908815
18. 588.▲
    Habit Ramp Up(swanson.github.com)

    3 points by swanson 14y ago|0 comments
19. 589.▲
    Rails Developers Should Take DCI Seriously(gilesbowkett.blogspot.com)

    1 points by swanson 14y ago|0 comments
20. 590.▲
    Personal Time Capsule(swanson.github.com)

    36 points by swanson 14y ago|6 comments
21. 591.▲
    by swanson 14y ago

    Nice easter egg in the footer - clicking the sun/moon icons toggles between a dark and light color scheme. You seem to be missing a subscribe button for the email form in the top-right corner. Additionally, it would be nice to have a page a
22. 592.▲
    by swanson 14y ago

    Yep - it's the same concept. But native support on Github would be cooler IMO :) And I believe it has the same issue with live preview not using your own CSS
23. 593.▲
    by swanson 14y ago

    There are several ways; but I might ways using the current Github UI.
24. 594.▲
    by swanson 14y ago

    Inside a Jekyll repo on Github: New file button = New Post (rich editor) Branch and new file = Draft Edit button (owner) = Edit Edit button (reader) = Submit correction Pull request = Submit Guest post Pull request
25. 595.▲
    by swanson 14y ago

    You save a story by upvoting it. You can access your list of saved stories by clicking on your user name while logged in, then going to "saved stories"
26. 596.▲
    by swanson 14y ago

    I am speaking way over my head - I did work with researchers doing optical metamaterial work one summer as an undergrad, but my knowledge is very naive - but one of the main draws of superlens (hyperlens was the term that I was familiar wit
27. 597.▲
    by swanson 14y ago

    You may want to checkout this short book by Giles Bowkett: http://gilesbowkett.blogspot.com/2012/11/i-wrote-ebook-in-we... It goes into the areas (like AR models) where Rails breaks the classic "OOP Golden Rules" and why it is able to get
28. 598.▲
    by swanson 14y ago

    I think in general models can handle their own validation (especially if you use AR), but I guess the difference is that these validations hit external "services", instead of like a :max_length validation. I agree on the first pass comment
29. 599.▲
    by swanson 14y ago

    Maybe it's because I've been reading about DCI lately, but I think this example could go even further in moving business logic out of the AR model. class GuestbookLibrarian def initialize(rate_limiter, tweeter, spam_checker)
30. 600.▲
    by swanson 14y ago

    Think about it from the client's perspective - using Github issues might be your preferred way of tracking the changes he requests, but it is unlikely his preferred tool. He just wants to email you the changes he wants and have them made -