lancerkind

9 ms·

31.
Ask HN: What Does “Being Proficient” at TDD Look Like?
2 points by lancerkind 8y ago|0 comments
32.
Why Devs Don’t TDD, an IT Drama
4 points by lancerkind 8y ago|0 comments
33.
by lancerkind 8y ago
It’s a container, which has its own networking and process containment. (You can list the processes running and you will only see your own process running in the container.) You get to build and configure your container using the command li
34.
by lancerkind 8y ago
Test Automation Strategy Series https://agilenoir.biz/series/agile-thoughts/ 001 Build a solid pyramid 002 Microtests at the base of the pyramid 003 Macrotests at the top of the pyramid 004 The Pyramid's secr
35.
Test Automatiom Strategy(agilenoir.biz)
1 points by lancerkind 8y ago|1 comments
36.
Architect disses TDD
1 points by lancerkind 8y ago|0 comments
37.
Science Fiction becomes a WORD
1 points by lancerkind 8y ago|1 comments
38.
by lancerkind 8y ago
The Test Driven Development series continues. Visit and listen to these insightful, easy to understand, and entertaining episodes about TDD. At Agile Thoughts, we work hard to be Portlandia friendly. ;-) https://agilenoir.biz&#x
39.
The TDD Undoer
1 points by lancerkind 8y ago|1 comments
40.
SciFi Thoughts podcast
4 points by lancerkind 8y ago|0 comments
41.
by lancerkind 8y ago
The static typing makes mocking harder (Java, C#). Working in Javascript makes mocking so easy you don’t need a mocking framework. TDD is an awesome practice in all languages, strongly types or not.
42.
by lancerkind 8y ago
I played a bit with mock driven development (I think this is the same as mockist). I so for haven’t found that valuable other than as a kata for learning a new mocking framework. @walligaotr Have you found mockist useful?
43.
by lancerkind 8y ago
Agreed. Well said and good points.
44.
by lancerkind 8y ago
Agreed: * Step 1) (macro) ATDD one or more acceptance criteria * Step 2) (micro) TDD your code to get a macro test to pass.
45.
by lancerkind 8y ago
Nice! That’s is the best workflow for me too. Your basically working from big picture downward or said another way: outside in. To do so otherwise creates more risk. I feel the bottom up approach leaves me exposed to discover bad news late
46.
by lancerkind 8y ago
Lol. Absitinence only sex Ed has nothing to do with TDD. Nor is it fundamentalism. It’s a waste of time to ponder as no real conclusions can be made from slapping the fundamentalism label on TDD. Better to just have an open mind and give i
47.
by lancerkind 8y ago
Nice idea to use defect injection to test the automated tests.
48.
by lancerkind 8y ago
There are test frameworks for every tier of any application on any platform. People are getting it done. Testing pixel presentation is a problem. Today, Automated macro tests can’t describe in a program how the UI should look before the UI
49.
by lancerkind 8y ago
It’s best to have both micro tests (TDD) and macro tests (Acceptance Tests, which if you write acceptance tests first, is referred to as ATDD). TDD refers to micro tests. ATDD is what you should say to communicate clearly what your doing. S
50.
by lancerkind 8y ago
:-) I actually enjoy writing well crafted code that does test and production functionality. Still, I admire your spirit. Just don’t join my team. ;-)
51.
by lancerkind 8y ago
None of those tests will silently fail. That’s their point for existing. They complain when the code stops operating as the developer designed it to work. Integration testing is valuable. It just isn’t scalable to the whole code base (bec
52.
by lancerkind 8y ago
It’s a false equivalence to equate TDD to religions as the effects are observable and measurable with TDD. In contrast, none of my loved ones have contacted me from the afterlife nor has any diety ever responded to my exhortations.
53.
by lancerkind 8y ago
Brilliantly said!
54.
by lancerkind 8y ago
I do this too in cases where I’ve got an “extreme” amount of learning to do. (Learning a new language, a library, or something I’m trying to make work just simply won’t do I break it down into a tiny test). This isn’t my usual TDD workflow
55.
by lancerkind 8y ago
I like your points about when working with a new developer and how it creates intermediate goals. Are you Pair programming when doing this?
56.
by lancerkind 8y ago
Nicely said @voodootrucker. And I agree with @Tashoecraft. Lots of people get value from TDD. Unfortunately, some don’t and assume it’s the TDD process that’s broke. Its not the tool’s fault. It’s also understandably difficult (though not
57.
by lancerkind 8y ago
Regarding your first paragraph. It sounds like your mixing up the TDD workflow with ATDD. ATDD uses a requirements level view (macro test) and those concepts are usually well known before starting development. So you can write those tests
58.
by lancerkind 8y ago
This is tough to do in a listening medium. Episode 12 covers a simple example that expresses the workflow and give you the general idea. https://agilenoir.biz/podcast/012-an-example-of-doing-tdd/ Getting a copy o
59.
Why Developers don’t TDD: a podcast series(agilenoir.biz)
43 points by lancerkind 8y ago|106 comments
60.
by lancerkind 9y ago
Some software languages or platforms are easier to do TDD in than say proprietary computing "appliances" in proprietary languages. You've mentioned Python, which is a pretty flexible language and conducive to doing TDD. Do yo

More ›