• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
is TDD Dead? System Nature is the anwser!
 

is TDD Dead? System Nature is the anwser!

on

  • 319 views

is TDD Dead? System Nature is the anwser!

is TDD Dead? System Nature is the anwser!

Statistics

Views

Total Views
319
Views on SlideShare
318
Embed Views
1

Actions

Likes
3
Downloads
2
Comments
0

1 Embed 1

https://twitter.com 1

Accessibility

Categories

Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

    is TDD Dead? System Nature is the anwser! is TDD Dead? System Nature is the anwser! Presentation Transcript

    • TDD is TDD DEAD? Diego Pacheco Software Architect | Agile Coach
    • TDD: Missing the Point! is TDD DEAD? Java Rails
    • System Natures Process / workflow Rules / Assessment Algorithmic / Calculations Data Driven IO Driven Network / Latency Analytics Visualization Validation / Startup Utilities / Catalog / Reference
    • System Natures
    • Wrap up! • What's matter is the system natures • That’s will define the most likely key design and architecture • All this will in fact driven the design, arch and language selection • Some Languages and tools are better for one thing than another's • Comparing TDD with Rails and Java is pointless • Kind of system you built with rails is different than the ones in java it should be • There are cases for engineering and there are cases for over-engineering • Startup X Enterprise • It will always have balance in the system and natures with N-Natures • You can kill or remove tests or TDD but when it make sense do Tests/Design you gonna need something else to replace it otherwise you are just reducing not being lean at all. • There are better ways todo TDD like Rich Hickey Design approach but there is a context for that. • The are lack of argument and vision IMHO • Both DHH and Fowler/Beck are right to me, but also blind in some sense • Rails is focused on productivity as a ruby extent for most of cases • Performance/Complexity and productivity are different concerns • The one who focus in doing everything is screed since some things are going into different directions.