Workshop Feedback -- 322 entries

Workshop Duration Better prepared Your workshop experience How to improve Recommended
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
Legacy Code Workshop
1.0 Much better We discovered a wide gap between training exercises and real code. We took an enormously long time to prepare a small portion of one out of thousands of modules in our system and get it building in a standalone cpputest environment. Although subsequent efforts are expected to get easier, it is a very steep hill to climb for a very large legacy codebase. Some offline preparation in identifying and sanitizing modules would have made this workshop more productive. However, the underlying challenges of applying these concepts to a large legacy codebase remains. No Show
Legacy Code Workshop
1.0 Much better It was both enlightening and a bit frightening due to the amount of effort that seems to be involved in creating unit tests for our legacy code. Yes Show
TDD Workshop (new code)
2.0 Much better Yes Show
Legacy Code Workshop
1.0 Much better It was sobering because we learned how hard it is to take some of our legacy code and apply cpputest unit testing from scratch. Lots of issues to be solved. But, I liked that we all saw this together and can not head off to try to tackle this big problem. Make it two days so progress can be made even if big hurdles are found? Yes Show
TDD Workshop (new code)
2.0 A little The workshop went well. Exercise of a mock is bit challenging since I don't have lots of background in programing. The first day of the workshop, I felt it is helpful but it can be very tough to be implemented. Now, I feel that it is not very tough but time consuming to implement in workplace. Despite of it, it's good practice. "MAKE YOUR CODE WORK BY TESTING THE CASE THAN WRITE A LONG CODE THAT DOES NOT WORK AND WHICH IS VERY HARD TO FIND THE BUGS!" All Good Yes Show
Legacy Code Workshop
1.0 Much better It was a good experience.It seemed chaotic at the start, and to be honest, 60 minutes in, I was not sure we would get anything to compile. By the end we had three separate code bases running one or more tests(two c, one C++). It actually worked well to be tackling multiple projects, because it allowed multiple people to drive simultaneously, and allowed the rest of the group to work in smaller mobs. I don't have any specific feedback at the moment. Yes Show
Legacy Code Workshop
1.0 Moderately Good example of process, would be nice if we could have looked at some of our code. Coverage of C# and QT. Yes Show
Legacy Code Workshop
1.0 Not at all We took code bases and built them in a test environment. I'm not currently working on any of these code bases. Most of the technique are specific to C and C++ and I have not been using these languages recently. Yes Show
Legacy Code Workshop
1.0 Much better This was what I was looking forward to the most as I am not currently writing new code, only trying to fix/maintain/support legacy code. While I was not able to actually add testing to my production environment, but watching other go through it was VERY helpful and I am able to envision how to start ding this back at my facility. I was however, able to get CppUTest and the starter project added to a Visual Studio environment and was able to practice a little with some old throw away code. Yes Show
Legacy Code Workshop
2.0 Much better I had a great time. I learned a lot about TDD, as well as C and C++ from your examples. (I am not a C or C++ programmer) I thought the legacy code workshop using our own code was great. However, I would recommend using your own an existing example of how to apply TDD to legacy code in order to keep everyone focused and speed up the delivery of the concept. Then use the customer's code so that they have already had an example. Yes Show
TDD Workshop (new code)
1.0 Much better I learned a lot about the lower layers of C programming that I didn't know. It bridge the gap between coding and implementation. Yes Show
Legacy Code Workshop
1.0 Moderately I am a product manager, so none of the actual application of settingup environments applied to me. However, I was interested in learning more about the other team members through observation of how they worked singularly and as a team. Yes Show
Legacy Code Workshop
1.0 Bring it on! Yes Show
Legacy Code Workshop
0.5 Much better i got to drive us through at least one of the undeclared references that needed to be resolved before we got to linker errors and using doubles to stub out module dependencies. I think it went pretty well considering that legacy code is going to vary in difficulty from class to class. Yes Show
Legacy Code Workshop
1.0 Much better The effort to add tests to legacy code is reason enough to build all new code via TDD. I wish we had done kernel code vs. user mode. I spent the better part of the weekend iterating on one kernel module... there are some key differences to tricking some of the headers to build as needed. Yes Show
Legacy Code Workshop
1.0 Much better Yes Show
Legacy Code Workshop
0.5 A little We were only able to cover James walking through a legacy code. I'd have liked to have more hand-on experience with our own legacy code where we could get started and write tests. I'd have liked to have more hand-on experience with our own legacy code where we could get started and write tests. Yes Show
Legacy Code Workshop
0.5 Much better I enjoyed the legacy code workshop. I would have liked to have gotten further, or shown what the final product looked like, but it was encouraging to see the struggles that I have are real. I would like to see the example taken further, or at least jumped to the conclusion to see what the final product was like. Yes Show
TDD Workshop (new code)
2.0 Much better Two days of theory mixed with practical fun exercises. Nothing comes to mind. Yes Show
Legacy Code Workshop
2.0 Much better Our company has two main product lines, one based on C and one base on C++, thus we spent one day looking at the unit testing of legacy C code and one day working on the legacy C++ code. As a developer who works primarily on the C++ project I was not that interested in the C side of things although there was some useful information there. I would have been happier getting more involved in the C++ side of things but I also understand the need to implement TDD on the C side too. A lot of time was spent dealing with external interfaces and dependencies from the legacy code that had to be fakes, mocked, etc. This process is necessary but takes up a lot of the class time. It would be more useful if a lot of this could be handled before the class starts so that we can see how to to begin testing the legacy code after getting it to compile and link, however, I understand that this is not a easy thing to do. Yes Show
Legacy Code Workshop
2.0 Bring it on! Very helpful. Especially liked the way we managed to get into the function to be tested via the faked call to pthread_create. Overall, a very useful introduction into the issues of getting TDD started on legacy code. Not sure how to implement this but the second day saw several people leaving early. I believe this was due to a desire to get back to other tasks but the focus of the first day was lost while you helped individual groups. Again, not sure how to remedy this as the one-on-one help was extremely important. Yes Show
Legacy Code Workshop
2.0 A little Yes Show
Legacy Code Workshop
2.0 Bring it on! Yes Show
TDD Workshop (new code)
1.5 Much better I have learned new concepts and new ways of working. It is quite balanced. Yes Show
TDD Workshop (new code)
2.0 Much better Could learn TDD concept and how to do it. Yes Show
TDD Workshop (new code)
2.0 Much better I enjoyed it even though most of it was over my head. Not sure. Yes Show
TDD Workshop (new code)
2.0 Bring it on! This workshop was a great experience. I learned a lot about TDD and the lectures/exercises inspired me to dig in and start applying the principles to real-life code. Again, my only complaint is about having to sit through tiresome, fruitless debates between the attendees and the instructor. Some people just don't want to change their ways. I am not sure you could do any better at handling these cases, as you've already demonstrated a great deal of composure and patience when addressing these situations. Yes Show
Legacy Code Workshop
1.0 Much better It was great to get a start on our legacy code testing using real code and having you there to guide the process at first. One of our developers actually found bugs in his code when writing tests that he thought would work but ended up failing. Yes Show
TDD Workshop (new code)
2.0 Much better It was eye opening Need more time Yes Show
Legacy Code Workshop
2.0 Much better Workshop was very useful and showed me the first steps on how to implement TDD in my legacy code. Already very good. Hands on principle on own code is the best way to go. Yes Show
Legacy Code Workshop
2.0 Much better Great experience presenting useful practice that can help anybody to improve programming skills. In advance convey instructor insight into dependencies in the code which is to be reworked in a workshop and get advise is it good example to be treated. The goal should be to have at least one full test completed on legacy code by the end of workshop. Yes Show
Legacy Code Workshop
2.0 Much better Yes Show
TDD Workshop (new code)
2.0 Much better Overall good, I think I got the basic understanding of the process. Because this is new to the organization I'm struggling how I can bring in the test harness and test cases along with the code baselines and how to develop a standardized way of reviewing the tests as part of the development process. James, this is the second feedback form I'm doing. I think you could make training and workshop one form. Yes Show
TDD Workshop (new code)
2.0 Much better Yes Show
TDD Workshop (new code)
2.0 Much better Yes Show
Legacy Code Workshop
2.0 Much better I took the "Test-Driven Development for Embedded C Programmers ". So I selected the workshop option by mistake in the feedback form Yes Show
TDD Workshop (new code)
2.0 Much better In-class exercies are well-prepared (online compile without local PC setup) and very useful for me to understand the concepts of TDD. Yes Show
TDD Workshop (new code)
2.0 Moderately It was very good. Yes Show
Agile Startup Workshop
0.5 Moderately Yes Show
Agile Startup Workshop
0.5 Much better Yes Show
Legacy Code Workshop
0.5 Much better Very helpful to see TDD applied to "real" code. More time than just a half day. Yes Show
Agile Startup Workshop
1.0 Moderately The Agile concept is good, but it will take time for organizations to follow over the existing waterfall style development. Provide successful use cases. Yes Show
Legacy Code Workshop
1.0 Moderately i think it wouldve worked better if we had installed our environment tools earlier in the day, but you did say that this was a sort of a change in schedule also, i think im writing this in the wrong place, but at least for my sake, i wouldve felt better if there was more focus on handling legacy code on the perhaps the second day of this three day training since that is the majority of what we deal with, but i understand that you may not have known that and what not all in all i really appreciate the new outlook that tdd and working with test harnesses gives Yes Show
Legacy Code Workshop
0.5 Bring it on! This workshop need to be for at least two days so that we can deal with more legacy code tips and tricks Yes Show
Legacy Code Workshop
2.0 Much better Learned how to integrate the test harness into our projects Yes Show
Legacy Code Workshop
2.0 Bring it on! Hands on experience setting up TDD environment and development. Yes Show
Legacy Code Workshop
2.0 Much better I think a lot of us have wrong idea about what unit test really is. What we try to do is more like doing functional test on a specific C module. Would be nice to see a complete legacy code example from you so that we don't have to deal with lots of compiler related issues. Yes Show
Legacy Code Workshop
2.0 Bring it on! Really liked the "Slow" fast process moving in a steady pace where each step is based on knowledge instead of finding a "magic" solution... Compile->fail->compile->ok->link fail->link ok... Loved the fff utils to resolve the linking and creating fakes. Spend a bit more time on mocking hardware. Yes Show
Legacy Code Workshop
2.0 Moderately I was interesting to apply what we learnt in the TDD course to own code, but I would have been able to take more from that if I had chosen a simpler function to test. What I mean is that selecting the function from our code should be taken with caution in order to not to stumble into unnecessary difficulties. Maybe let the trainees know what I tried to explain above. Yes Show
Legacy Code Workshop
0.5 Not at all I made a mistake. I did not attend this. I made a mistake. I did not attend this. Yes Show
TDD Workshop (new code)
2.0 Much better Interesting and thought provoking. Nicely presented. Yes Show
TDD Workshop (new code)
1.0 Much better Yes Show
Legacy Code Workshop
1.5 Much better The workshop was very useful and had a lot of good ideas on how to retro-fit tests on existing code Yes Show
Legacy Code Workshop
1.5 Much better The workshop was very useful and had a lot of good ideas on how to retro-fit tests on existing code Yes Show
Legacy Code Workshop
2.0 Moderately Basic sample framework was already created by someone in the company before which we took and applied it to a module for simple file/function test. However applying to existing non-trivial legacy function was the real test and involved first understanding the legacy code/requirements, then writing the tests based upon the understanding and then debugging the tests (since legacy code is a existing standard and when test failed, we had to investigate why it failed given the code was part of the release. Since example/sample framework was already created within the company, we could have tried this on our own and did not really required to be in the workshop. No Show
Legacy Code Workshop
2.0 Moderately It's a case of bring your own code and write module tests. The principle exercise however - was getting familiar with our own department framework which was inadequately documented (all too new). There is no golden bullet. Yes Show
Legacy Code Workshop
2.0 Bring it on! Yes Show
Legacy Code Workshop
2.0 Moderately Really enjoyed it working step-by-step through legacy code to create first unit test. If some legacy code can be shared before hand and some exercise are designed based on this; and making sure all possible concepts can be applied. Yes Show
Legacy Code Workshop
2.0 Bring it on! Good. Quite different to the tdd course in as much as it is really is workshop in how to use the tools that were introduced in the tdd course. Very useful to try and instrument existing code. Yes Show
Legacy Code Workshop
1.5 Much better It was fun. It was hard to resist changing the legacy code before we'd written all the tests we could. Include an in-house presentation of what our build system already provides that can help. We had one, but it was half a day late, and slides/notes would have helped. Your input/manageent was great though! Yes Show
Legacy Code Workshop
2.0 Bring it on! Very good... A bit painful at first but that was expected. Now things are ticking along I am very enthusiastic about it. Not sure it could... Yes Show
Legacy Code Workshop
2.0 Much better It was good learning. Learnt new skill to see legacy code from new perspective. Yes Show
Legacy Code Workshop
1.5 Much better Gained practise using cpputest to retrofit unit tests into legacy C code performing both positive and negative testing using a number of techniques - mock, FFF and mock. Learnt how to quickly develop test stubs using FFF that can be used by myself and others and customised according to individual test needs. More time - possibly some more preparation on our side because an awful lot of time was spent setting up a build environment which is a process specific to Cobham Wireless Stevenage. Better explanation on the mechanisms on our own Wiki - particularly around what has already been done to support the process - would have been welcome. Yes Show
Legacy Code Workshop
1.5 Much better Yes Show
TDD Workshop (new code)
2.0 Much better Yes Show
Legacy Code Workshop
1.5 Bring it on! Yes Show
Legacy Code Workshop
1.5 Much better Excellent. Applying it in the real world was a real enabler. Perhaps an individual (but guided) simple framework creation for 1-2 hours before legacy code. Reason :: understanding the compiler / linker / build environment was very insightful. Yes Show
Legacy Code Workshop
1.0 Much better Left more to own devices and was helped more by colleagues who had already started this work here - James was v useful though on the various approaches not sure Yes Show
Legacy Code Workshop
1.0 Much better It helped me in absorbing the TDD concepts and apply these to the work I do on daily basis Little more practice on advance TDD concepts like Mocks, FFF etc Yes Show
Legacy Code Workshop
1.5 Bring it on! Working with each other really helped everyone get up and running in the first day. It helped having an already created environment people could use, and some people who had used it previously attending that part. Yes Show
Legacy Code Workshop
2.0 Much better Very good and useful exercise Yes Show
TDD Workshop (new code)
2.0 Moderately Fitting some of our existing classes into test harnesses was a humbling experience. It took a tremendous amount of work but was probably worth it. At the very least, several dependencies and other vulnerabilities were revealed during the process. The workshop relies mainly on an organization examining their own code so there's not much that can be improved about that aspect of it. Yes Show
Legacy Code Workshop
2.0 Much better Yes Show
Legacy Code Workshop
2.0 Moderately It was quite fascinating. I've never attended training where the exercises involve the customer's own code base. Since I'm in HW, I've seen the SW code base but never worked with it to that extent before. Yes Show
Legacy Code Workshop
2.0 A little I don't think the group I was associated with made the best choice for learning purposes, but that is our fault. I think the choice of code to work on is pivotal in getting something out of this workshop. The instructor really can't be expected to be much of a factor in this key decision. Yes Show
Legacy Code Workshop
2.0 Bring it on! I enjoyed discussing design ideas and getting some fresh perspective on adding unit tests. I think we spend too much time in analysis paralysis when should try things. We'll frequently spend longer discussing how we should could test something and it was refreshing to just try something and see what works. For the mobbing portion it would have been useful to ensure we actually switched people out more frequently. Yes Show
Legacy Code Workshop
2.0 Much better Great experience. Good to work in our own codebase with the concepts learned. n/a Yes Show
Legacy Code Workshop
2.0 Bring it on! Overall good experience. Very frustrating to start, very satisfying when you have a finished test and some refactored code. Easy to get burned out on beating the legacy code into submission. Might want to alternate more between lecture and hands-on. Yes Show
Legacy Code Workshop
2.0 Much better It was very challenging to get the code in a test harness. It was all good. Yes Show
Legacy Code Workshop
2.0 Moderately The most important thing I learned when dealing with complex and very dependent systems is that following one dependency at a time and analyzing and understanding the need of it really helps a developer learn and understand there code. When working with multiple languages for different systems, setting up a test harness was relatively painless for one language. Because of this the depth of setting up the test harness felt a little shallow for users of other systems. However I was able to ask and James was able to help. I felt it was information that should be part of the presentation rather than having to ask as an aside. Yes Show
Legacy Code Workshop
2.0 Much better It was nice having some time to sit down and tackle something in the legacy code base. Yes Show
Legacy Code Workshop
2.0 Moderately Useful. Yes Show
Legacy Code Workshop
1.5 Much better gave insight into setting up a module test environment with legacy code Yes Show
Legacy Code Workshop
1.5 Much better gave insight into setting up a module test environment with legacy code Yes Show
TDD Workshop (new code)
2.0 Moderately Couldn't select Five days in the "How many days did you participate in the workshop?" drop down, maybe you need to update your tests for this page!! The workshop was good, I do feel like I could go on the whole thing again and still learn loads. Free book would have been good!! Maybe pushing a few more exercises into day 3 so that it was broken up a little more? Yes Show
Legacy Code Workshop
1.5 Much better Really happy with the workshop. The TDD training was effective only because of this workshop. Quite often we find it difficult to make use of the methods we learned in a training in the daily work, but here we already made some progress towards it. I would prefer each of the participant doing the workshop individually than in a pair. Yes Show
Legacy Code Workshop
1.5 Bring it on! Yes Show
Legacy Code Workshop
1.5 Bring it on! Really enjoyed it. I think this was the part where the penny dropped for many attendees as they saw that it was possible, albeit with a bit of upfront grief, to implement a working unit test in legacy code. You could tell by the buzz around the room that people were actually enjoying themselves. Not sure, I think it's fine as it is. Yes Show
Legacy Code Workshop
1.5 Much better excellent Yes Show
Legacy Code Workshop
1.5 Much better Well structured and paced. It was good to keep changing the partner you are with in each major section of the workshop. It would have been good at the end of each exercise to have seen an example of the exercise correctly fully completed that you could download or keep for future reference. Yes Show
Legacy Code Workshop
1.5 Much better Very good, learned how to integrate the initial framework of cpputest to our project. It would have been better if all work on the same code and if instructor discuss (or suggest changes/improvements) this to all (not individually) in regular interval. Yes Show
Legacy Code Workshop
1.5 Much better This was very helpful to see that putting the code under test was not as daunting as previously thought.The methodology is easy to adhere to Yes Show
Legacy Code Workshop
1.5 Bring it on! Good to do pair programming again. Don't get to do it enough! Longer.... Yes Show
TDD Workshop (new code)
2.0 Bring it on! Excellent Yes Show
Legacy Code Workshop
1.5 Bring it on! Very good seeing how the concepts can be engineered into existing code to make it better. Don't know Yes Show
Legacy Code Workshop
1.5 Bring it on! Yes Show
Legacy Code Workshop
1.5 Bring it on! Yes Show
Legacy Code Workshop
1.5 Moderately The workshop can be improved by including the examples for the cases/scenarios where the "Code Under Test" depends heavily on 3rd party software. Yes Show
Legacy Code Workshop
1.5 Moderately I selected C project where debugger ability was limited due to interactions with QNX shell scripts Detail tutorial on substitution of: shared and static libraries, headers, macros, interfaces, hardware inputs/outputs, database, timers Discussion on unit test in single thread for multithreading application Yes Show
Legacy Code Workshop
1.5 A little good.. learn new things cpputest for working code. NA Yes Show
Agile Startup Workshop
1.0 Moderately I found the course a good "quick start guide" on what questions / areas to focus on. More discussions about velocity and upfront planning. Yes Show
Legacy Code Workshop
2.0 Bring it on! It was very nice experience, came across lots of dependencies inside code. Found and was able to fix some of the dependencies (with the help of trainer). Workshop was good, but need little bit more time. Yes Show
Legacy Code Workshop
1.5 Moderately Could not succeed. Learnt the challenges and approach. Need some home work. Work on real problems on live code. Yes Show
Legacy Code Workshop
1.5 Much better Got a lot dependency issues. Still working on cleaning them. It was a very good start. I like it! Instead of letting us follow the instructions on the paper, instructor might demo how to hook up the test harness so it would be easier for everyone to follow. Yes Show
Legacy Code Workshop
2.0 Much better Although MinGW and Cygwin were quoted as potential platforms for use with cpputest on PC it seemed MinGW had a number of issues and I could not get it working. I understand there were also issues with Cygwin on PC platform. Maybe these issues could be investigated/resolved before presenting them as potential environments. Yes Show
Legacy Code Workshop
1.0 Much better My experience was positive. I learned new things about legacy code. The way I was testing legacy code was not good. Now I know better how to approach it Beginners taking part to the workshop should be guided in choosing the right piece of code to use as legacy code. If the wrong choice is done, the risk is to spend all time available trying to figure out dependencies. Yes Show
Legacy Code Workshop
1.0 Much better I've chosen a low-level hardware-related module of one of my personal projects: there was a lot of dependencies to microprocessor's .h files to be broken before starting to write the tests for the modules. For me it was a good example because in embedded environment this dependencies are really strong. In our workshop we've started with a legacy code chosen from DALI libraries provided by a collegue of us, but after some tries we switched to another one (mine) that could have been more interesting. Unfortunately, because of the workspace compilation troubles of a lot of us there wasn't a common line and a common example that everyone followed and each one went forward with his personal example ...that indeed was a also good thing because eachone was forced to face real problems with his keyboard in hand... Actually I don't know what could have been better: - giving the chance to each-one to face specific problems in real personal legacy code (with the help of the teacher shared among all the students) or - all the students following one or two real examples of pre-chosen real legacy code with specific tecniques applyed For sure we've lost a lot of time with the workspace problems... Yes Show
Legacy Code Workshop
1.0 Moderately Doing this in one day is really challenging. There are so many different issues which can arise. But it's a big help to lower the entry barrier when we're back in our daily work again. Not easy: Co-Trainers to solve the different issues in parallel to synchronize the course from time to time. Yes Show
Legacy Code Workshop
1.0 Bring it on! The workshop was extremely helpfull in bringing TDD to my code. One of my concerns was that I might not be able to apply the knowledge from the training to my daily work - the workshop eliminated this concern. the only trouble was because of the different versions of visual studio - but that's hard to handle! Yes Show
Legacy Code Workshop
1.0 Moderately We should not work on our own code, but on a legacy code coming from teacher and especially written with educational purposes (showing the techniqies . In this way, I think, we could learn more in the same timeframe. Yes Show
Legacy Code Workshop
1.0 Much better Provide in advance the exercise context. By example tell us that will wil goes to implement a scheduler or led driver or something else. Yes Show
Legacy Code Workshop
1.0 Moderately A lot of new things to learn. Some directive to prepare in advance your own project where to apply the TDD technics Yes Show
Legacy Code Workshop
1.0 Much better It was interesting to see how to make testable a legacy code. The "small step" approach is, indeed, useful to make progresses. However, it was very hard to get the legacy code even to compile, and took a lot of time to get everything fixed. I think that making everyone working on the same legacy file might be better, since it would be easier to track everyone progress and to help in case of problems. In this way might be faster to get to something working, so everyone can see the different aspect of the legacy code testing. Also, might be better to check the source chosen to make the training, so it's not too hard, or too complex to get it done. Yes Show
Legacy Code Workshop
1.0 Moderately Have more time Yes Show
Legacy Code Workshop
2.0 Bring it on! It was useful being able to spend some time getting a framework, such as cpputest, working against existing code we'd inherited. Begin thinking about how we'd scale this up. It was useful as it was. Yes Show
Legacy Code Workshop
1.5 Much better I found it very useful, to get to apply the techniques we had learned over the previous days. "Doing" under the guidance of an instructor/mentor is a very good way to learn. James helped us resolve a number of issues that would have taken us some time to resolve. I found the first day very intensive, but I enjoyed the chance to put theory into practice on a piece of code that I knew hadn't been tested to my satisfaction. Didn't find any bugs (yet) but it identified a number of small improvements for testability and maintainability. Can't think of any improvements. Yes Show
Legacy Code Workshop
1.5 Much better The workshop was interesting as it is always difficult to try and put courses into practice and that is what this workshop was addressing. Being able to see the testing techniques applied to familiar code makes it more useful to be able to make progress after the course. A lot of time is spent getting the tools set up to work in the different projects, without much TDD being applied. Intimate knowledge of the pre-compiler, compiler and linker is needed to wade through the deluge of error messages, which can be frustrating. Being able to avoid some of this pain would enable us to focus on the testing techniques better (e.g. understanding where mocks would be used, progressing from exploding fakes to proper fakes). Having this workshop was really useful, but maybe a longer workshop would be more useful. Yes Show
Legacy Code Workshop
1.0 Much better I met many problems in my legacy code due to a lot of dependencies to resolve One day is not enough Yes Show
Legacy Code Workshop
1.0 Much better it was a very good experience because I have found important weaknesses of my product code Is good as it is Yes Show
Legacy Code Workshop
1.0 Much better maybe it is good as it is Yes Show
Legacy Code Workshop
1.5 Much better We have got better ideas on how to retro-fit TDD technique to our legacy code. It can be a challenge to apply TDD from the middle or late stage of projects. The difficulties of TDD may be how to write test cases and how many tests are needed. It is even harder for legacy code because it was written by someone else or long time ago. We do not have much time to cover this area. Yes Show
Agile Startup Workshop
1.0 Moderately a Yes Show
Agile Startup Workshop
1.0 Much better Overall good - learned about user story cards and assigning points that reflect effort. Even though we are a medical device company that requires thorough documentation, we can still use agile methods and develop only those pieces of the detailed specification as they are needed before implementing each portion in code. N/A Yes Show
TDD Workshop (new code)
2.0 Moderately very informative, good blend of hands-on and lecture The pace of the first day could be increased by moving the sticky note discussion (likes, concerns) to the second day after more material is covered. Yes Show
Legacy Code Workshop
0.5 Much better Quite valuable. Finally a consultant that doesn't have an allergy to talking about the actual problems faced by people and willing to be specific instead of contrived. We could have used way more time. Yes Show
Legacy Code Workshop
0.5 Bring it on! It was EXTREMELY helpful to work with actual code from our codebase. This was the first time I have experienced this and was very pleased with the result. I learned strategies for getting a difficult piece of production code into the test harness. 3 hours wasn't enough. We needed more time. Please come back to see us! Yes Show
Legacy Code Workshop
0.5 Much better It was primarily spent getting an area of code into the test harness. Which, is arguably, the least helpful in terms of a workshop. Getting with someone on site prior to the workshop and getting an area of the code brought into the test harness would be good. Then having them step back a couple of steps so that resolving the problems involved in brining an area of code into the test harness in a controlled fashion would allow for all topics to be covered and more practice in applying the meat of the test harness. I would definatly be amiable to a multi-day workshop covering this specific topic. Yes Show
Legacy Code Workshop
0.5 Bring it on! Great, but never enough time. Can't think of anything Yes Show
Legacy Code Workshop
0.5 Much better 15 minutes in the hot seat. Full day would have been useful. Yes Show
Legacy Code Workshop
1.5 A little Too much time was spent setting up our test system which the instructor couldn't help with. Would have preferred to have gone through the concepts without working on our code. Spend the time on legacy code refactoring concepts. We can then apply the principles to company code in company time. No Show
Legacy Code Workshop
1.5 Much better I was nice to see how 'mission impossible' changes over time to 'we can do it'. It may be more useful to say more explicitly what we need to prepare for workshop in advance. So we may not waste time thinking which module to choose. Yes Show
Legacy Code Workshop
1.5 Moderately it became apparent very quickly that no-one on the course knew how to make our internal test system work, this was somewhat unexpected and highlighted the fact that our test system is hard to use and setup. it was a shame this was not discovered before the course as it would have meant more progress could have been made in the day and a half allocated. This is a failure on behalf of CSR/Qualcomm, not a reflection in any way on how the course is run. the company attending the course should have made sure its employees attending the course were better prepared before the start of the course, I don't know whether this is made clear to the company that its employees would get more out of the legacy workshop if they were better prepared in the first place, its really not rocket science and i'm sure it was probably well pointed out when the course was booked that this would be beneficial for those attending Yes Show
Legacy Code Workshop
1.5 Much better -Good, as we could develop some test cases that where no there -Good to have peer programming -If a teach lead or somebody who know about the legacy code and making it work would be helpful in the workshop.And who could tell what kind of methods would be used project wise, may be mock or fake etc, it is good. Yes Show
Legacy Code Workshop
2.0 Moderately To be honest, I didn't like how much time we spend on setting up the environment It would be nice if someone could spend some time before the training to prepare working environment. Yes Show
Legacy Code Workshop
1.5 Much better - It was great experience to test legacy code using tdd approach. - We could bring up the test setup using unity and learnt to use where and when mocks are applicable or fake stubs. Probably more time for legacy code workshop would be of more help. Yes Show
Legacy Code Workshop
1.5 Bring it on! It was a crazy idea but it worked. Ignore everyone else's code and focus on mine for the whole session. Yes Show
Legacy Code Workshop
1.5 Much better The legacy code workshop was quite useful in that, I had the opportunity to see a legacy software module in another functional area where some unit tests are already in place. This helped gain a different viewpoint for my potential refactoring efforts in the future. A bit more preparation beforehand would bring great value to the attendees as it would help avoid synchronization issues among team members. For example, had we agreed on a couple of key areas before the training, such as 1 library module per functional domain where we need refactoring, we could have spent the last 1,5 days altogether much more efficiently. Yes Show
Legacy Code Workshop
1.5 Much better It seemed like slow and frustrating progress to begin with, good thing is that that's the hardest part out of the way. Instructors time was split between groups working on 3 separate code bases, it wasn't really a problem but having a single code base to work on would have given more instruction time for everyone. Yes Show
Legacy Code Workshop
1.5 Much better Brought home the magnitude of the task of writing the test after the code but made it possible. Could be longer, more attention to specific problems with legacy code Yes Show
Legacy Code Workshop
2.0 Much better We started writing tests for our power library. It took 2 hours to get the first test to build and run. The second test took about 15 minutes to write. We got stuck with the 3rd test, James showed us some new techniques that we should try and we managed to make some progress in getting further tests to run No suggestions Yes Show
Legacy Code Workshop
1.5 Bring it on! We got some time to think about bringing the legacy code into the testing framework. I think its been conducted pretty well already. Yes Show
Legacy Code Workshop
2.0 Much better First part of the workshop was hard work to the point of being painful! While focussed on specifically on our code i felt a bit of knowledge lacking about how to actually get started if it hadn't already been done. Yes Show
Legacy Code Workshop
1.5 Bring it on! We brought some of our existing code into a test harness. It was good to have pragmatic suggestions from the instructor. A number of useful 'tricks' were also presented. Dunno Yes Show
TDD Workshop (new code)
1.5 Much better It was interesting to hear the way other team have used test tools to simplify the way their software is tested. We also managed to craft a simple test harness to perform unit tests on DSP code via in-house build tools and code simulator. This has given us the basis for developing a more advanced system to support unit testing of our DSP code. I guess we perhaps needed more time or to have prepared more before the course. Yes Show
Legacy Code Workshop
0.5 Moderately I realised the scope of the task in front of us, and it made me think about what are aims should be for a realistic adoption of better unit test coverage for legacy code refactoring. It made me feel we are a long way from applying TDD in our legacy embedded system. But that isn't bad- it is better to know more! Really I think there should be a period with an instructor per team of 4 to 5 guys working on test generation, just to keep guys on the right path, and provide immediate feedback. I also think that far more preparation should have been done upfront, whilst the course was being arranged, by my company, not by Wingman SW. No Show
Legacy Code Workshop
1.5 Much better Discussed our systems with Mike and was able to create a simple test harness and test with him. note on answer below. I might be obvious, but I would recommend the workshop only after attending the course. Yes Show
TDD Workshop (new code)
2.0 A little Since I am not a C programmer it was very hard to follow as they loaded our code into the test harness. They were moving too fast for me to follow so I zoned out after a while. The workshop was good. It does not directly apply to my verification job so I was not able to follow a lot of it. Yes Show
Legacy Code Workshop
1.0 Much better It was interesting. I have tried porting code off target before to enable some testing or development and gave up after not too long as I felt like I was going down a never ending rabbit hole. The demonstration showed that although painful at first, taking it step by step and using the various stubbing & faking techniques it was possible. This exercise also revealed a lot of issues with the code structure and the various dependencies. I thought it was a great experience. It was a little painful, but James had seen most of the issues before and knew how to address them so we could make progress with getting the module under test. Yes Show
Legacy Code Workshop
0.5 Moderately A Yes Show
Legacy Code Workshop
1.5 Much better good experience to see TDD could work on our legacy code technically n/a Yes Show
Legacy Code Workshop
1.5 Moderately An example project would help a lot Yes Show
Legacy Code Workshop
1.5 Much better good Tell us what we should prepare before the whole course, not just in the day before the workshop starts. Yes Show
Legacy Code Workshop
1.5 Bring it on! Test case will force you to write a well designed code. May be share some small skills to decouple the code at first may help students to get start quicker. Yes Show
Legacy Code Workshop
0.5 Much better i have only half day to practice on this, my bad, the course itself was good. already been good. Yes Show
TDD Workshop (new code)
2.0 Moderately I liked it. Inspiring. Want to do this at "home" Peering with others at the same level (peer from attendants feedback about own skills) Yes Show
TDD Workshop (new code)
2.0 Moderately Most of the basic stuff was familiar, though I learned some new tricks. Haven't used cpputest before and mock objects was new to me and seems very handy. Could have started with mock objects earlier. CircularBuffer and LightControl cases were somewhat similar. Yes Show
TDD Workshop (new code)
2.0 Much better This has been like being force-fed Nyquil cough medicine, but you have a great energy and demeanor for dealing with the inevitable reaction. I can see the light of how this could grow on me and be as fun as being a cowboy (without the hangover of debugging afterward). I would need some time to digest this all and to try to apply it to be able to answer this. Yes Show
TDD Workshop (new code)
2.0 Much better Very informative. Give a simple exercise as introductory before going to extensive ones. Yes Show
Legacy Code Workshop
1.5 Much better Enlightnening Seting up of the CppUTest farmework would have been good to have a step by step guide avlible. Due to various reasons not everyboady can do this at the same time. Idealy it would be nice if this was done in advance (Easy to say now ) Yes Show
Legacy Code Workshop
2.0 Much better For the legacy code I feel like applying of TDD is limited and hard to do, even the way of TDD brings many benefits, like better testability of the code and better support for refactoring. Maybe present at the beginning of the workshopp to all participants how to set up the CppUnitTest environment and how to set up the cpputest-starter-Project. Yes Show
Legacy Code Workshop
2.0 Moderately It took to much time to set up Cpputest for our legacy code. Present more re-factoring methods Yes Show
Legacy Code Workshop
1.5 Moderately It took very long to get the code compile and link before any test could be created No idea Yes Show
Legacy Code Workshop
1.5 Much better It gave a lot of experience on how to implement TDD practically on our code. Since we had to do a bit of configuration as well for the new environment that we used, gave us a hands on for configuration as well. All the problems that different teams faced could be shared in a common place so that we know where to look if we face a similar issue. Yes Show
Legacy Code Workshop
1.5 Moderately The workshop provided hands on experience in applying the concepts of TDD and setting up the test environment of the legacy code that could be used as a reference to start applying TDD concepts at work. Groups share their experience/ challenges faced during the workshop. Yes Show
Legacy Code Workshop
1.5 Much better To see the micro cycles really working. That it is worth to write the test first. I don't know. Yes Show
Legacy Code Workshop
2.0 Moderately Workshop was good. Support provided during implementation is appreciable. Feeling confident enough to modify or refactor legacy code. Workshop structure is in good shape Yes Show
Legacy Code Workshop
2.0 Much better it's fun. and a new approch to see our legacy code. what concerns me is that we may lost in our test cases if we want to do full coverage test Help us to set up the starter project more efficiently Yes Show
Legacy Code Workshop
1.5 Much better Good to see how to solve the problems to get the legacy compiled in a test. Starting point for bringing our legacy code under test should be better prepared. Yes Show
TDD Workshop (new code)
2.0 Moderately 5day course. Very thorough course with well thought out example to work through - got a lot out of it. I have only put moderately as I was using a lot of the techniques already and some of the legacy code techniques are not applicable to my domains space - as a course I think it was spot on. Yes Show
TDD Workshop (new code)
2.0 Bring it on! helped to improve my OOP/OOD concept and testing skill Could be slow down a little bit on the last module (mock testing). Overall is excellent Yes Show
TDD Workshop (new code)
1.5 Much better It's good to practice what I just learned. If the instructor can parallelly show some application of TDD in his work when the trainees are working on UT, it's better. Yes Show
Legacy Code Workshop
1.5 Much better this is a good method. But make a new UT test project need many time, fix compile issue, link issue. I'm wondering can we automate this work like TestRT, it will auto generate STUBs for us, after wizard done, a executable project already exist. short env setup time, more time to practice TDD Yes Show
Legacy Code Workshop
1.5 Much better The participants should get well prepared for the legacy code to work on (CppUTest project is up). Yes Show
Legacy Code Workshop
1.5 Bring it on! I found this workshop it's helpful. I could setup the framework for test project. I like it as it is. Yes Show
Legacy Code Workshop
1.5 Much better good experience. we have chance to really trying it on our legacy code and have the trainer help if we face problem, and normally we will face problems. hope the pre-requisite is told upfront clearly, so that we will prepare some legacy codes that can be used in the workshop. I happen to know it quite last minute but luckily we are in progress to trying out TDD, so it is lucky that I can have legacy code that can be used in workshop. Main reason to know it earlier because it take times for us to successfully build some legacy code separately (outside original build environment) which is needed by the workshop, as most of us only deal directly with the real code but didn't involve much on how to get the software built (main effort is to identify the inclusion path needed or the mocks needed). Yes Show
Legacy Code Workshop
1.5 Much better I think my best experience is the refactoring of the legacy code. I got many improvement from the the workshop. I have no comment for this workshop. Yes Show
Legacy Code Workshop
1.5 Much better 1. I had trouble because of intrinsic function with the code I am working on. 2. Spent big part of the workshop writing simulation function. 3. But since I have managed to make simulation function working I can write test cases later. 1. People who already have the framework embedded in the code gain most, as other fight to make CPPUtest work with their code. Maybe a TODO list can be given with guides that some of us can do before attending the legacy code workshop Yes Show
Legacy Code Workshop
1.5 Moderately Get valuable feedback from James , while facing problem when implemented CPPUTest on legacy code. Learn more technique to deal with legacy code. Make sure the legacy code test environment are prepare and can be build. So that there are chance to apply the concept or skill learn in TDD training to apply when on workshop. Yes Show
Legacy Code Workshop
1.5 Much better It's great that we can have a chance to relate our code implementation and how we can improve it over time using TDD methos make having working unit testing environment as a prerequisite to the workshop Yes Show
Legacy Code Workshop
1.5 Much better Maybe its better to get the workshop participants to setup the framework prior to training as a training pre-work - e.g. provide steps etc. With that, workshop participants can start writing test cases immediately and focus on the real problems. Yes Show
Legacy Code Workshop
1.5 Much better It feels like working but I like the way where we are paired and things get faster that way. A day and a half seems like not enough. We should have prepared the framework before coming in to this Legacy Code Workshop so that time are save. Yes Show
TDD Workshop (new code)
2.0 Much better NA Yes Show
TDD Workshop (new code)
2.0 Much better It helps me to feel convinced that we can apply the methods learnt right away More the number of days are for the workshop, more are the chances for us to get the consultation. Yes Show
Legacy Code Workshop
1.5 Much better More guide. Yes Show
Legacy Code Workshop
2.0 Much better It's a good way for me to see how TDD can be applied to the code I am working in I think a follow on session may be useful in case we run into further problems. However, since James offered unlimited support after the class, this may not be required. :-) Yes Show
Legacy Code Workshop
1.5 Much better Worked on current project stuffs, and James was able to help when needed. students should be encouraged to bring in the hardest assignment they have and can coped. This will help to learn more in short duration Yes Show
Legacy Code Workshop
1.5 Much better maybe two whole days would be better to get more questions to be discovered and be answered. It takes long time to get the test suite ready. Yes Show
Legacy Code Workshop
1.5 Much better Good to emphasize the training from the course It was good; longer might be better Yes Show
Legacy Code Workshop
2.0 Moderately Integrating CPPUTest was *much* easier than I expected. Having the VM prepared up front was key. A little more guidance/knowlege on how to set up and run Eclipse to take advantage would be good. Most of us had never used Eclipse before. Yes Show
TDD Workshop (new code)
2.0 Much better I looked at the application "C" code for existing energy meter test stand. I believe my approach was influenced by the preceding TDD lectures about test first and refactoring. Yes Show
Legacy Code Workshop
1.5 Moderately Yes Show
Legacy Code Workshop
1 A little yes Show
Legacy Code Workshop
1.5 Much better yes Show
Legacy Code Workshop
1.5 Much better yes Show
Legacy Code Workshop
1.5 Much better yes Show
Legacy Code Workshop
1.5 Bring it on! yes Show
Legacy Code Workshop
1.5 Moderately yes Show
Legacy Code Workshop
1.5 Much better yes Show
Legacy Code Workshop
1.5 Bring it on! yes Show
Legacy Code Workshop
1.5 Bring it on! yes Show
Legacy Code Workshop
1.5 Much better yes Show
Legacy Code Workshop
1.5 Bring it on! yes Show
Legacy Code Workshop
1.5 Moderately yes Show
Legacy Code Workshop
1.5 Much better yes Show
Legacy Code Workshop
1.5 Much better yes Show
Legacy Code Workshop
1.5 Moderately yes Show
Legacy Code Workshop
0.66 Much better yes Show
Legacy Code Workshop
0.5 Much better yes Show
Legacy Code Workshop
1.5 Moderately Very good -On the october class~ poeple from the same team should continue with the test projects we started creating -Even though in October new people can continue on the existing projects~ they should still feel the pain on getting a piece of our legacy code into CPP U test. Maybe they should feel the pain for half a day and then move on to the other existing project to continue on. -People on the October class should work with the people that took class in September to setup the environent ahead of time. yes Show
Legacy Code Workshop
1.5 Bring it on! As a new member to the development community here in Atlanta~ it was nice to be able to get a glimpse of everyone's role in development down here during the workshop. I thought you did a great job of listening to the explanations of the existing code and suggesting starting points for test refactoring. No improvement necessary. yes Show
Legacy Code Workshop
1.5 Much better good instruction and exercise. code refactor yes Show
Legacy Code Workshop
1.5 Bring it on! Very good -- even though the programming environment we had was in LabView~ but working on learning to apply TDD with peers was very fruitful and fun. Including expertise~ ideas for environments such as Matlab~ LabView~ etc. yes Show
Legacy Code Workshop
1.5 Much better I found it helpful~ but would have been more helpful if I had my own code to work on. Extended programming sessions would have been greatly aided with secondary monitors. This is more a host responsibility but I think the workshop would have been more productive being on the SLB campus where docking stations and secondary monitors could be set-up (at least for the workshop portion). yes Show
Legacy Code Workshop
1.5 Moderately Good tool for testing code. Please give more examples that make us better understand~ not only on EE area. yes Show
Legacy Code Workshop
1.5 Bring it on! It's quite impressed to realize how bad I did before. I got many valuable concepts~ ideas~ and advises in this course. I don't know. It's good enough beyond my expectation. yes Show
Legacy Code Workshop
1.5 Much better I learned a lot during the legacy workshop than TDD training. I made the unit test to work for fortran environment. I also unit tested one of the subroutines in my project. This will certainly lead me to test other subroutines in my legacy code and refactor the code whenever possible. More time should be alloted for the workshop. Although the intructor was very knowledgeable on TDD~ he never worked with unit testing in fortran environment. Hence~ I would like to see the workshop to cover TDD in other languages as well rather than focusing only on C/C++. yes Show
Legacy Code Workshop
1.5 Bring it on! It was helpful to be away from regular work to focus on getting over the hump and issues involved in setting up a proper working environment. The help was useful. More experts available. yes Show
Legacy Code Workshop
1.5 Bring it on! It was interesting - I started from scratch but my colleagues made some discoveries in their legacy code yes Show
Legacy Code Workshop
1.5 Moderately How to cut the tightly coupled dependency. It was helpful if we can share the technique each person learned through workshop. yes Show
Legacy Code Workshop
1.5 A little yes Show
Legacy Code Workshop
1.5 Moderately First step (environment setting and code build) was most difficult. yes Show
Legacy Code Workshop
1.5 Bring it on! Really great. Started to write unit tests and refactoring of our code base~ Not sure. I like it as it is. yes Show
Legacy Code Workshop
1.5 Much better I could set up testing environment for our product. I might be helpful to create FAQs in your workshop experience. yes Show
Legacy Code Workshop
1.5 Bring it on! I tested a class that manages a double-buffer for TI processor. I decoupled RTOS using fake and tested it. Might be a good idea to invite some people who took this training before for knowledge sharing. yes Show
Legacy Code Workshop
1 Moderately I worked in paire group. More than half in exercise time~ we tried to remove dependencies in target class. And 1st class we chosen we gave up to test. And we made mock class and test class for mock and target class. After we tested classes we refactored test class. yes Show
Legacy Code Workshop
1.0 Bring it on! Looked at the source code with everyone and refactored it. I enjoyed it~ so it could be longer. yes Show
Legacy Code Workshop
1.5 Much better I learnt a lot on TDD. I was not convince before going to the training. Working on my own code prove me that I can write better quality code just by thinking first on what I want to do with my code. I think I would be better to get the installer of cppUtest before the course. yes Show
Legacy Code Workshop
1.5 Moderately A little bit struggled at fist. Later on~ I made small steady progress. yes Show
Legacy Code Workshop
1 Moderately more challenging than start a new TDD project fresh. yes Show
Legacy Code Workshop
2 Much better Very useful to apply TDD to our actual environment. No suggestions. yes Show
Legacy Code Workshop
2 Much better It was great to see the test harness actually functioning in our codebase. This gives me a great deal of confidence that I could extend TDD from these initial tests. Working in teams. A single person from a group is at a disadvantage. If several people from a group go to the class they can help each other understand how TDD can work in their environment. yes Show
Legacy Code Workshop
1.5 Bring it on! It was extremely useful to bring in the test harness into my project environment~ and we'll be able to apply it immediately. I'd highly recommend that the participants use eclipse or another common IDE. yes Show
Legacy Code Workshop
1.5 A little It is a good workshop to learn TDD Probably spending a bit more time explaining the solution to each problem. yes Show
Legacy Code Workshop
1.5 Much better Very useful to apply knowledge to real problems. Would benefit from other team members also attending. There is great synergy in working together in this workhop as a team! yes Show
Legacy Code Workshop
1.5 Moderately Found out a very different way to approach development giving unit testing more importance. Maybe more examples with legacy code. yes Show
Legacy Code Workshop
2 Moderately Very useful in introducing techniques I can use in my legacy code. I need to spend the time to read and digest the blog articles related to legacy code to get a better understanding on how to implement appropriate techniques in my work~ but now I have some places to start from. yes Show
Legacy Code Workshop
2 Much better yes Show
Legacy Code Workshop
2 Much better It is hard to find an isolated module for testing~ and it is hard to cut the decadency to other modules~ for example~ to find the header files~ the function declarations. One of the challenge is in FFF. You can give a check-list for FFF implementation. A wiki page will help. yes Show
Legacy Code Workshop
2 Much better I was sceptical about how much of TDD can be done for code that is primarily made up of templates C++ templates. This course showed me a way forward in terms of treaing compiler output as a test output. CppUTest installation ran into a few issues. Having up-to-date zip files can help. yes Show
Legacy Code Workshop
2 Much better Very good It can precede with an example of Legacy code being adapted to TDD. In our case we directly started with our code yes Show
Legacy Code Workshop
0.5 Much better It was great to get help with starting to make unit tests for legacy code. Without the help~ it would have been much harder to get started. yes Show
Legacy Code Workshop
0.5 A little I was helpful to have assistance getting up and running on practical code. I would suggest that you schedule your time so that you can be present for the exercise. It was frustrating for me to have you gone when a question came up. More time than a half day. yes Show
Legacy Code Workshop
2 Much better it is impressive training. trainer provide feedback on code which i work on. yes Show
Legacy Code Workshop
1.5 Much better - initial time to setup first TDD testcase for legacy code is huge. But once we did the first one~ the rest is flowing along nicely. - Actually find one bug after writing 2 test cases. - explain more on the FFF and mock method will help remove compiling dependence~ as well as help creating unique test cases that cannot be done off target. yes Show
Legacy Code Workshop
2 Bring it on! All the problems anticipated / discussed were present in our code. It was good to see the strategies work on production code. I think making people do Agile development during the Legacy Workshop would be helpful. yes Show
Legacy Code Workshop
2 Much better Good When someone has a problem~ stop the class and solve it in front of everyone. Maybe get them to plug their computer into the project and do it together in public. yes Show
Legacy Code Workshop
2 Much better It was good experience to appy TDD on legacy code. I also discovered how useful FFF could be to simulate different behavior of underlying modules. yes Show
Legacy Code Workshop
1 Bring it on! Great way for us to start applying what we learned on existing code. yes Show
Legacy Code Workshop
2 Much better It's very helpful in picking out design issues based on SOLID principle. work in groups yes Show
Legacy Code Workshop
2 Much better Interesting~ challenging and humbling. Like first learning to ride a bike without training wheels Sometimes helping people with the more difficult problems delayed others who just needed a quick fix (dumb question) yes Show
Legacy Code Workshop
2 Moderately quite difficult to get my legacy code even running in the environment. yes Show
Legacy Code Workshop
2 Much better Found it more difficult to use TDD for legacy code than what I originally thought. yes Show
Legacy Code Workshop
1.9 Bring it on! Good~ took a while to get Keil code setup and running in Codewarrior~ and GTest took a while too Clones of James yes Show
Legacy Code Workshop
2 Bring it on! Managed to setup my in code in 2 hours because the code was already well organized. Now I can start on focusing on more interesting test cases that could not be envisaged before yes Show
Legacy Code Workshop
2 Much better Had an eye opening experience with the amount of dependencies I have allowed to occur in my legacy code. The effort required to get the first test to run will be great but the payoffs should outweigh this work. Personally a bit more consideration from myself when choosing code to use. I chose one of the tougher sections to attempt. yes Show
Legacy Code Workshop
2 Moderately 1. Message buffer checking (new function). 2. Data processing function (just ported and started a small part of code testing~ still on the way) I brought up relatively simple code (which should have been)~ but too simple and isolated~ I could not receive a good gain. If there is another workshop~ I try to find the one will need some trick to port. yes Show
Legacy Code Workshop
2 Much better Sorry this is the part that I don't recall much or I may have confused which is the Legacy part. yes Show
Legacy Code Workshop
2 Moderately Working on build testing harness for PLC code yes Show
Legacy Code Workshop
2 Bring it on! very helpful because I am using my actual codes and I can get help from the teacher and colleagues in the class yes Show
Legacy Code Workshop
2 Moderately I ended up pursuing a wrong-track approach to working with code relying on a lot of custom compiler commands/types by trying to include the custom libraries so my overall output was low~ but I learned a lot about the way to get into the nitty gritty of getting existing code into a way to implement TDD. Much more valuable than just a theory course still leaving me confused on how to implement the setup myself afterward. Even more people to help would have been beneficial. yes Show
Legacy Code Workshop
2 Bring it on! frustrating in the beginning but once the setup is done it will be very beneficial you spelled test wrong under the Post-Training Feedback header. you typed Legacy Fest Feedback underneath TDD for Embedded C Feedback yes Show
Legacy Code Workshop
2 Much better Fairly smooth More people to provide help when you think you need it. yes Show
Legacy Code Workshop
2 Much better I have now a working environment that allows me to write tests on my baseline structure. This was my main objective. I have also identified a couple of legacy modules that could get good benefit from unit tests without too much burden. - yes Show
Legacy Code Workshop
2 Much better warn user that they will have to select a function of their own code (with few dependencies). yes Show
Legacy Code Workshop
2 Bring it on! It was a good start. Some problems with types that we need to resolve (as expected). 0 yes Show
Legacy Code Workshop
2 Much better Not so much I expected. For the course preparation asked to prepare a functionality of the code to test. yes Show
Legacy Code Workshop
2 Much better Legacy workshop is really necessary. Getting into TDD is difficult in the beginning~ and the help is greatly appreciated. Without this~ we might not apply TDD in our work. Better understanding on the behaviour of complex features: we might control that each block is correctly behaving~ whatever we throw at him~ and then maybe find some of the issues we are chasing more easily. It will also help to gain some confidence on the bug fixes yes Show
Legacy Code Workshop
2 Bring it on! I was suprised how easy it was to integrate the TDD framework with my embedded softwre baseline and get the first 2 tests already working. yes Show
Legacy Code Workshop
2 Much better Very hard to automate test if the design does not allow it (dependancy and abstraction). The great difficulties came from our code not being easily testable. yes Show
Legacy Code Workshop
2 Much better Interesting topics~ facts and techniques on legacy and refactoring. Setting up TDD for a legacy project: these things must be done anyway so better have an expert readily available to help actually get started during the class (rather than learn techniques only~ go back to one's desk and possibly losing interest into actually _doing_ it...) yes Show
Legacy Code Workshop
2 Much better yes Show
Legacy Code Workshop
1.5 Much better yes Show
Legacy Code Workshop
2 Moderately yes Show
Legacy Code Workshop
2 Moderately yes Show
Legacy Code Workshop
2 Moderately yes Show
Legacy Code Workshop
1.50 Bring it on! yes Show
Legacy Code Workshop
2 Much better yes Show
Legacy Code Workshop
2 Much better yes Show
Legacy Code Workshop
2 Bring it on! yes Show
Legacy Code Workshop
2 Moderately 1. Working with peers on SLB code was extremely beneficial. Setting up environment for TDD for SLB use~ and the support group that came out of the class was excellent. 2. The feedback that the previous TDD batch at SLB passed on to us to be prepared for the Legacy Fest was valuable. 3. Volunteers that helped during Legacy Fest added value to the Fest and to get all the participants on board with the set up more smoothly. For us to be able to get the most out of the Legacy Fest~ James alone should not be left to handle 20 participants. 1. Last day's arrangement of tables was more helpful. 2. Similar to pre-TDD workshop that we had in SLB~ a pre-LegacyFest workshop from the TDD support group at SLB will help. 3. The experience at Legacy Fest and best-practices should be shared with the participants of the next TDD classes. yes Show
Legacy Code Workshop
2 Much better CPPUTEST is a good method of testing. Was able to set up the environment quickly and was able to start writing useful tests More time spent on writing tests on code that attendees bring. yes Show
Legacy Code Workshop
2 Moderately I tried not to mess up the production code but I found out that some of the header files were redundantly included in the source file so I am glad that I could clean things up yes Show
Legacy Code Workshop
2 Much better I liked the idea of improving legacy code in small steps. We did not get to the last exercise that focuses on legacy code~ and that may have helped practice some techniques to apply on legacy code. yes Show
Legacy Code Workshop
2 Moderately Very painful in applying TDD on the legacy code I don't know. Maybe the best way is to re-write the whole thing with TDD techniques. yes Show
Legacy Code Workshop
2 A little wish there was no legacy code yes Show
Legacy Code Workshop
2 Much better yes Show
Legacy Code Workshop
2 Moderately Working for over a year with the legacy code. Whenever there is a change needed - We should write a test for the code to be changed - Refactor the code - Fix the code and make sure nothing is broken and the test still passes By time~ we will have many test cases running in the legacy code and this will help us a lot for future changes. yes Show
Legacy Code Workshop
2 Bring it on! I did not notice that my code is already legacy until tested. More exercise yes Show
Legacy Code Workshop
2 Much better yes Show
Legacy Code Workshop
2 Bring it on! yes Show
Legacy Code Workshop
2 Much better yes Show