TDD for Embedded C
2018-09-06 19:15:50 UTC
Most useful learnings:
About the experiences which older developers had made. About the problems of bad software and bad architekture and how to develope better software which you can mange afterwards
Concepts v exercises:
Presentation v discussion:
Too much presentation
- Skip the most of challenges and give it as a homework which solutions will be discused at the next day. About one hour for a chalange is a lot of time which could better be used to talk about the experiances we had made during trying to solve this chalanges. Every guy needs different time to understand the task, the setup and needs more or lees time to solve a solution. Maybe it would be cool to make 3 Days in 2-3 Weeks, so that there is more time to solve the challenges and think about questions to discuss. BUT: Its also helpfull if someone monitors you for a short time So maybe a combination about short challenge and homework whould be good.
- Shorter exercises during the trining with steps where you can go if you stuck at one challange. So that you can skip it and move to the next part. Like the exercises about code refecoring. It whould be helpfule if you could jump to the least refectoring chalanges.
- An introduction to each exercise: How is the exercise-project (or call it "challenge project" or "learning project") there set up, which files are there and what will they do (what is there purpose). How is that work what I find there at the starting point (like the other test implementations), what is alrady done and what is your task (in which files) in this challenge.
James had put a lot of knowlage in this course and gave us so much learning stuff for practice it later and learn about other stuff. That is realy cool, this course opens a door! A door to a way full of interesting stuff to learn wich hopefully ends up in better programming skills, more knowhow and better code. THANKYOU.
Because I had to work first on other stuff and drink beer and eat some steaks direktly afterwards. I think this will ends up in "no concentration for programming tomorrow anymore". Sorry. But starting at the weekend is also good :)
Challenges to applying:
How and where to start first. And the experience how to build a testcase for dependency X or Y on my own.
Please give us the number of each textfeld before we write to long comments.... :( Refectoring text to a number of chars is frustrating:D
Legacy code workshop:
Recommend to others: