searls

14 ms·

91.
by searls 10y ago
Hi HN! I'm the speaker in this talk. Just a heads up that when I refer to "The Failing Hacker News", that's just all part of the satire. It's all love here!
92.
Video: Make Ruby Great Again(blog.testdouble.com)
59 points by searls 10y ago|6 comments
93.
Testdouble.js vs. sinon.js(blog.testdouble.com)
5 points by searls 11y ago|0 comments
94.
Good_migrations: a gem to prevent Rails from auto-loading app code in migrations(blog.testdouble.com)
5 points by searls 11y ago|0 comments
95.
My favorite way to TDD(blog.testdouble.com)
3 points by searls 11y ago|1 comments
96.
My favorite way to TDD(blog.testdouble.com)
8 points by searls 11y ago|0 comments
97.
by searls 11y ago
That is an incorrect assumption if it's made universally. The answer is that it depends on what you're testing, why, and how. It also means what you mean by refactor.
98.
by searls 11y ago
I'm the author of that article and if anyone has any questions, feel free to ask me. I'm building up the wiki of well-discussed but rarely documented nuances to testing that I think are worth capturing. A lot of these little artic
99.
by searls 11y ago
Hey HN, I actually made this site as a companion to my RailsConf talk yesterday (I'm sure it was humorously confusing out of context). The talk's slides are up here: https://speakerdeck.com/searls/sometimes-a-
100.
by searls 12y ago
Thanks for the concise description. Love to see Team Ember take advantage of the information users are already feeding the existing public API.
101.
by searls 12y ago
I wrote this one so any comments are welcome and I'll try to answer them as best I can!
102.
Healthy migration habits(blog.testdouble.com)
6 points by searls 12y ago|0 comments
103.
Crafting a conference talk.(blog.testdouble.com)
3 points by searls 13y ago|0 comments
104.
by searls 13y ago
Hey HN, I just wanted to thank you for the overall very positive, constructive comment thread. Thanks to you this post got roughly/over ~22k page views and I didn't receive a single vitriolic comment or bitter dissent. All I got w
105.
by searls 13y ago
Wow thanks for the kind words!
106.
by searls 13y ago
+1 for DAS. Gary's great and I think we agree pretty closely on these issues.
107.
by searls 13y ago
I think I'd have to offer that my experience differs. TDD is not at all big-design-up-front, even with this reductive exercise. In fact, most features start very minimally and the tree of dependencies grows over time, just like any sys
108.
by searls 13y ago
TDD as I practice it does, but I think OOP as it's traditionally taught encourages developers to tangle mutable application state and behavior, which leads to all sorts of problems. The more I practice, the more I learn that life is be
109.
by searls 13y ago
Yes I am.
110.
by searls 13y ago
Yeah, the common implications of the word "test" have always been problematic. The BDD movement did a good job bringing that to light, but I didn't want to re-litigate that all in my post just to make a point about semantics.
111.
by searls 13y ago
Apologies for the continued downtime, we're trying to get a CDN in front of the (static apache) heroku app. In the past not having any dynamic language in the background was enough to stay up, but not today apparently.
112.
by searls 13y ago
Time at a white board breaking down a problem is rarely wasted :)
113.
by searls 13y ago
I'm not sure if the current draft says so, but I talked about how the logical units ought to be "pure functions" most of the time at some point.
114.
by searls 13y ago
Yep! Sandi and I get along very well when it comes to these topics :)
115.
by searls 13y ago
Yep. I don't really practice "OOP" anymore because each of my objects are really just behavior with no application state (their only state would be the other behavioral objects they depend on). However, in a classical languag
116.
by searls 13y ago
The trouble with abandoning symmetrical unit tests is that: * The unit is no longer portable and can't be pulled from the context it was first used in (e.g. into a library or another app) without becoming untested. And adding character
117.
by searls 13y ago
This was indeed my motivation for writing the post. I think the next step to take if you agree with my premise is that we need to come together with ideas for how to best teach TDD to beginners/novices. Exercises that promote these
118.
by searls 13y ago
I understand the concern, but I value consistency and discoverability, so symmetry of thing-being-tested to test itself is (so far) the best way I've found to make sure it's dreadfully obvious where a given unit's test is. Th
119.
by searls 13y ago
Apologies for the downtime folks, this post is proving a little too popular for us. Would love to see some folks reaction to the post in the comments
120.
by searls 13y ago
I'm organizing the JavaScript track for Codemash 2014, a large generalist track in Ohio. This post represents my thoughts on what holds back most technical talks and what sets apart great ones.

More ›