Workshop Feedback -- 100 entries

Workshop Duration Better prepared Your workshop experience How to improve Recommended
Legacy Code Workshop
0.5 Moderately Yes Show
Legacy Code Workshop
1.0 Bring it on! The course covers concepts that are fundamental for professional developers. TDD is one more tool in our toolbox that should be mastered by any real programmer.This course gave me a solid foundation to effectively apply it in my everyday job. I discovered some subtleties that are hard to capture when we read a book. Provide more case studies to help correlate attendees problems with real life examples. Yes Show
Legacy Code Workshop
1.0 Much better Very nice experience working own familiar code and implementing TDD Not much in my point view. Good instructor. Yes Show
Legacy Code Workshop
1.0 Moderately Yes Show
Legacy Code Workshop
1.0 Much better All good, thanks. Was fine for me. So no real need to change something ;-) Yes Show
Legacy Code Workshop
0.5 Moderately Good workshop. Burkhard is very experienced and showed the steps how to run TDD on integrate legacy code; very impressive for me. On the other hand: our already available cmocka test setup is (from the point of tooling!) very similar; tdd is mostly a different art of doing development. When I created some GINA interfaces in the past, testcase development started when ~50% if the code was already available (the straight forward stuff) and therefore was mainly used for stability+ranging. This workshop depends from the used code example. It should more pointed to the fact, that a code which is known from most attendees is better to use. This should be done at the very beginning of the training, not in between the training days (as usual, there is always more than the training at the training days...), that attendees have a better chance to sync internally before. Yes Show
Legacy Code Workshop
1.0 Much better Together with my colleagues we could start TDD with an existing component and implemented some first test cases. In the beginning, i was a bit skeptic for to get any success. But now we learnt, how to proceed. This is a very good starting knowledge to use TDD for our components. Currently i have no idea for improvements. Maybe later with the experience of successfully developed components with TDD. Yes Show
TDD Workshop (new code)
0.5 Much better I listened to how for one group their development of a new product could be switched to using TDD Yes Show
Legacy Code Workshop
0.5 Much better Yes Show
TDD Workshop (new code)
2.0 Much better Yes Show
Legacy Code Workshop
0.5 Much better Yes Show
Legacy Code Workshop
0.5 A little not yet The workshop will be in June not yet The workshop will be in June Yes Show
Legacy Code Workshop
1.0 Bring it on! I did not 100% understand what should be prepared for the workshop, so the start was a bit rocky. We quickly identified our dependencies and created stubs. James showed us some common patterns to solve typical testability issues in our code. We finished with a small set of working tests for actual production code on our master branch. A clearer TODO list for preparation would have helped me: What exactly do I need, what is optional. Yes Show
Legacy Code Workshop
0.5 Much better Colleagues have done some initial work beforehand, so lots of the first time consuming blockers have already been solved. Therefore, it was fun to see the progress within the five training hours. I don't see anything. Yes Show
Legacy Code Workshop
0.5 Much better I heard that other teams spent most of the time to make the code testable. But once you understood the principle of exploding fakes, there is no additional benefit to resolve another 50 dependencies. This is just boring work that has to be done. I attended the workshop where Wilhelm prepared the code for our team. We could focus on the testing itself. We talked about testing patterns, test optimizations, path coverage. This was great. I think that each group should spend time to prepare their code before the workshop. Alternatively the selected code must be very very simple. Yes Show
Legacy Code Workshop
0.5 Much better Hardworking colleage managed to resolve the exhausting include dependencies for us before, so we saved a lot of time and could focus on essentials during course There should be some general drawing, cheat sheet, overview of the approach during the workshop and finally to take as reminder. Yes Show
Legacy Code Workshop
0.5 Much better It was very helpful for getting started to write good tests in our own project. A summary of the main learned issues at the end of the workshop would be nice. Yes Show
Legacy Code Workshop
0.5 Much better Upfront it seems like there is no way to get into a sufficient testing structure. But James guided us with small hints or suggestions through this pain. This gave us another view on testing techniques for refactoring. In the end we identified several aspects to look at i our code. - Yes Show
Legacy Code Workshop
1.5 Much better Please quote me anonymous. Yes Show
Legacy Code Workshop
0.5 Moderately Yes Show
Legacy Code Workshop
2.0 Bring it on! I learned a new way to developp ;) In our case, having more time between theorical and practical part could help...as we're very busy, it was difficult to provide relevant start point. Yes Show
TDD Workshop (new code)
1.0 Bring it on! Just trying to regenerate my certificate Just trying to regenerate my certificate Yes Show
Legacy Code Workshop
0.5 A little The workshop showed a few practical techniques to resolve code dependencies step by step, which was very instructive. Still, I didn't like the workshop, because a discussion was constantly started that was hardly possible to follow for inexperienced in this subject. Smaller groups or proper moderation. No Show
TDD Workshop (new code)
2.0 Moderately I really enjoyed working with the environment that was provided in the workshop. It made testing the code changes much more fun and straightforward. Yes Show
TDD Workshop (new code)
1.5 Bring it on! Really enjoyed the course and felt that I've learnt so much; it will change the way I write code from now on. The course material and practical work were balanced well. James has a wealth of knowledge on the subject and it felt like we were learning from the best. n/a Yes Show
TDD Workshop (new code)
0.5 Much better . . Yes Show
TDD Workshop (new code)
2.0 Moderately It was a good introduction to TDD concepts. I was so far very unfamiliar with TDD. - Yes Show
TDD Workshop (new code)
1.5 Bring it on! Learned a new and more confident way of approaching writing code Yes Show
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