Training Feedback -- 100 entries

Course	Rating	Better prepared	Recommend to Others	Most useful	Concepts v Exercises	Presentation v Discussion	Course improvements	Exercise rating	Exercise improvements	Instructor comments	Start tomorrow	Challenges to applying
TDD for Embedded C/C++	Very Good	Moderately	Yes	I understood the concept of TDD and how it is helpful to reduce time to debug for the bugs later.	Good balance	Good balance	May be more time can be allocated for the training	Very Good	Exercises were good already	Instructor was friendly and tried his best to accomodate every engineer with different expertise.	I cannot because I will need to go through the concepts once more.	I think time pressure	Show
TDD for Embedded C/C++	Excellent	Moderately	Yes	Value of unit testing; and test before you code; and test and code at the same time.	Good balance	Good balance	On Day 1, it's natural for newcomers to have doubts about applying TDD to their existing legacy codebases. Instead of dismissing these concerns, it might help to proactively acknowledge them with a message like: "It's okay to have questions—try TDD hands-on during this workshop first, and by Day 2 or 3, we'll dive into how it fits with legacy systems." This kind of framing could foster more open-minded and engaged participation right from the start.	Excellent	something to consider... The 3rd day exercise was non-intuitive and took a while for me to understand. Then I had to explain it to my test partner as well. I know you explained it all well; but it was unfortunately not enough. Is there a way to make it easier to understand? e.g. one slide- which shows the relationship. "IPRW_CpuUMock.cpp" --> to mock IO Read/write functionality; and it will be used by FlashTest.c, to help test/develop Flash.c " IPRW_CpuUMockTest.cpp" -> is JUST for testing " MockFeatureX" -- and can be used as a reference while developing FlashTest.c	I loved the subtle(ish) sense of humor. I am impressed and delighted with your sharing of the material and even the website access - in case we want others in our team to try out TDD! This is very generous- thank you.	Perhaps. I need to identify a small task where I can write/add unit test - which is low-risk; and perhaps not too many dependencies on the existing legacy code.	We have test framework and unit test and integration tests and automated CI - etc everything in place- so that's not the problem. So there may not be any real challenges except finding a task and start applying the ideas.	Show
TDD for Embedded C/C++	Very Good	Much better	Yes	working with examples	Good balance	Good balance	May be add more languages(C#/Java) with examples	Good	May be add more languages(C#/Java) with examples		yes with our new projects and see how it will work for our team	legacy code	Show
TDD for Embedded C/C++	Excellent	Much better	Yes		Good balance	Good balance		Very Good		James is very knowledgeable and entertaining. I found the course to be very enjoable and inspiring as I've wanted to improve the testing that I do.	Yes, though it is slow at first. Practice is needed to get the process smoother and quicker. There is a large legacy codebase at work though.	A large legacy codebase that is not well suited to TDD. I started with making small test programs for functions to create/test with TDD to get going and as time was limited.	Show
TDD for Embedded C/C++	Excellent	Bring it on!	Yes	I really enjoy the 'Test Doubles and Mocking' module. They both are a very powerful tool to abstract the hardware.	Not enough exercises	Good balance	More exercises each day. Around one hour of exercises is not enough for me.	Excellent	The exercises are good, I don't think they can be improved too much.	James is a very good instructor. He explains very good the concept and makes the training funny.	I think the basics can be applied from the first day, but for the rest of concepts I prefer to deep in them before applying to my day to day.	In my workplace they are (and I am for now) debug-later programmers, so maybe is challenging to adopt this new development paradigm. However, I think that if a good pilot project is developed it will be easy to change DLP to TDD.	Show
TDD for Embedded C/C++	Excellent	Bring it on!	Yes	I took both the self paced and online courses, and I found them both beneficial. I also think that I saw the value of doing the self paced course before the online course. I was already familiar with the course material so I got to spend less time working out the mechanics of what we were doing, and focus on the ideas behind TDD and really nail down what the process is like. One thing that I liked about going through the live course over the self-paced one was the break-out room collaboration time. Have another brain to bounce ideas off works really well I think. I would have liked to see more complex mocks, but I understand our time was limited. Other than TDD as a development practice, I think mocks are going to be the most useful thing that I learned.	Good balance	Good balance	I don't have any complaints. Thanks for offering to continue supporting the attendees, and keeping the content available for so long.	Excellent	They're simply, I think they should stay that way to keep "TDD" as the focus.	You were very enjoyable to listen too, seem like you care about your attendees, and I found your course very entertaining.	Yes! I may be in a different position than some because my company already practices TDD.	I think the biggest challenge for me at this point is that I'm still learning TDD and it's not muscle memory for me yet.	Show
TDD for Embedded C/C++	Excellent	Bring it on!	Yes	Be patient, work on very small safe steps	Too many exercises	Good balance	As the focus on the course is adapted to the atendees skills, I consider that it can perfectly fit to any team, so just keep doing as it.	Excellent	I need more time to go through all the exercises, but the ones followed during the course are fine to me. I hope to cover more exercises along the following year!	Fabulous course. It is recommended not only to developers, but also to those responsible for the development team to exploit the potential of working in small steps without predefined barriers. The course content is very extensive for only 3 days. The important thing is not to complete everything, but to understand the concepts, the good practices, and adhere to the recommended methodology. With James' experience and the ease with which he passes on his knowledge, learning is continuous and entertaining. James' course material and support make it easy for you to keep learning continuously.	Yes, I can. Indeed, I started some time ago, but tomorrow I can improve a lot, by reducing my tests size and by keeping changes more bounded to small tests!	Too many legacy code to understand and to break into smaller compilation units.	Show
TDD for Embedded C/C++	Very Good	Moderately	Yes	Learn the beautiful art of what can we achieve with TDD. First thing first is how to begin with!	Good balance	Good balance	I felt it's bit intense. Maybe spread it for 4 days instead of 3	Very Good	I think they are good with what they are for learning purposes.	Have some interesting stories behind most of the example to keep us curious! Presentations were very good and not monotonous.	No, I think I need to take a step back and visualise everything and see how can I utilise it with what I learned.	I think Integration with existing IDE and make everything work asap as our test team won't understand the reason behind slow progress.	Show
TDD for Embedded C/C++	Very Good	Bring it on!	Yes	"Make the change easy, then make the easy change". Writing a new test, then commenting it out, updating the code to work for the new test while keeping the existing tests working, then reinstating the new test to test the new code.	Good balance	Too much presentation	Maybe fit a shorter exercise later in the day instead of a long presentation and demo session	Excellent	Chances to go further with the exercises, if you are familiar with the basics, instead of working with someone new to the concept	Very good at engaging the audience during presentation and demo	Yes, we embedded several of these techniques already so we are not having to overhaul any processes or preconceptions	Miss-conceptions of people outside the software team that it is a slow or inefficient way of developing.	Show
TDD for Embedded C++	Very Good	Bring it on!	Yes	During the training James drove the point home on what it really means to make small, incremental, changes driven by behaviour-focused tests. This helps us stay focused, solving one problem at a time, and combined with the requirement that we must also make the test fail helps ensure the code works not by accident, but deliberately.	Good balance	Too much presentation	Overall this was a very good course. At times the presentation and/or demos would go on for a bit longer than what I would have hoped, especially towards the end on day 3. Breaking these long sections with an excersise, so say a presentation or demo section does not run longer than 20 minutes will help make the course more interactive and engaging. This is me nitpicking though. Overall there is a good balance. The video recordings are great in terms of content and I enjoyed the humour. Production quality is functional. I would only comment I found the flashing lights in the intro and outro sections a bit disconcerting. It should be possible to achieve the same lightning effect but whithout the entire screen flashing.	Excellent	It's hard to say how the excercises can be improved. The pacing and in-code guidance felt good. I also liked the choise to start with a circular buffer to avoid having too many unfamiliarities at once.	James' delivery of the content and the way he handled the sessions and engaged with the trainees was outstanding.	If we are talking literally tomorrow, then yes but not for work. Main reason being my role (Systems Engineer these days) on the project I'm currently on does not involve writing software (although I'm aware the software team are already employing TDD practices). That said, I'm more motivated to seek a role that does :)	I'm convinced to immediately change the way I write software, and employ TDD both for work and personal use. The key challenge will be how efficient I can be writing tests and skillful in demonstrating the value of TDD to other stakeholders, without presenting the tests as a necessary burden but a key part in making the development process more systematic and efficient.	Show
TDD for Embedded C/C++	Good	Much better	Yes	Seeing the fake it 'till you make it, quickly progressing TDD demo for the circular buffer. Learning about avoiding analysis paralysis and prioritising progress on the big ideas.	Too many exercises	Good balance	Videos were a bit too fast and not clearly enough explained for me. More visuals to point during a number of explanations would have been helpful. Lost me on some areas of the course e.g. end part where trying to test a legacy code unit.	Very Good			Yes	No challenges.	Show
TDD for Embedded C/C++	Very Good	Bring it on!	Yes	The actual process of working with TDD. Beforehand I knew it was about writing tests first but it seems much more powerful/sensible than that.	Good balance	Good balance	My C++ isn't the best and so I did spend a bit of time grappling more with C++ than practicing TDD but that is mainly my fault as this is a C++ course. (as a bonus my C++ is now much better than before the course :) )	Very Good	Perhaps more boiler plating so that I could focus more on writing tests and implementing new features. Gain though, if my C++ was better then this might be much less noticeable.	Really engaging, both in the recorded sections as well as the live bits!	For some parts of what I do. For full-stack components I will need to have a think and some research if TDD can be applied to front end dev work. Perhaps with something like selenium/robot framework etc	Slightly slower initial dev time. The business side might not like this as usually the tests are the first thing to be cut when there is a tight deadline. Doing the tests first/during means that they cannot be cut in the same way. It will need to be proven that TDD is faster overall.	Show
TDD for Embedded C/C++	Excellent	Much better	Yes	Thinking in small pieces and applying it Test Doubles Hardware examples were interesting.	Good balance	Good balance		Excellent			I will start tomorrow		Show
TDD for Embedded C	Excellent	Much better	Yes		Good balance	Good balance	No direct suggestions, created some review remarks during course	Very Good			Yes, these are actionable lessons that I can directly apply in my day-to-day work.		Show
TDD for Embedded C	Very Good	Moderately	Yes	Knowledge of the tools that exist, as well as the beginning of a framework on implementing said tools.	Good balance	Good balance	I'm unsure at the moment. I'm relatively new with firmware and believe that the course was quite helpful.	Very Good	I felt there was often a disconnect between the exercise intent and what the students understood they were to do. Changing the description and/or lead up to the exercises may help clear up some of the confusion, leading to a more productivity.	I felt the instructor was knowledgeable and interested in teaching the class. However, some modification to the way some of the exercises are explained could be useful. Please see previous comment.	Yes and no. Some of the concepts are easy to apply to many situations. Others situations call for more finesse. For instance, how do you test the functionality between to pieces of hardware during integration? It'll often be different in each application and requires some thought. However, the course certainly laid down a decent framework and argument for going down the TDD path.	Firstly, standardization. Getting everyone to standardize on a TDD toolset and application of those tools will be quite difficult. Past that, it's just figuring out the correct method to apply it to the various efforts.	Show
TDD for Embedded C	Excellent	Much better	Yes	As a technical manager, my learning focused on slightly different aspects of the training. The most useful thing I learned was how to justify "unit testing" to my colleagues in the project management department. One way in which we can justify unit testing (over system testing) is by simply pointing out that achieving coverage through system test alone takes exponentially more time and money than testing behaviors module by module (supplemented by integration/system tests, of course).	Good balance	Good balance		Excellent			Internal surveys show that, on a scale from 1-5, the average attendee's confidence went up by +0.7 points in confidence for covering all appropriate edge cases and +0.5 points for developing embedded software when hardware is not available. 3 people, to my knowledge have already set up their test frameworks and are well on their way to adding to their test suites.	Our business is quality oriented, but many of our project managers believe in the fallacy of the iron triangle, where higher quality comes at a cost. This training equipped me with the facts I need to educate them better.	Show
TDD for Embedded C	Very Good	Much better	Yes	TDD philosophy. I am not an embedded programmer but I see how TDD can be applied to any programming.	Good balance	Good balance	Possibly having more time to do the prep-work ahead of the training. Maybe a full week or two, I was trying to tie things up on other/regular work items up to the last minute before training.	Very Good	I would have been interested to learn more about CppuTest the first day. Not nitty gritty details, just more intro on the test syntax expected and why.	James was great, explained things clearly and I enjoyed learning about his why he does things the way he does. Very informative!	Yes, I will investigate other test frameworks since I don't need to use C or C++ for my programs.	I don't foresee any major workplace obstacles.	Show
TDD for Embedded C	Good	Much better	Yes	How to use the testing framework.	Good balance	Good balance	It would be nice if both people could code at the same time for exercises.	Good		The instructor was very good.		Company Security poster. One shot deliverables that do not allow for continuous code improvement. One programmer per project.	Show
TDD for Embedded C/C++	Very Good	Much better	Yes	How to TDD was a new concept for me, so it was probably the most useful concept.	Good balance	Good balance	May a different explanation or more focus of the Test Doubles and Mock hardware section before starting the exercise. It didn't really make a lot of sense until James ran through it.	Excellent		Great job! Excited to see the book when we get it!	I could start and will apply other systems	No active standard of practice is currently established so working through that.	Show
TDD for Embedded C/C++	Excellent	Moderately	Yes	The process for coding with test driven development. I found it useful when we started with semi easy examples to learn the testing process.	Good balance	Good balance	Potentially give more examples to work through. Light scheduler can be hard to navigate at first because we are brand new to it.	Excellent	Give homework or time to look over exercises before the class starts.	instructor was very knowledgeable. You could really tell he knew the material and how to teach it.	no. I would need to do a little research on my own and set up my own test harness. I do believe I could create my own project using TDD.	getting things approved through IT. Getting proper buy in from stockholders.	Show
TDD for Embedded C	Excellent	Much better	Yes	learning how to add spies and fakes to code	Not enough exercises	Good balance		Very Good	simpler examples in the beginning so we feel more confident later on	very patient and helpful	No, I would need to update our existing code to work with testing.	Updating the existing architecture and file structure to accommodate testing	Show
TDD for Embedded C/C++	Very Good	Bring it on!	Yes		Good balance	Good balance		Very Good			Yes! My company is moving towards having a unit test framework already set up on our projects, so it will be fairly easy for me to incorporate TDD into my workflow.	One big challenge is that our embedded compiler is very slow. So I may end up taking slightly larger chunks than would be preferable in a TDD environment in order to minimize compiler usage. Another challenge is that we haven't fully incorporated a unit test framework for our GUI development yet. But this is something we're working on overcoming so I don't anticipate it being a long-term challenge.	Show
TDD for Embedded C/C++	Very Good	Bring it on!	Yes		Good balance	Good balance		Very Good					Show
TDD for Embedded C/C++	Excellent	Much better	Yes	That TDD is an iterative process which can actually help implementing new features faster. Feedback loops should be fast in order to keep developers engaged.	Good balance	Good balance		Excellent		James knows what he is talking about and is really good at engaging the crowd (even if they are Finns who don't feel that comfortable at keeping up the discussion)	You should start today. I could start applying TDD immediately once I start working on some code.	Perhaps the legacy environment makes this hard. Also build times can be limiting factor but those need to be tackled in order to keep TDD going.	Show
TDD for Embedded C/C++	Excellent	Bring it on!	Yes	small steps by steps , more easily to get understand	Good balance	Good balance		Excellent					Show
TDD for Embedded C	Very Good	Much better	Yes	Setting up tests for my code and mocking Hardware.	Good balance	Good balance	Presentations (code) occasionally tended to get "blurry", but may be a problem with my browser.	Good	Unfortunately did not get to do all the exercises and switched directly to our Ceedling test harness	Has a real long experience.	Yes. and I will have to, this is a must have.	We already started using TDD for 2 years, unfortunately I am an old schooler and needed to get hands on first, before getting down to it.	Show
TDD for Embedded C++	Excellent	Much better	Yes		Good balance	Good balance		Excellent					Show
TDD for Embedded C++	Very Good	Much better	Yes	The systematic approach of how to write tests and code together. Also the need for a quick feedback loop.	Good balance	Too much presentation	To me it was not very clear which videos should be watched before the training sessions. This lead to a lot of information that I had already watched being presented again.	Excellent	Sometimes the instructions were not really clear. If this was not intentional to simulate real-world squishy requirements it would be good if the instructions could be improved. Also vim keybindings in code dojo would be nice :)	I enjoyed the presentation and the anecdotes. During excercises I personally would prefer just a nudge in the right direction instead of more in-depth help.	Yes, however, the first step would have to be invested in better setting up our compile-run_test feedback loops.	Mainly build time and code dependencies on a platform that is different from the development platform. Also legacy code that was not designed to be testable.	Show
TDD for Embedded C/C++	Very Good	Bring it on!	Yes	TDD working loop, refactoring, clean tests.	Good balance	Good balance		Very Good	Check correctness of the exercises! There was some misleading instructions in the light scheduler exercises (or comments/videos contradicting the exercise instructions - I mean the "current state" and "what to do" was contradicting). Also there's even no link to cyber dojo in 3.6.		Already started	I guess to me biggest challenge would be helping others to start doing it	Show
TDD for Embedded C/C++	Excellent	Bring it on!	Yes	Firmly going forward with seemingly useless small steps, like for example: hardcoding return values.	Good balance	Good balance		Excellent			Actually I'm already following TDD. From now on I'll be a bit more confident with it.		Show
TDD for Embedded C	Excellent	Much better	Yes	This is the second time taking the coarse and the most useful thing was learning how to do right all the things I learned wrong the first time. I could understand the little minutia that makes a big difference in my understanding of how to do TDD. Interface and decoupling. Testing in isolation. Testing only interfaces not internal code implementation. How to use fakes and spies and what mocks actually do.	Good balance	Good balance	I found a number of Little things, particularly in videos that look like they evolved over time with patches. Not being a C++ user I got a bit frustrated with things C++ introduced and distracting from what I want to learn.	Very Good	Sometimes I did not understand what I was supposed to do. That might just be me though. Hints were helpful and rereading instructions helped.	I enjoy your humor and understanding of what we are faced with. Your knowledge was good. I like seeing that you make the same mistakes we do and did not edit it out to look like you always write perfect code the first time.	I am using it now.	Getting others on board with it. I am responsible for mandating its use. Are group will all be signing up to take this course very soon.	Show
TDD for Embedded C	Excellent	Much better	Yes	The structured approach of TDD and solving problems "one problem at a time".	Good balance	Good balance	Although there have been examples in the course, I would love to see more: "where do I start?". Breaking down a problem into parts and then writing your first test still feels like the hardest part. If you have any suggestions on a good read or course where I could improve this skill, love to hear that. The FFF-part of the course felt a bit overwhelming and took away my "focus" on what I had learned before. So I skipped this part initially.	Excellent		The level and pace of the course was perfect for me. That has to do with the exercises but also with the instructor. As a non-native English speaker the course was easy to follow along and very pleasant to watch. Very happy with the instructor.	Starting today!	- Where to start is a challenge - Legacy code :)	Show
TDD for Embedded C	Very Good	Much better	Yes	Mindset for small iteration cycles Mocking	Good balance	Good balance		Very Good					Show
TDD for Embedded C	Excellent	Much better	Yes	The strategy of only writing code to make a test pass. If you do this well you won't end up with a bunch of test debt and instead will generate functional code in a consistent and manageable way.	Good balance	Good balance	Perhaps if for each concept there was more than one example. For instance, for testing direct inputs and direct outputs only one example was given and that was the circular buffer, maybe another example of testing direct inputs and outputs could be given.	Excellent	No comment.		Yes I have begun integrating TDD into my work as much as possible. Even if I only apply TDD to a small section of my code base I feel a lot more secure about that section of code which allows me to focus on other sections of code.	Remaining calm in the face of tight deadlines and not just starting to write code, instead writing in a TDD fashion. There is also a pressure to produce something that to other team members / clients appears to represent a lot of output, think UI or actuators, however it is very easy to get something to look like it's working and not very easy to get something working robustly that's well architected to be extensible and maintainable. Managing these expectations is difficult.	Show
TDD for Embedded C	Excellent	Much better	Yes	The physics of TDD and how to appropriately strategize when developing using TDD. How to go about what tests to write (ZOMBIES), the TDD micro cycle, and in general learned about writing code proactively and pragmatically in a systematic and simple manner. It is a common misconception to think about TDD as just a means of writing unit tests. In this training, I learned about how tests can drive the implementation of the production code one small step at a time. Overall, I also learned to be proactive with my development approach.	Good balance	Good balance	I believe overall the course was great and covered everything very well. But the legacy code section could be improved further with an example/demo of how to adapt TDD for the new code that gets added to the legacy code. Dragging the existing legacy code to the test environment is a challenge, so I know it's not very straightforward. But I think in most scenarios, the legacy code is tested by other means, in some cases unit tests, but in some cases using functional, integration, and systems level tests. So it would be nice to understand the physics of how to write tests for the new code that gets added to the legacy code.	Excellent	Exercises were great. Maybe could be even more embedded systems focused?	James is great! I absolutely love his calm, fun, and very practical way of presenting sometimes rather difficult to grasp topics. I love how James is very approachable and friendly on top of being a master of the field. I certainly appreciate James and his support as an instructor.	Yes I can. The only issues/blockages I may face would be regarding which tests to write. I know we discussed the ZOMBIES approach, but if we could have a high-level step-by-step; it would do great wonders. Also, setting up the makefiles and test environment could be a blocker.	Adding tests for the new code added on top of the legacy code. The new code somehow depends on the old code and needs to be taken into considerations. The overall dependencies.	Show
TDD for Embedded C/C++	Very Good	Much better	Yes	Using Mocks, Spies and Fakes for testing. This training has reinforced and supplemented what I have learned from reading James' book on TDD.	Good balance	Good balance	Better step by step description of what is expected while doing the exercises (i.e., test requirements). We were often confused on how to start or what to do next even after looking at the vague instructions.	Good		Very knowledgeable guy and good presenter. Takes a very dry topic and makes it interesting and fun.	Yes, I have already started.	None, it is encouraged!	Show
TDD for Embedded C	Very Good	Much better	Yes	TDD helps us reducing bugs by driving the implementation I am testing. This has genuinely surprised me to see the implementation evolved from a "stupid" hardcoded return value, to the actual action I wanted the code to do. If I had to pick one, and because it is funny, I'll do for the ZOMBIES. Although I was skeptical at the beginning of testing "nothing" (the zero case). It sounds counter intuitive to test that at creation nothing happens. Well, this was before really driving the implementation by the tests. And start growing the tests, and then the implementation, with just what we need.	Good balance	Good balance	I think there was enough exercises. It is challenging in 4 hours to have interaction with James, doing exercises, presentation, reviews, so this was a great balance IMO. The gather tower is a really fun way to interact to each other. The dojo site provides a ready to use exercises so we do not need to bother to setup the environment, and let us focus on the concept of TDD. Excellent. Having the book is a must have in my opinion, as it has all the concepts explained in the sessions, but even more. Participating to the class could provide a discount to the attendees.	Very Good	The dojo website makes us focusing on the TDD aspect of it, awesome. I wish there were a more collaborative view embedded in dojo, where I could see the cursor of my peer and we could interact together simultaneously, but thanks to the app gather that was not a need anymore. All the exercises were well guided and concrete. I would have liked to have a better continuity to the exercises: we started with a simple example without dependencies; then a more real life example with dependencies. Yet, I think it would have helped me to have the CircularBuffer in use in the LightScheduler. Given the "octopus" of collaborators mentioned by james, the buffer would be at the very bottom, and the LightScheduler some layers above. But I am not sure now, since I have tests for my circular buffer, how is this impacting my tests for the light scheduler. Does it even matter? That is something I'd have liked to explore.	James is awesome, I could feel is experienced, he is humbled. We did have minor presentation issues, but that's what presentation is, isn't it? I loved the time spent during the sessions, James knows what he talks about, have plenty of stories to be told, and is very clear on the intent of the class. The videos are funny!	I'll start right away! Although my very first application won't be TDD as I have to create the unit tests for a recent legacy code that has been created, so the last session about the legacy code was definitely helpful.	Applying the concept of TDD given the time pressure for deliveries. But we have a really good testing culture at my companies, but only for Hardware in the loop, which tends to be really expensive, time consuming, complex, and does not help much to find the bug early. We do have unit testing, but not every devs do testing, so why not spreading that cultures.	Show
TDD for Embedded C/C++	Very Good	Much better	Yes	The hardware mocking concepts	Good balance	Good balance	The legacy part maybe was a too long and the hardest to follow, probably more hands on in that case would help.	Very Good					Show
TDD for Embedded C	Excellent	Much better	Yes	I learned that if you fix one thing at a time it is easier to work consistent over time.	Good balance	Too much discussion	This course can be approved by stating the level you need to be at in the different languages. For example: Expert at C#, novice at C etc.	Excellent	Not sure they can be improved in terms of content. The exercises where relevant to real world scenarios. What can be improved is having equal amount of exercises for C, C++ and C#.		I can not start tomorrow because i need to practice more with C#.	Not many challenges except finding a usecase that is easy enough to get started with.	Show
TDD for Embedded C/C++	Good	A little	Yes	brainstorm the test, test the target fail, implement/fix the target the retest until the test is success.	Good balance	Good balance	If somehow the learner know a little bit about the syntax/statement of the framework in advance.	Very Good	it is kind of hard the first time to know what the framework statement do. After understand the big picture, then the exercise can be tackle easier, specifically for dependency exercise. If we have a class relationship first, then it is very helpful.		I cannot because my project does not apply TDD.	Division/department/project has to approve applying TDD.	Show
TDD for C++	Excellent	A little	Yes	The Importance of using tests while coding.	Not enough exercises	Too much presentation	More coding sessions for general practice.	Excellent	Smaller groups, longer sessions.	Tremendous effort, patience, and creativity.	Yes	Secret server, no internet resources	Show
TDD for Embedded C++	Excellent	Much better	Yes	The overall workflow of TDD.	Good balance	Good balance		Excellent		I appreciate the hands-on and detailed help James provide for the attendees.	No (due to immediate tasking), but will start as soon as possible		Show
TDD for Embedded C/C++	Excellent	Much better	Yes	The capability and principles of TDD. I am now very familiar with how to move through testing either new code or existing code. I came into this course with little to no knowledge on how to write tests. Now, I can say I feel comfortable in trying to implement this in my code in my projects.	Good balance	Good balance	There is a lot of prep work that we do have to do when going into this. However, I know due to the time constraints and nature of this course, it's not easy to fit everything in. I think either a longer training time would be great. But, there is also a self-paced option that is offered as well, so not complaining much either.	Excellent	N/A	James was pretty clear in giving instructions. So clear that even the exercises were still a good step by step process into achieving your goal. This would eventually translate to what I can do in my own code.	I could. I am currently writing up some unit testing for our code in my project right now. The only problem right now is mainly because it is code that I did not work on directly. Already looking through it I know that it will be difficult to create good testing.	Challenges are that a lot of the code that I would work on are already established. Main thing is just getting familiarized with the code to be able to build good tests. That may get lost in translation. I think I would be able to put everything into practice if I was able to have a fresh start. However, that would be a feat in itself.	Show
TDD for Embedded C++	Excellent	Much better	Yes	The whole approach of test driven development	Good balance	Good balance	The only issue I had was not being able to access the course through my work computer	Excellent	the exercises were great		Yes, I think I can start tomorrow with using what I learned today	The only challenges sometimes is any changes to a code net to make an output file to an SD card or burn it to a CD to test it in the hardware we have	Show
TDD for Embedded C++	Good	Much better	Yes	Breaking down code operations to smaller actions.	Good balance	Good balance	Better prep for concepts.	Very Good	Better understanding of the source code used.	Did well explaining the concepts he was sharing.	Yes, one step at a time.	Legacy code with a lot of dependencies.	Show
TDD for Embedded C++	Good	Much better	Yes	Getting used to testing early and often instead of waiting for the very to test and try to solve the errors then.	Good balance	Good balance	I think the course was taught very well, maybe slow down a little bit when presenting the code during the lecture part	Good	Maybe give better instructions on what is required for the exercises, they were a bit confusing at times	Great instructor, very passionate about the subject and always willing to help out.	Yes, I am currently working on a C# project and I am taking it step by step so now I can implement TDD while developing my code.	No challenges that I can think of. I have a good idea of TDD now	Show
TDD for C++	Good	Much better	Yes	Learning about the mock class.	Good balance	Good balance	I do wish that the course was mostly in c# because that is the language that I am familiar with.	Very Good	A tad more guidance with the exercise. Most of the tasking was straight forward, but some was unclear on the instructions.	Instructor is nice and helpful.	Yes because I took the course to apply the teachings in my work.	Making sure that everyone else is on board.	Show
TDD for Embedded C++	Good	Much better	Yes	How to do about testing my code	Not enough exercises	Too much presentation	Start testing from a fresh project and have class follow along. This will help all those who are very new.	Good	Start simpler		yes, because I have to.	Legacy code	Show
TDD for C++	Excellent	Much better	Yes	How to start thinking of test code and how to use it in certain scenario. Surely this is more dominately effective for embeeded system but this can work with framework coding as well.	Good balance	Good balance	The C# actually threw me off using the mocking feature. I did not fully understand how to use that syntax/	Excellent	This was perfect. I do think that having a little more time for the excersize would be perfect as well.	You did awesome. Thank you for the help you provided.	POssibly. I do need to think of how to create stubs to work on the framework and see if we can get the Mock code on there	There is a lot of restrictions within the government on porting in code from online sources	Show
TDD for Embedded C/C++	Very Good	Bring it on!	Yes	Test Driven Development fundamentals	Good balance	Good balance		Excellent					Show
TDD for C++	Very Good	Much better	Yes	I learned how TDD works	Good balance	Good balance		Very Good					Show
TDD for Embedded C	Good	Much better	Yes	How to write test for C/C++ using TDD methods like Zombies	Good balance	Good balance	Some of the code between exercises would change and either be too far back or ahead of the previous spot.	Very Good	I wish the dojo used for the code exercises had better coloring and syntax filling abilities. Definitely made it slower than needed.	Good, he really likes TDD	Yes, Although this may not always be something I can use due to the size of some legacy code. But all new code!	There is a very sizable legacy code work base.	Show
TDD for Embedded C/C++	Excellent	Much better	Yes	Learning that in the long run, TDD provides less buggy code. Also, learning the incremental process of TDD.	Good balance	Good balance	I think if we get more into the real world where you have to deal with legacy code. When I went back to work and did a story I noticed that it first took a long time just to figure out the code first. I think a good exercise would be to take some legacy code and write tests for it to understand the code.	Excellent	If we had to work with some legacy code that was not necessarily from our personal work where there are security issues. But instead the instructor set up some legacy code in an example for us to deal with. That would have been worthwhile.	The instructor had excellent presentation skills.	Like I said, the issue is when you deal with legacy code it is hard to jump in and just perform TDD.		Show
TDD for Embedded C/C++	Excellent	Bring it on!	Yes	The most important thing I learned was a refresher in TDD. I do like having a testing framework and having tests to guide my development. I don't fully agree with the TDD ideology. I think if I was in an organization that fully embraced it I might feel different.	Good balance	Good balance	Extend the course hours and include more material to work on. The web interface is clunky and hard to find stuff and go to gather town and such but did not take away from the material of the class.	Very Good	The exercises were good the way they are. I am not sure I can offer an improvement.	Instructor is good at what he does and how he communicates it.	Yes, since we already use testing frameworks and apply some of the principles of TDD. I am not sure we can implement all the principles only because it's hard to code prior to a design.	Creating tests before we know what to build. At least have some sort of design in place prior to coding.	Show
TDD for Embedded C/C++	Very Good	Much better	Yes	The most useful thing I learned was how to use the tools like fakes/spies/mocks to make testing much better while you are in different stages of implementation.	Not enough exercises	Good balance	I think this course could be improved by having more time working on the exercises in groups. I found the pair programming to be very helpful but we were not able to complete the exercises.	Very Good	The exercises were well thought out and easy to follow. One thing I think could be improved is to maybe break up the group exercises into multiple parts so that we could complete a part, discuss, then continue with the rest.	James is very enthusiastic which makes it easy to pay attention to what he is talking about and following along. Also he was very helpful during the exercises with nudging us in the right direction and leading us onto the TDD path when we went astray.	No. The code we have is legacy and has a large amount of dependencies. On top of that we currently have no means to simulate the hardware for our embedded system. However this paradigm could be applied to future projects.	One challenge is the size and complexity of the existing code. Some parts of the code are decades old and interfaces between C++ and ADA are fragile. Another challenge the time it takes to run tests. With no way to run the code outside of the actual hardware out test feedback loop is in the realm of 10-20 minutes rather than seconds. An ever present challenge is schedule, it will be difficult to carve out enough time for the team to refactor and apply TDD to our existing code.	Show
TDD for Embedded C/C++	Excellent	Much better	Yes	I learned how TDD can facilitate writing code with minimal bugs, in a much shorter time. I also learned that it assures the developer that his code does what he/she thinks it should do.	Good balance	Good balance	I don't see a way the course could be improved, but at least for me it would be more beneficial if it was spread over a longer period. May be having a session every other day, so that trainees can have more time to deepen/solidify what they're learning.	Excellent	I don't have any recommendations for that.	The Instructor is very knowledgeable on the subject matter and he makes every effort to make sure trainees are learning the material.	I can start tomorrow. I feel like I'm in a good position to start applying what I've learned.	No challenges.	Show
TDD for C++	Excellent	Much better	Yes	Its important to do things in incremental steps. Failing tests on purpose will prove functionality of your code when the test passes.	Good balance	Good balance	Less time spent on reviewing the classes' code	Excellent					Show
TDD for Embedded C++	Excellent	Moderately	Yes		Good balance	Good balance		Very Good					Show
TDD for C++	Very Good	Much better	Yes	The ideas for TDD	Good balance	Too much presentation	Maybe after finishing exercises, provide possible solutions	Good			Yes, but would need the entire team to be on board		Show
TDD for Embedded C/C++	Excellent	Much better	Yes	The difference between Spies, Fakes, and Mocks	Not enough exercises	Too much presentation	I would have benefitted from more exercise time. I believe the wingman website would be improved by marking a section yellow when it has been started.	Excellent	More time struggling with the code	very knowledgable	not quite. I would like to finish the exercises before I'm confident	Integrating them into our CI/CD pipeline	Show
TDD for Embedded C/C++	Excellent	Bring it on!	Yes	The most useful thing I learned was how helpful it was to take those little steps in TDD and getting a really fast feedback loop going.	Good balance	Good balance	I thought this course was excellent and cannot at this time think of any improvements.	Excellent	I liked the light bulb exercise but the circular buffer exercise was not as exciting.	I think you did an excellent job explaining the various concepts of TDD and the one on one help the rooms was nice as well.	Yes, I can start tomorrow because the concepts taught in this course were clear and concise and can be easily applied to my current work.	The challenges would be getting team members who did not take this course apple TDD concepts in the same way we did here.	Show
TDD for Embedded C/C++	Excellent	Much better	Yes	Practicing how to break down coding into testable steps	Good balance	Good balance	Even more hands on practice would be great	Excellent		Presented ideas in a clear and meaningful way			Show
TDD for C++	Excellent	Bring it on!	Yes	How spies work under the hood	Good balance	Good balance		Excellent				Large codebase. Already doing TDD, but I need to alter my workflow to write more tests upfront. Hard to test interactions between many components.	Show
TDD for Embedded C/C++	Very Good	Moderately	Yes		Good balance	Good balance		Good					Show
TDD for C	Excellent	Much better	Yes	The different ways to test	Good balance	Good balance	The course was easy to understand and get into	Very Good	The description of some of the exercises were slightly confusing or vague. But not enough that it couldn't be figured out what to do given enough time.	The instructor was very knowledgeable and often provided a lot of advice when we were stuck.	I think it would take time to make changes to my current workflow to get it implemented.	The current workflow my workplace has feels sufficient already.	Show
TDD for Embedded C/C++	Very Good	Moderately	Yes	Learning how to break down tests into a very minimal form and building up to a complete test suit for a particular system.	Good balance	Good balance	Some of the video quality was not to good at the beginning although it was fixed in the end. So perhaps just remembering to set up the video settings before class begins.	Good	N/A	Instructor is very knowledgeable on the topics and definitely has a lot of experience which allow him to clearly convey information as well as relate to the problems students may encounter in their day to day code.	There is definitely a curve to learning how to get away from current non-TDD mindset to a more TTD approach so this is why it can take a bit to start.	Time constraints may come into play for trying to do things in a different manner.	Show
TDD for Embedded C	Very Good	Much better	Yes	I learned that tdd is just the best way for embedded project to grow the ability to know why your code is working and why it is failing makes such a difference in production and deployment of product	Not enough exercises	Too much presentation	It can be improved if it made more beginner friendly	Very Good	they can be improved by providing proper background to the problem we are solving and what are we trying to achieve Also a simpler example leading to complex problem would be a great addition	perfect	i cannot start tomorrow because i have to revise and get clear concepts and read some more material about tdd especially about mock stubs and fakes	too much legacy code and very bad deadlines	Show
TDD for Embedded C	Excellent	Bring it on!	Yes	How to test and develop at the same time	Good balance	Good balance	Perhaps a install guide for cppu test at start of the course, would be nice to follow along natively on machine	Excellent	I work a lot with STM32's so I'd love a specific example using a dev bord perhaps, starting with some desired functionality (using GPIO's, ADC's, SPI or reading and writing to flash). Maybe as a final assignment or something just to get the full embedded dev experience.	James is fantastic	No, there is still a fair amount of work to do to intergrade TDD into the teams workflow and flush out the inevitable kinks with changing workflow.	Being able to accurately emulate the microcontrollers to a point where tests will be an accurate and a reasonable recommendation	Show
TDD for Embedded C	Excellent	Much better	Yes	- Break chain ofhardware dependencies - If you need change later, TDD will help you so much amd make you sure all changes will be what you indeed - You won't too much effort about DLP(debug later programming) - Don't too much think where your driver go. MAke a list what you need and then write test for each and make it pass! You will see your driver is getting complete!	Good balance	Good balance	it may be achieved by telling more topic of TDD before starting to training.	Excellent		Salute to this man! He is absolutely guru of embedded software and TDD! He was so much about the attendees and always answer the questions with patient.	I don't think so because ı need much more information to implement all idea to my code. But at some point, ı think ı have to start it with no need more knowledge about TDD. Sometimes you learn on the way!		Show
TDD for Embedded C++	Very Good	Much better	Yes	Getting hands on guided practice with TDD.	Good balance	Good balance	Maybe push us a bit more prior to the training to have us work out with you what we want to work on in our code prior to starting the training course. I felt like we struggled to select a direction that would also utilize your time well on the last day.	Excellent	No comments		Yes, we have some of our code setup to work with TDD and I understand the process now.	Time getting everything going.	Show
TDD for Embedded C++	Excellent	Much better	Yes		Good balance	Good balance		Very Good					Show
TDD for Embedded C	Excellent	Bring it on!	Yes	How to integrate cpputest into legacy code.	Not enough exercises	Good balance	On days 3 & 4, I felt like more planned exercises would have been useful for engagement.	Excellent	N/A	James is a very personable teacher. The whole team grew to appreciate his knowledge and expertise.	We are well prepared to make TDD a crucial part of our dev workflow.	Team buy-in	Show
TDD for Embedded C/C++	Good	Much better	Yes		Good balance	Good balance		Very Good					Show
TDD for Embedded C++	Excellent	Much better	Yes	The value of TDD	Good balance	Good balance		Excellent			Yes!		Show
TDD for Embedded C++	Very Good	Moderately	Yes	How TDD can help test small portions of code as they are being developed to ensure that bugs are identified and addressed as close to their introduction point	Good balance	Good balance		Very Good			Need to identify the right way to introduce TDD into the target environment (a physical device) where most of our code runs.	Specific target environment with multiple hardware and software interfaces and layers	Show
TDD for Embedded C/C++	Very Good	Much better	Yes	Very good concept of Test Driven Development and the benefit of using it.	Good balance	Good balance	This course is great the way it is planned.	Very Good	The demos and the hints are very helpful for exercises. However, a bit more hints for exercises would also be great - and attendee should choose to go to hint or ask for help.	James did a fanatic job of teaching this course. Thank you, James! I really enjoyed the class. You delivered it well, and I was really my great pleasure to learn so much from you.	Yes, I definitely will start to apply what I learn from this course today.	Working with massive legacy codebase. Refactor will be a challenge.	Show
TDD for Embedded C/C++	Very Good	Much better	Yes	The process of building up new features in very small steps based on tests.	Good balance	Good balance	Maybe more of a focus (exercises) on integrating TDD into large legacy code-bases. Many people wouldn't be able to have "Greenfield" scenarios, and I don't think there was an actual exercise that we had to go through to begin testing in a scenario where there was a lot of legacy code already written.	Very Good	Just as mentioned above, an exercise to add unit testing and begin TDD in a legacy code scenario.	James is enthusiastic and helpful. I also liked his corny programming jokes.	I doubt it. There are many many different modules that our team contributes to, and there are many other people that contribute to those different modules as well. I think our team will have to come up with a strategy to try and implement TDD for our scenario, but it likely will take time to get to that point.	There are many different git repositories that we contribute to, and we are not the owners on many of them. We don't necessarily always have the authority to decide whether unit testing and TDD are options for different repos.	Show
TDD for Embedded C/C++	Excellent	Much better	Yes	The first steps for TDD.	Good balance	Good balance		Excellent			Yes!	At this moment, I'm student and freelancer, so I will start to implement these ideias as soon as possible.	Show
TDD for Embedded C	Very Good	Bring it on!	Yes	Fail the test case first and then make it pass and refactor.	Good balance	Good balance		Very Good					Show
TDD for Embedded C	Excellent	Much better	Yes		Good balance	Good balance		Excellent					Show
TDD for Embedded C	Excellent	Bring it on!	Yes		Good balance	Good balance		Excellent					Show
TDD for Embedded C/C++	Excellent	Bring it on!	Yes	How to write the tests that will drive the development.	Good balance	Good balance		Excellent			On new code yes, on legacy code not yet - that's more trick and requires some more learning.	Legacy code!	Show
TDD for Embedded C/C++	Excellent	Much better	Yes	TDD does not require too much time: you are going to spend that time anyway when you write code and figure out the different scenarios. With TDD you get to keep that work; without TDD you lose it after you are done writing the code. (I was already convinced of the value of testing).	Good balance	Good balance	You can see that it already went through so many iterations...really difficult to find something to improve	Very Good			Yes, even today!	Existing code base with tests: still going to apply the boys scout motto ;-)	Show
TDD for Embedded C/C++	Excellent	Bring it on!	Yes	I found learning about mocks and fakes was incredibly useful. I had taken a course in college that introduced me to the fundamentals of using different debugging techniques and TDD, however mocks and fakes were never discussed.	Good balance	Good balance	Maybe a brief overview of how to setup CppUTest to work on a machine after we have gone through the course using cyber-dojo to get an idea of how to setup/integrate it into a codebase.	Excellent	N/A	James was incredibly helpful whenever questions were asked and at making sure no one got stuck during the exercises.	Yes! I've already begun integrating unit tests into my current project	One challenge is the reliance on some large third-party libraries, such as OPC which could be potentially challenging to test	Show
TDD for Embedded C/C++	Excellent	Much better	Yes	I have experience writing unit tests from previous jobs but never looked at TDD. This class has helped me to learn to focus on a problem by breaking it down to pieces. I love the coverage on fakes and mocks.	Good balance	Good balance		Excellent		He is clear, precise and answers questions very clearly. I love how the class is very interactive. This is probably the best training I've ever taken. It never got boring.	I think I can.	Deadlines.	Show
TDD for Embedded C	Good	A little	Only if improved		Good balance	Too much presentation		Good					Show
TDD for Embedded C/C++	Excellent	Much better	Yes	Testing is crucial. You have to make the initial investment and get your testing in place. You then feel comfortable changing code knowing that you have your safety net around you.	Good balance	Too much discussion		Excellent	A bit more clear instructions. I sometimes had to re-read the instructions multiple times to understand what I'm reading.			The initial time investment of setting up the test environment. From the scrum master/product owner perspective, this time doesn't produce any output to the product.	Show
TDD for Embedded C/C++	Excellent	Much better	Yes	How to slow down and not try to solve every problem at once! Ways to isolate and test specific functionality without having to go through a time-consuming build process.	Good balance	Good balance	I don't think it can be improved past this point. Paraphrasing James, I don't think that the course should be designed to convince naysayers that they should embrace TDD. The combination of the lectures, videos, and exercises leads you to your own conclusions on whether TDD would be right for your project at its current stage; I think that many people will find value in TDD as they are gradually exposed to its concepts.	Very Good	More consistency between the instructions for each exercise and the instructional comments within each exercise codebase. Led to some minor confusion a couple of times.	Knowledgeable and amiable. Quite refreshing to have an instructor who is not only able to answer most of your questions, but also provide the correct level of details to be able to ask them.	Probably not. Our code base is pretty far along and needs to be completed sooner rather than later. I am not sure if the benefits of TDD would be recognized by other members of the product team given they already think the process is slow.	I believe that all employees, not just software engineers, could be convinced of the benefits of TDD when applied to a brand-new or future product. I'm concerned that slowing development down (even with the promise of saving time in the future) would be unpalatable to many employees working on a preexisting product.	Show
TDD for Embedded C	Very Good	Bring it on!	Yes	How to do TDD on Embedded Systems. I didn't know it was possible.	Good balance	Good balance	It was a bit overwhelming the first day, trying to get through the pre-work and find what we need to do. It was better once we got the rhythm of it.	Excellent			I would love to but I probably can't, because I did not get a chance to setup the environment and I need to switch projects for a min.	Getting people on board with it.	Show
TDD for Embedded C/C++	Excellent	Moderately	Yes	mock interface	Good balance	Good balance	it's ok like that	Excellent	it's ok like that	very smart guy!	I already started more than 10 years ago...	no challenges	Show
TDD for Embedded C	Very Good	Much better	Yes	spy/fake design and mock obj	Good balance	Good balance		Very Good		James was very prepared and clear.			Show
TDD for Embedded C/C++	Very Good	Much better	Yes		Good balance	Good balance		Excellent					Show
TDD for Embedded C/C++	Excellent	Much better	Yes	How to mock the hardware and build the code completely off the target.	Good balance	Good balance	If it is not already possible, it would be great to have the live recording of the three lessons, at least the parts related to live explanations and live demo exercises (e.g: Legacy code setup) in order to review some details that I can have missed.	Very Good	I don't think excercises need to be improved, I believe they are a good start point to practice with tdd.	Very nice person, with great experience on programming. He gave us many advices and suggestions and he was able to keep us focused on the lessons all the time.	Yes, I think so, because I have much more information and references to set up a test environment and start to work with tdd.	These ideas are already applied for software, our goal is to apply also for firmware projects.	Show
TDD for Embedded C/C++	Very Good	Much better	Yes	How writing tests helps you better focus the requirements, and the power of pair programming	Good balance	Good balance		Very Good		Great communication skills.	Still need to get a grip on how to integrate CppUTest in Eclipse on Windows. Maybe the day after tomorrow?	Extensive legacy code base, will take some time to make it work with CppUTest.	Show
TDD for Embedded C/C++	Excellent	Much better	Yes	I learned that I can test everything and even Legacy should not haunt me.	Good balance	Good balance	A better code interface where developers can edit at the same time.	Excellent	Perhaps some interface where the coders can edit the code at the same time.	Very kind man. Great speech skills.	Yes, now I have everything I need to skip the worst part of the learning curve.	Tests where we have no control of what can happen. Network management in embedded devices for instance.	Show
TDD for Embedded C/C++	Excellent	Much better	Yes	I learned alot about not just TDD, but also about the do's and dont's of c++/c programming. refactoring, testing in general (testing doubles), rethinking. This course will not only benefit me in the context of TDD, but benefit me everywhere in my development.	Good balance	Good balance	I think that everything was perfekt.	Excellent	As a non C++/C developer I found it very easy to find my way around. I actually finished all the required exercises without any issues and enjoyed doing so.		Im not sure. Its not an easy step to do and it for sure cannot happen from today to tomorrow as it takes a whole rethinking the thinking :). But I for sure will push because I believe and have seen that its benefits are evident.		Show
TDD for Embedded C/C++	Excellent	Much better	Yes	I learned alot about not just TDD, but also about the do's and dont's of c++/c programming. refactoring, testing in general (testing doubles), rethinking. This course will not only benefit me in the context of TDD, but benefit me everywhere in my development.	Good balance	Good balance	I think that everything was perfekt.	Excellent	As a non C++/C developer I found it very easy to find my way around. I actually finished all the required exercises without any issues and enjoyed doing so.		Im not sure. Its not an easy step to do and it for sure cannot happen from today to tomorrow as it takes a whole rethinking the thinking :). But I for sure will push because I believe and have seen that its benefits are evident.		Show
TDD for C++	Very Good	Much better	Yes	of course - how tdd works	Good balance	Too much discussion		Very Good		good, understandable sequence of arguments, some experiences from past work -> good mixture	yes	setup a Test environment will be a big callenge	Show
TDD for Embedded C	Very Good	Much better	Yes	While I have been using NUnit and Ceedling for about a year, the approach to develop the test cases in small steps is something I don't do, is more in "bigger steps". I do believe that TDD is very helpful both during development and in maintenance; I have had to do releases for which I am confident QA tests will fully pass because I already have the test cases in place for the code.	Good balance	Good balance	Personally I struggled a little with the mocks.	Very Good	As mentioned, I did struggle with the mocks, when first started the exercise I didn't know what to do because the concept was not fully understood.		Yes, already using it, it is a matter of slowing down and do little steps.	TDD is largely applied, so there is buy-in. The biggest challenge is that the projects I work in are legacy, so all test cases are implemented (as explained in the training) as new features or changes to the code are done; following this we already have hundreds of test cases covering a lot of the code.	Show
TDD for Embedded C	Very Good	Much better	Yes	I liked the idea of putting the code that interacts with hardware in as contained spot as possible	Good balance	Good balance		Good	I think the problems could have more context. Some times I had code that performed the task required but was different enough I had to redo a lot of it for a continuation of the problem.	In instructor was good	I can start on my next project		Show