Skip to main content

Code Retreat 2017 retrospective

 In general, this year is much better compared to previous years

There are several important points that I need to write down

Typically, the main reason for me to do code retreat to help developers in the community to expose more to TDD/craftsmanship.

Recently, I asked myself question: “How come it’s not easy to adapt TDD, automated testing which should be the core value of any efficient teams?” I don’t think that people is lazy or people is resistance, I think as the industry, there’s lots of ambiguity in how people should approach TDD (SOLID principles, 4 simple rules of design, etc … are too generic) and agile practices (agile manifesto, etc…)

How can I apply SOLID, 4 simple rules of design into my day to day jobs?

What’s the most important reasons for developers to write automated tests? is it testability design, is it executable documentations?….

what’s the different between integration/component/API tests? should we care?

when I discuss about unit tests with QA, typical answers I get is that it’s programmer tests? IT’S SO NOT TRUE? It does contain many behaviors of the systems, some behaviors are at very low level and business people shouldn’t care about, but I believe MOST OF THE BEHAVIORS could and should be expressed at high level domain language and can be used as executable documentation for different stakeholders such as QA/Non technical people. Should we call those tests as behavior unit tests instead of unit tests?

How can we make the TDD/Refactor/agile practices easier for people to adapt?

  • Maybe, shrink the change?
  • Maybe, there’s lots of things can go wrong but there’s few things that you got to get it right, so script critical moves?
  • Maybe, Looking for bright spot (examples) so people can see the benefits and start small?
  • Maybe, tweak the environments to encourage the right behavior and discourage the wrong behavior?

I think code retreat is one of the good place for me to find the answer to that question.

Comments

Post a Comment

Popular posts from this blog

Yet another interpretation of pyramid tests

In recent conversations regarding automating tests, It seems to me that the common understanding of the team is that the only acceptable automated test case is through the workflow tests through the UI. As far as I know, that’s not entirely correct and per “Pyramids of Automation” chapter 15 in More Agile Testing , I think there are lots of different ways we can automate test cases. I would like to take the opportunity to describe the pyramids of automation again with some thoughts/questions. First, let me try to describe the original pyramid again, and here’s the picture that is worth thousands of words Per the above pyramid from Mike Cohn with some modification in “More Agile Testing”, the lowest level, the unit tests, gets the fastest feedback on every commit which would provide the most benefits. The higher the tests located in the pyramid texts, the slower the feedback and lower profit we would get from the automated tests . “The test automation pyramid is a model intended to guid...
Post a Comment
Read more

Collaborative Learning at Coderetreats

Written collaboratively by: Trung Vo, Bob Allen, Jacqueline Bilston, Christopher Fietz, Llewellyn Falco “… I really liked that there was something there for every level and anytime I would get stuck, there was someone there to help….” — Sara K. What is a Coderetreat? Coderetreat is a day dedicated to allowing developers time to practice their craft. The focus is on practicing skills like Test-Driven Development (TDD), refactoring, and incremental design that is proven to make developers move faster with fewer bugs. It is designed to enable participants to focus on their practice, with as few distractions as possible. The day is made up of several short sessions where we either work in pairs or mobs to solve a small coding problem. Each session, we start new with the same problem; this allows us to focus on the new skill we are learning. What do you get out of it? Coderetreat is an excellent place to learn what you know and what you don’t know. As in life in general, there are always ne...
Post a Comment
Read more

4 hours body summary

The lowest effective dosage the smallest dose that will deliver your intended result to eliminate stored fat , perform a bare minimum to activate a fat-loss cascade of particular hormones to build muscle in tiny or significant amounts, complete the bare minimum to activate local (muscle-specific) and systemic (hormonal) development processes Physical recreation is not exercise. Exercising involves performing MED to produce a targeted change . Ground Zero No Tracking = No awareness = No behavioural change tracking the ratio of body composition and not weight. Ask yourself, " How much is a useful muscle, and how much is useful fat? " four principles of failure proofing make it conscious , beware in real-time and not after the fact. For example, taking a picture of what you're about to eat will make you think twice. Make it a game , measurement = motivation. Seeing any changes in numbers creates a positive feedback loop to make it competitive. The potential loss is a more f...
Post a Comment
Read more