Workshop Feedback -- 100 entries

Workshop Duration Better prepared Your workshop experience How to improve Recommended
TDD Workshop (new code)
2.0 Bring it on! It was great, and mind blowing. I just get start on TDD and my mind still not get used to it. The online exercise is really helpful More feedback of exercise and some peer programming will be really helpful. Yes Show
Legacy Code Workshop
0.5 A little It was a bit difficult to follow. Perhaps this is the nature of the beast, but perhaps a friendlier example would have helped drive the point home better. The first time you see something, you'll probably only get about 10-15% of the concepts communicated. A friendlier example may have helped. Yes Show
Legacy Code Workshop
0.5 Bring it on! We covered legacy code in the TDD class, but perhaps this workshop is a different thing. Yes Show
TDD Workshop (new code)
2.0 Moderately Yes Show
Legacy Code Workshop
0.5 Much better Learnt a bit about how to apply the techniques to existing codebase. Yes Show
Legacy Code Workshop
1.0 Much better I think it was really interesting, but it was a shame we spent so much time with the framework setup in windows. Maybe, it could be a good idea to notify the team one week before the course, saying the should prepare a PC with some tools and code. For instance, CppUTest in window with Cywing, cmake, etc. Yes Show
Legacy Code Workshop
1.5 Much better Yes Show
TDD Workshop (new code)
2.0 A little It was nice in general. I only have one note: the 3rd day we spent much time trying to test our legacy code. I saw that it is incredibly hard to resolve the dependencies and I feel that solving this would have been nice. I could not also pay much attention when James used a script to generate fakes. If you wish you can contact to me by e-mail. I think I will need some time to go over all this workshop again to see if I am able to use the tools provided. The TDD concept is clear to me, but I do not know yet about the exploding fakes and when you used a script to generate I do not know what exactly. It is not easy to try to apply the concepts as the explanation continues. If you wish you can contact to me by e-mail. Yes Show
Legacy Code Workshop
1.0 Bring it on! Difficult and frustrating at the beginning, as it took several hours to set up the framework. Afterwards, very satisfying and instructive. Setting up the framework beforehand Yes Show
Legacy Code Workshop
0.5 Much better It would be better to have the framework installed before the course, avoiding to waste time trying to starting it. Yes Show
Legacy Code Workshop
1.0 A little Poor. There was only one person trying to compile the code of our own but there were technical problems Maybe the tool could have been asked to be installed in advance so maybe a week earlier we could have try to be ready for getting as much as possible from the workshop. No Show
Legacy Code Workshop
1.0 Much better It has been a bit frustrating not being completely possible to test our code but wee have understood the idea. If we were told a week earlier what to install for the workshop it would have been better. Yes Show
Legacy Code Workshop
1.0 A little We had problems to set up the test harness, so I think it would be nice to have it installed in a VM. It would also be nice to have a guide to install this environment prior to the course. Yes Show
Legacy Code Workshop
1.0 A little No Show
Legacy Code Workshop
1.0 Moderately Half of the day was spent with one person's code being demo-ed. This took up too much time and I would have benefited more from a full day of trying it on my own and having the instructor available for questions. I spent most of the morning just getting the environment set up and getting a blank test to work, which would have likely gone faster if the instructor was able to answer my questions. We only had 2.5 hours to work on this (since there was more lecture after lunch). Not enough time of individual work to be called a workshop. Provide a shorter demo in the morning. Expect students to spend time getting the environment set up. I needed much more hands-on experience than I was able to do. Yes Show
Legacy Code Workshop
1.0 Bring it on! The beginning of the day went through a classmate's project, but if I'm being honest, the classmate knew what was happening, how to address it, and was plugging away at it without much explanation. At a high level, I sort of got what he was doing, but looking from an application viewpoint, I didn't feel like I could take what he was doing as a how-to to help for when I might need to do that on my projects. The rest of the day was fine, as I was implementing my own testing framework items, and we already had a test hardness, so we made tests to handle the refactor we needed to do. Maybe the instructor could walk through a dedicated legacy code example in the morning, that hopefully can provide a how-to and general guidance principles. Yes Show
Legacy Code Workshop
1.0 Much better Was a little confusing at times as I was distracted by other concerns, but overall I found it useful in understanding mocks (they are used internally here, but I hadnt written one before). Maybe sub groups rather than everyone working on the same code? Yes Show
Legacy Code Workshop
0.5 Much better Yes Show
Legacy Code Workshop
1.0 Much better I wasn't completely sure at first about the workshop actually, because our software is already set-up to run tests on PC, so I wasn't sure of the benefits, and I wasn't sure what code to use. But in the end, I think it was really useful to see how we can set-up a test on a very limited amount of code using the exploding fake script, and how we can get to test the code with very limited changes to the existing code (for instance by catching the log messages). Yes Show
Legacy Code Workshop
1.0 Much better I think the legacy code was not very useful in overall. We did two sessions, one in the morning and another short one in the afternoon. The first one was ok, but I have to say the people did not collaborate much, they did not have the correct mood/energy. The second session was even worst (lower energy/mood) and we indeed found problems with our code but I did not see any hand-on solutions, only suggestions. I think the instructor should "read" the room and try to lift the energy/mood of the people, so more people can collaborate and work together rather than being unprofessional and talk about politics or whatever. To be fair this should be done by the people organizing the workshop but this did not happen in our situation and the trainer will be the one blamed for it! No Show
Legacy Code Workshop
0.5 Much better It appears that unit testing legacy code can be very difficult without restructuring code. But I believe that with shown techniques it can be done. Not sure, maybe cyber-dojo exercise for it... Yes Show
Legacy Code Workshop
1.0 Bring it on! Good discussion on approach. Was interested in the stub generation tool and fake framework - very neat Yes Show
Legacy Code Workshop
1.0 Much better It was quite interesting and provides lots of ideas for how to handle legacy code It would benefits for some more real case examples. Yes Show
Legacy Code Workshop
2.0 Much better I didn't know anything about the workshop content, so everything was new to me. It has been fairly difficult to follow all the details. But summarily I caught a lot of new ideas on designing approach that I really want to pratic them. I would like more pairing exescises Yes Show
Legacy Code Workshop
0.5 Much better was interesting, it get to the point about what port of the production code has to be refactored, how, why Having synthetic/artificial examples of legacy code Yes Show
Legacy Code Workshop
2.0 Moderately I struggled a bit due to missing some of the concepts being used, aside from that it was a good workshop sharing Pre requirements Yes Show
TDD Workshop (new code)
0.5 Much better It was good. New techniques related to refactoring and impact of simple desciplines was seen. It was good to see how to handle business challenges when dealing with legacy code. It's great as it is right now.. Yes Show
Legacy Code Workshop
2.0 Much better Yes Show
Legacy Code Workshop
1.0 Much better Fun and informative, but a bit too slow paced for me during mob programming. Yes Show
Legacy Code Workshop
1.0 Much better Very positive. Yes Show
Legacy Code Workshop
1.0 Bring it on! Sticked to the legacy code refactorization principles and added a bunch of unit tests with non-behavior-changing refactorization to a class without unit test. Think it's good enough. Yes Show
Legacy Code Workshop
1.0 A little Our codebase already has the low-hanging fruit tested for every file, so this workshop was an investigation into how to redesign some of the control flow to allow easier testing Yes Show
Legacy Code Workshop
1.0 Much better Yes Show
Legacy Code Workshop
2.0 Moderately Yes Show
Legacy Code Workshop
2.0 Bring it on! Yes Show
Legacy Code Workshop
2.0 Moderately It was less informative than the TDD workshop that preceded it. More hands-on to our own code. Yes Show
Legacy Code Workshop
2.0 Moderately Discussion on mocking was very useful. I did not feel that the dive through the existing legacy codebase was very helpful. Yes Show
Legacy Code Workshop
0.5 Moderately Best workshop, it help me out the fear to changing the legacy code Yes Show
Legacy Code Workshop
0.5 Moderately Got the overview of the legacy code refactoring process. Need to practice and apply the principles in the real project work. More Legacy code examples would be better. Yes Show
Legacy Code Workshop
1.0 Much better It was good we could have more different examples for exercise. Yes Show
TDD Workshop (new code)
2.0 Moderately It was good . It gave the kickstart to start implementing TDD in current projects. Yes Show
Legacy Code Workshop
1.0 Much better I thought TDD is weird at the first time. But now I am considering how I could make my codes more testable. If I could understand off-target environments more with my legacy code before the course, it could be helpful to take the workshop. Yes Show
Legacy Code Workshop
1.0 Moderately I felt I needed a lot of pre-work to apply TDD. If you prepare the prepared code that can apply TDD in advance, the workshop seems to be more efficient. Yes Show
Story Writing for Embedded Systems Workshop
2.0 Much better Yes Show
TDD Workshop (new code)
2.0 Much better I know how to apply TDD to my work. I know how useful TDD is. . Yes Show
Legacy Code Workshop
1.0 Bring it on! Yes Show
Legacy Code Workshop
1.0 A little Yes Show
Legacy Code Workshop
0.5 Much better Yes Show
Legacy Code Workshop
1.0 Much better We spent some time looking at how to do TDD in matlab James had done some research into the unit test frame work used by matlab. During the session we were managed to use the test frame work on simple test case working and figured out a possible way to handle test doubles. This was interspersed with some theory on handling legacy code. Not sure Yes Show
TDD Workshop (new code)
2.0 Much better This was a 3 day workshop. James, I found that you did an excellent job of presenting your methodologies in a clear and consistent fashion. What's more, the planning of the course combining your view over the course participants development with the pre-designed test sequences, lent itself to a productive experience. Overall, I found the course sequence and planning around the attendee experience, which is to say the tooling availability and usage, to be well considered and fluently applied. Finally, the content of the course was very valuable, and provided a clear communication of TDD methodologies, refactoring, and general productivity management. I found that some heavily opinionated concepts present a distraction. I'll start by stating that it is clear that the presentation of TDD is very intentional and comes from a lot of experience and thought. Nevertheless, no one size fits all, and an unyielding emphasis just distracts. Here are my thoughts on two specific examples. 1. Optimizing error control through minimization on the period of a single TDD cycle is reasonably controversial. A lot of good developers are going to balk at the implication that they should write incomplete and unsound code. I fully understand the reasoning around the technique, but this style simply won't work long term for some developers. Perhaps is a pedagogical tool to insist on this practice, but I for one will compromise on this technique and still get a lot through TDD. 2. Emphasizing classic C programming, then discounting comments as a code smell, forces the developer to pick at the thread, and it doesn't hold up. Classic C is full of comments Yes Show
TDD Workshop (new code)
2.0 Much better It was enlightening to see the techniques applied to the embedded environment. I had been previously acquainted with NUnit and MSTest in the C#.Net world. Not sure. It was pretty robust and focused precisely on the course specifics. Yes Show
TDD Workshop (new code)
2.0 Much better Yes Show
TDD Workshop (new code)
2.0 Bring it on! Yes Show
TDD Workshop (new code)
2.0 Much better It's so interesting. No comment Yes Show
TDD Workshop (new code)
0.5 Much better ---> ACCIDENTALLY ENTERED THIS FORM <--- ---> ACCIDENTALLY ENTERED THIS FORM <--- No Show
TDD Workshop (new code)
2.0 Much better Good experience. More examples. Yes Show
Legacy Code Workshop
1.5 Moderately I felt more engaged during the TDD exercises on the first two days. I had never seen the codebases that were chosen for the Legacy code refactoring exercies so it was all foreign to me and I was not given an opportunity to perform any of the refactoring during these exercises. So my experience was watching other people struggle through errors and write tests for code I had never seen before. The information presented during the lectures was very useful but I primarily learn through practice and repetition and I worry I won't retain a lot of what was presented. Take a more proactive approach that every team is engaged during exercises. Yes Show
Legacy Code Workshop
0.5 Bring it on! It got a bit off tracks but I did come away with a much better knowledge. The remoteness of our connection made it a little impersonal unless you were driving. I don't know how to change this other than recommending more prep time Yes Show
Legacy Code Workshop
2.0 Much better Working on our legacy code? It was very, very painful. It was valuable to fight through the initial "get something small under test." But oh boy. Yes Show
Legacy Code Workshop
1.5 Much better It was difficult getting our items to a point where the workshop was more then "find the dependency issue". And this was after coming in "prepared". I feel like we dropped the ball here. Getting production code under test is not a 'contained' process. It quickly spends a lot of time on items that should be demonstrated once or twice, but then moved along. Spending time prior working with us to get something working in the test harness, then remove pieces to turn it into the above state would have been beneficial for the class as a whole. Yes Show
Legacy Code Workshop
2.0 Much better Good practical experience and a foundation for Real Work tomorrow. Yes. Yes Show
TDD Workshop (new code)
2.0 Much better It was very useful. I have learnt how to improvise on some concepts and techniques. Thank you. Having more hands-on exercises would help. Yes Show
Legacy Code Workshop
1.0 Much better It was interesting to see the concepts applied to our actual legacy code. It brings ideas on how to fix dependency issues when writing unit tests for legacy functionality, it helps to prove that TDD is doable on legacy code (but not pain free). It would help if the group was smaller Yes Show
Legacy Code Workshop
1.0 Much better It was a little tricky to find suitable code to work through for the workshop as it was important to have something that could be made to build with a test harness without too much effort and that did not have so many dependencies that we would be tackling build issues instead of test concepts. It did take a bit of time which may have not been so interesting for some attendees. We would have liked more on the SOLID principles on that day as we already have some good test practices. The approach to getting an existing software module to be extracted from its dependencies in order to be tested independently was very useful and no doubt helped to encourage people to persevere rather than give up when it starts to look like too much effort. Yes Show
Legacy Code Workshop
1.0 Not at all Unfortunately it wasn't worth it as there were too many of us to sit close enough so missed most of the conversations. Smaller group. No Show
Legacy Code Workshop
1.0 Much better The workshop shows the methodical way of starting to test the legacy code. It is more suitable for smaller groups where the code under review is relevant to all participants. Sometimes it felt a bit slow paced. No Show
Legacy Code Workshop
1.0 Much better Very useful how to see how can we apply TDD on legacy code. Yes Show
Legacy Code Workshop
2.0 Much better It was very good, but I felt like we lost some time because of compiler compatibility. Maybe requesting some code we would like to apply the concepts made available on GCC (which was for VS) Yes Show
TDD Workshop (new code)
2.0 Bring it on! Less C++ Yes Show
TDD Workshop (new code)
1.0 Bring it on! wonderful learning experience . Yes Show
Legacy Code Workshop
2.0 Bring it on! Was good, but a bit slow sometimes because the "mob" was slow Yes Show
Legacy Code Workshop
2.0 Bring it on! It gives you good ideas on how to start integrating this into our own work. Urge participants to PREPARE a CHANGE to the existing code. That more or less caught us by surprise. Yes Show
Legacy Code Workshop
2.0 Much better It felt a bit messy. It felt that a better preparation and structure would have created better results. See previous comment. Yes Show
TDD Workshop (new code)
1.5 Bring it on! 50/50 good/bad for the part of the workshop where we dove into existing code. Specifically, one of the code-bases was particularly gnarly, and I felt like we (as a class) flagged and didn't focus on powering through with baby steps (perhaps we fell into a bit of a gripe-fest). Otherwise, it was great to set some footholds into existing code, and see our classmates recognize what was actually possible. Perhaps a firmer hand in guiding us through particularly gnarly code-bases. Knowing how to tame them is essential, but also requires a lot of wherewithal, which we might need to help come from the instructor. Yes Show
Legacy Code Workshop
1.5 Bring it on! Fantastic, very helpful to work with a dozen newly trained TDD eyes take on real work problems. Loved that everyone had an opportunity to have their project be a focus. 1 day may have been enough, after working on my project I was itching to get back into it! Yes Show
Legacy Code Workshop
2.0 A little The workshop was very disorganized. The portions where we all worked on one piece of code as a large group were very slow since most of us had never seen the code before and didn't know how it worked. There were also some show-and-tell times when we looked at test cases written for existing code, which I didn't really get anything out of because I didn't know what the code was supposed to do or how it worked. The one section where we broke into small groups to bring legacy code under test was ok, but I didn't feel like my group got very far because we didn't have a very clear path for testing. I think this would have been much better if the managers/class organizers had picked what code we would work on before the class and told us before hand so we could review it to get a little more understanding. Also, I think we should have spent more time in small groups and less as one large group all working on one thing. No Show
Legacy Code Workshop
2.0 Much better I liked the mob programming exercise and also the concepts that were presented. I did not have any code I am currently working on that could be part of this workshop. Having exercises to do when you do not have your own code to work on. Yes Show
TDD Workshop (new code)
2.0 Much better Havingg done a bit of TDD-ish development previously, this gave me more insight into the techniques and philosophy of it. I found the hands-on exercises, particularly the pair programming, especially valuable. I especially liked the use of TDD as a mediation for cut-n-paste errors, which I've not been able to find a tool for to-date. Yes Show
Legacy Code Workshop
2.0 A little Honestly, I wish I could have skipped these two days because of program pressure. I didn't get much out of it because I'm not working in a development environment that easily extends itself to TDD. The workshop kind of assumed that everyone could (or has) set up their environment for TDD... I'm still struggling with getting that part set up. I wish there was more help with getting CppUTest set up (or at the very least, I wish there were pre-req instructions for setting up CppUTest before the training and workshop). No Show
Legacy Code Workshop
2.0 Moderately I would have rather we either do more structured TDD exercises or split into smaller groups to work on our team code bases rather than some of the time we spent discussing / reviewing code as a whole class. I just feel that the relative ROI of that exercise was lower than other activities from the 4 days. Not sure, maybe we just needed to be better prepared with code to apply TDD to, even if it was re-implementing components we (as a company) had already written. In fact, doing that may have made the exercise slightly more comfortable (without looking at the old implementation), just for the purpose of practicing the technique, not necessarily rewriting our code base. No Show
Legacy Code Workshop
2.0 Bring it on! No Show
Legacy Code Workshop
2.0 Moderately I talked more in the other form about this, but we did not prepare for this properly, in my opinion. Blue did not come with a clear plan for what code should be reviewed and tested, and the complexity of the code we brought meant that it did not serve as a good example. No fault of the instructor here. Higher bar for what code will be tested/used and a reduced scope in terms of complexity. Yes Show
Legacy Code Workshop
2.0 Moderately Should've been more prepared and organized to benefit from this. Have participants provide a plan of action and specific code they'd like to work on as prep, before the course begins. Yes Show
Legacy Code Workshop
1.5 Bring it on! The code was very complex and a lot of time was spent trying to understand what was there before it could be put under test. We did successfully implement a test framework. If developers come to workshop with a better understanding of the legacy code to be discussed and/or the instructor has reviewed the code beforehand. Yes Show
Legacy Code Workshop
2.0 Much better Yes Show
Legacy Code Workshop
1.0 Bring it on! It was really instructive to watch more experienced developers solve the problems of getting our code to build off target with a different compiler. Yes Show
TDD Workshop (new code)
2.0 Moderately Working in pairs was incredibly beneficial. It would be helpful to assign partners from the start rather than reorganizing people after the first activity. Yes Show
Legacy Code Workshop
1.0 Much better the workshop is helpful. Yes. Improvement: I hope the setup instruction provides extra details. Yes Show
Legacy Code Workshop
0.5 Much better It was very useful to get know what and how can be be improve in our tests of legacy code. Yes Show
Legacy Code Workshop
1.0 Moderately Yes Show
Legacy Code Workshop
1.0 Much better It was interesting to have an external feedback on our code and we learned many things, but it was a bit exhausting. It'd be better if the teacher had already seen the code before the workshop, but it's obviously almost impossible to setup I guess (NDA, etc) Yes Show
Legacy Code Workshop
0.5 Much better Yes Show
TDD Workshop (new code)
2.0 Moderately It was great It was great => not much to improve... It proved that the background I have already put me on the right tracks. Yes Show
Legacy Code Workshop
1.0 Much better It could have been better. We wasted the first half of the day trying to get our environments set up and not actually learning anything. Once we got going, however, I found the workshop useful. A lot of the delay was because we were trying work on a project that is not mature and is difficult to build. Perhaps encourage groups to choose code that can be set up quickly and reliably. Yes Show
Legacy Code Workshop
1.0 Much better It was interesting to colloborate with my peers, get an existing class into a new shared library, and enabling it for test. It was very constructive working with each other to solve our problems at hand. None Yes Show
Legacy Code Workshop
1.0 Bring it on! I feel like we should have been more prepared on our end. Again, I think we could have made more progress if we had done a little more upfront preparation to get our environment setup. Yes Show
Legacy Code Workshop
1.0 Bring it on! I mostly watched another engineer attempt to build a test harness for his code. The workshop is good but you may want to require (or strongly suggest) that the classroom has good connectivity and workstations so we can work more efficiently. Using VNC on a laptop over slow wireless is tedious. Yes Show
Legacy Code Workshop
1.0 Moderately pulling a lot of dependencies for both header files and cppu test in first 5 hours of the workshop. I feel our code base needs a lot of clean up or good tools and architecture restructure to bring the TDD in. The workshop definitely helps us, engineers, realize how complex our legacy code has became. but, you have to start some where... I think it would help from our end to think about our legacy code or bring in people that worked on our tools to benefit more from the workshop. The workshop can be more efficient if we had picked a simpler component as well. Yes Show
Legacy Code Workshop
1.0 Moderately It was very interesting seeing how things went with a relatively complex component. We got hung up on some generic aspects of our architecture, but hopefully we would be able to work out systematic ways to deal with those (since these things are common in our code). Good to see techniques for overcoming issues. But, still seems daunting to apply on a large scale in our code. Maybe 2 days would be better. One day to deal with initial challenges, then come back fresh for a second day to see how much more could be covered. Yes Show
Legacy Code Workshop
1.0 Much better I broke off from the group and tested some code I wrote that was separate from Sirius and I had a good experience (found some bugs). If we understood how our test infrastructure works we wouldn't have to reinvent the wheel to get the cpputests to work. Yes Show