jshen

76 ms·

931.
by jshen 12y ago
Maybe we mean different things by "separated". I want the app server bundled into the app, not an assumed dependency that the app has on the target environment. Rack in the ruby world exposes an API that ruby web apps build on top
932.
by jshen 12y ago
so why separate the two if there is always 1 app per app server?
933.
by jshen 12y ago
Here's another example that showed up on /r/ruby http://benlakey.com/2014/05/04/testing-is-science/ I don't think I'm overstating it.
934.
by jshen 13y ago
Know of any open source code bases built this way?
935.
by jshen 13y ago
I think his first sentence is a strawman. What I'm tired of from the TDD crowd is that they insist that people are doing it wrong if they don't do to the extreme demand of others. A great example of this is Bob Martin saying that
936.
by jshen 13y ago
I don't think a full test suite that takes 4 minutes is slow, and I don't see much if any value in adding a bunch of abstractions and indirection for the purpose of running the full suite every 5 seconds. I get 99% of the value by
937.
by jshen 13y ago
I'm in the same boat. What are you using for UGC sites instead of Adsense?
938.
by jshen 13y ago
And TDD is of no use to me if it expects me to run my full test suite whenever I change a line of code. If my code isn't decoupled enough to run a subset of tests for a small change then my code is bad so there is no good reason for TD
939.
by jshen 13y ago
"Over the years many people have complained about the so-called "religiosity" of some of the proponents of Test Driven Development. " And Bob is guilty of that religiosity himself. See here https://www.youtube
940.
by jshen 13y ago
It's not slow to test a rails app. See DHH's latest post.
941.
by jshen 13y ago
Is bob Martin a cargo cult practitioner? jump to the 58 minute mark. http://m.youtube.com/watch?v=WpkDN78P884
942.
by jshen 13y ago
Neither of us ever said all TDD folks are cultist. We are both tired of being told that we are absolutely doing it wrong if we don't practice TDD. For an example of people telling us this please see this talk by bob Martin and jump to
943.
by jshen 13y ago
"and management advantages over the historical process of writing them last and has a high correlation with well factored code." Where is the data supporting this claim? I don't believe it is true. "That's it, no do
944.
by jshen 13y ago
Tell me who is a good representative of TDD that has written a lot about it. Where is the cannon of TDD so to speak.
945.
by jshen 13y ago
http://en.m.wikipedia.org/wiki/No_true_Scotsman
946.
by jshen 13y ago
"The reason for DI is that a very common point of change with software is at the interaction between clients and services. Tight coupling at this point of change is usually a design smell." The problem with TDD is that if it is NO
947.
by jshen 13y ago
if you write them after the fact you aren't doing TDD or something as good as TDD. At least, this is what the TDD mob says.
948.
by jshen 13y ago
He ignores the points DHH makes, and then replies with his own snide talking points like a politician on a sunday morning talk show.
949.
by jshen 13y ago
I'd love for him or you to give me an example of an alternative that I should't "feel bad" about.
950.
by jshen 13y ago
That was a terribly thought through reply. It sounds like the sort of bullshit you hear on sunday morning political shows. "Let's pretend I didn't hear my opponents points, and throw back my own talking points which fail to a
951.
by jshen 13y ago
You have it backwards. TDD advocates are the ones claiming that their way is the one true way, that all software should be done their way. Edit: I'm not sure why I'm getting downvoted. Here's a quote from Bob's post that
952.
by jshen 13y ago
That was my point. Testing is not the primary factor that determines the quality of design. I see it making a marginal difference at best. Edit: Stupid autocorrect.
953.
by jshen 13y ago
They are errors of intent and bigotry. Intent on the part of over zealous prosecutors, and simple bigotry of human nature.
954.
by jshen 13y ago
Here's the crux of my argument, quality code is not a function of the number of tests. I tried real TDD 5 years ago and I can assure you code I write today (with less tests) is better than the more tested code I wrote 5 years ago. This
955.
by jshen 13y ago
This may be a confusion due to overloaded words. In rails you often write tests against a real instance of a database using fixtures to load data, and roll back the state after the test. Many TDD type people will shout at you "those ar
956.
by jshen 13y ago
so you don't have a counterexample?
957.
by jshen 13y ago
And this is a great example of how religious/fundamentalist TDD sounds to non believers. Let me briefly summarize the above two comments. "We want our code to be modular, composable, and reusable therefore ... you should write you
958.
by jshen 13y ago
"It's a good read on how not to lead a company" But they are very successful. People say the same thing about Jobs, and again, they are very successful. People that say, "this is no way to lead a company" have to ha
959.
by jshen 13y ago
The documentation on the Go site is really good. You don't need much more than that. The early access book from Manning is really good so far ( http://www.manning.com/ketelsen/ ) but it's only a few chapters fi
960.
by jshen 13y ago
I'm not sure official sources are more trustworthy than unnamed sources on such matters. If G+ has an uncertain future the official source would never say that publicly, I.e. Would never tell the truth.

More ›