Shimon Krokhmal's blog

I've created an israelli bloggers group on facebook.
if you have a blog and you are from israel, send me a request to join the group :)

Months after shani tagged me for this issue, it's time to pick up the glove, and write a post about it.

a little note on that matter,
i think that if a developer whats to become better, he should aknowelange it mentally to always strive for self improvement.

Things I should do.
to answer that question, i must ask myself what are my goals, where do i see myself in 3-5 years ?
well, as far as i remmember myself, my goal was always to become a solution Architect, the dude that can design "dreams" to reality.
to achive that, you must work your way from the buttom, get femilier with all the bits and bites, design practices, practice software development and after few years in the field, emerge your own opinion about software development process, devolopment methodoligies, and create new consepts.
once you have done all that, you can start becoming an architect.
after defining that, lets ask this question again :
What things should i do?

• read alot about development methodologies, and when/where to apply them (Scrum like development is not always suitable for every organization)
• upgrade my skills to current technologies (.Net 3.5)
• Apply new learnt stuff to daily tasks

Things I want to do

• Write a book on software development (it won't be published in the next year)
• create a perfect development process (is it possible ?)
• enter the BDD world.
  

Things I won't do
as much as it is tempting to leave what i am doing now, and persue my dream becoming a solution architect,
the next few years seems as a good time to gain more expirience at the development section before advancing to the next level.

Tagging this dude :
 Micky Shriber

In the last few weeks, i was doing a deep dive into some development methodologies such as TDD, BDD, and scrum.
what was bothering be about the TDD approach is the concept of designing for testability.
in early stages of my research, i spoke with Nati, a good friend of mine that practicing TDD in his team,
he told me that in order to write practice TDD it is imperative to write testable code.
What is testable code i asked ?
Well, this is not a simple question to answer, roy Osherove has even written a book about that,
from changing the design of your application, like using MVP to an "Inherit & Override" practice .
all these practices make your TDD life easier, but we need to ask ourselves one simple question :
"What is the purpose of your application ?",
seems like a stupid question to raise, but due to the noticeable progress of the software industry towards TDD blindly,
this may affect the software performance/Quality "Just" for making our code testable.

I came across Eli Lopian's article about Stop Designing for Testability, which confirms my concerns about the issue, i Totally agree with him.
testable code has an added value, but must we not forget the real purpose of the application, which is to run best in production environment.

This post is a sort of a reply post to nati's post - Testable code, is it worth it ? regarding that matter.

Testable application is certainly an added value to the development process and to the business as one,
but we must be careful not to make it the main issue of the application.
a great example of how TDD should be done is the TypeMock.Net tool, which allows you coding TDD without affecting the performance and OOP design of the application, in my opinion, this is the way to go the TDD way.

What do you think about this matter ?