Training Preparation -- Why these 100 Attendees Are at TDD Training

Why are you attending this class?
To improve my professional career by having more insight on how to develop applications faster and more reliable, particularly in hardware projects
Show
To gain a much deeper understanding of why how and when to use TDD.
Show
- I really want to learn Unit testing and make it like my second nature regarless of the language that I use to program.
Show
To fully understand what TDD is. To learn the good habits and techniques and to be able to apply them in our current project
Show
Never tried TDD, we are starting a new project (~2months old) it would be the perfect time to learn and implement a more efficent method of developing.
Show
I wish to improve my workflow and be able to create more reliable code.
Show
Want to know more than just the name. Its recommended by a lot of colleagues, want to understand how it can help me and my team
Show
I came across your website a year ago when I was working at a different company where testing was all done manually, ugh months and months of filling in test steps and results in a excel sheet.
Show
Want to learn TDD
Show
Starting to get more involved in firmware development. TDD seems like it will save time and catch edge cases hard to implement on target.
Show
To gain deeper understanding of TDD which allow me to justify sending the rest of my team to training.
Show
I usually work by TDD. then I'd like to know how to apply embedded software. example learn good mocking practice.
Show
I heard about TDD from a co-worker whose been using it on his own developments. I see the benefits to it and want to learn more.
Show
I want to write better software.
Show
I have an interest in this and it's corporate provided training which makes it easy to take and pay for. I also like the Agile methodology and am interested in seeing how TDD fits with that.
Show
To change my current quick and dirty (probably ineffective) testing habits, replacing them with a methodical system.
Show
I want to learn about TDD and how it can help me improve the software I deliver.
Show
TDD seems like it will make me and the team better software developers. TDD is a positive trend for the software development community.
Show
learn TDD for C-only projects; understand how to apply TDD to firmware that needs to run on hardware (e.g. TDD for DMA SPI driver that only has problems after the MPU comes out of a low-power state)
Show
Improve delivering quality software
Show
Don't you know what's going on outside?
Show
i was "encouraged" to
Show
Improved software development velocity, decrease expensive debugging sessions. Reduce the reliance on breakpoint debugging.
Show
As my software team has just formed we decided since we are just starting out we might as well try to establish good habits from the start.
Show
I have a lighter project load during this apocalypse.
Show
Lots of new developers in my department. Want them to do software engineering not just programming and create better products in less time.
Show
Our group is trying to do things better.
Show
TDD seemed like something, since already offered, I should at least be exposed to, since at least in theory, it seems like a good idea. I will decide whether it is something I actually want to integrate into my development process.
Show
To learn more/refresh about TDD.
Show
The boss is making me do it :)
Show
suggested by management
Show
organization push development adopting TDD
Show
Was asked by management. Not my first preference. My opinion: the company needs to increase the resourcing/infrastructure for automated testing before asking developers to just "write more tests".
Show
To learn on what are the test methods and process use by others witch and standards in the firmware industry.
Show
I'm feeling kind of useless as a Scrum trainer and wondering if it's too late for me to go back to a normal programming job.
Show
I want to write more robust code!
Show
I would like to help myself (and team) get better at creating sustainable code.
Show
- To better understand what are 'good concepts'/'way of working' to create testable/tested embedded code. - What environment is needed for good (unit)tests (Do they need to run on target? With(out) the RTOS?
Show
I'm not happy with how many errors I introduce to my code at the moment. I started coding in a TDD way but I'm too slow at it. So when deadlines approached I skip TDD and more errors are found latter. So my goals are: better and faster.
Show
My team is not happy with the unit testing approach on other projects. We are trying something new on this one. I want to make sure we are on the right track and get ideas for improvement.
Show
I want to develop firmware fast, reduce debugging time, be lest paranoid that a fatal bug is going to make it to deployment.
Show
We've started to adopt unit testing. I'm interesting in learning new strategies to help with this.
Show
I want to learn TDD as our company begins to ramp up our testing frameworks. I believe that having a strong understanding of TDD can not only improve our team's testing abilities, but also improve my own coding skills.
Show
Learn methods of applying TDD to legacy code, particularly separating GUI and other views from the process and presenter. I usually end up re-writing large amounts of code to add TDD.
Show
To learn how to improve the way that I test code.
Show
I hate debugging code, especially my own.
Show
Heard about you from Elecia White (I did a show with her and Chris a while back). Learned more about TDD, decided it was a good idea.
Show
To learn about how to deliver training over the Internet, with strong curiosity about how the pros do embedded programming.
Show
I'm new to the team, and some of the other team members have recommended the class. Also, some of the coding standards and development processes adopted by the team are inspired by the course - so it makes sence for me to adopt as well.
Show
I hate making erros and hate event more finding erros mad by others. I want to spend my time being productive while trying to ship fewer errors. I want like some kind of defensive measure, which helps me in find my own errors early.
Show
I have been having a difficulties with testing in general when developing embedded software. It takes so much time to test.
Show
To learn more how to develop a good software.
Show
my boss asked me to sign up and take it; other folks said it was pretty good.
Show
* To get a common language regarding test and code in our team * To get a common understanding on good/bad tests in our team * To refresh on TDD habits
Show
To refresh my knowledge on TDD and because I want the team to have a common understanding of the principles and values of TDD.
Show
A colleague have recomended the course.
Show
I felt that I need to have hardware mocking explained to me, reading the TDD book exposed me to a lot of ideas at once and I need help focusing on what's important.
Show
It's one of my employee goals. I want to be more effective at my job and generate easy to read/modular code effectively
Show
My manager made me
Show
To learn TDD concepts and determine if it is right for our group
Show
Because my coworkers took it last year when I wasn't an employee yet and they offered me to take it and I said yes. Also, I'm curious to know what this training looks like.
Show
Pawel says it's a good opportunity, I have no idea what TDD is, and it's for Embedded C/C++
Show
It's because my manager told me told, and also because I want to learn more about TDD
Show
My manager recommended I attend. Probably because he doesn't think I do enough testing.
Show
like to learn more and read James' TDD code before
Show
I believe we don't test our code well enough. I'm looking to learn more about test methods which will increase quality and confidence in our system.
Show
We want to see if this will be a good learning experience for our group
Show
I like the concept if getting working code quickly and reduce bugs
Show
The company is giving us the chance to do it, and I think it is a great opportunity to learn how to perform robust testing. It can save a lot of time and it can help to gain confidence on the code you write.
Show
I want to learn how to organize and reach to our goals in a better way. I have been following Barr Group for years and I think I could learn a lot from your trainigs. That is why I recommended Barr Group's trainings to the company.
Show
As I said, we have started with TDD not long time ago. I want to attend it so that we can learn more, see what we are doing wrong, what should we change, new approaches, etc.
Show

Show
To learn and improve my software developing skills
Show
Because my boss wants we improve our work quality and I also think it's good for us.
Show
Once you start working in a business do a good quality job or simply do not do it. I like doing good quality job.
Show
I think it is neccesary to know TDD to be a good programmer
Show
I want to learn this technique to be a better programmer. I have been wanting to have this type of training since I started to follow Barr Group, so I'm happy I got the opportunity.
Show
I'm interested in improving my C development skills
Show
The company has offer to do it and it looks interesting
Show
I'm curious about how TDD works and how it can be used in embededd systems.
Show
I want to learn more about this so that on future and current projects I can employ it and have it benefit myself and my team during our development process.
Show
I want to follow best principles like these to be a better engineer, and to teach others around me. I like carrying lessons forward. I hope to apply the skillset to other work with Python and C++ as well.
Show
I'm interested in this paradigm in practice to potentially make it a standard for our development teams.
Show
Growth as a SW developer.
Show
After chasing bugs in legacy code, I'd like to implement tdd structure for that project. Also, I'm starting to manage a project, and I've seen the benefits of tdd in my other project.
Show
I am hoping to develop some best practices for embedded development.
Show
I want my code to have less errors and be able to re-check itself when I make changes.
Show
I want to improve my overall embedded coding skills. I haven't had any formal instruction on how to test embedded systems, so this seemed like a really useful class.
Show
My superiors have taken this class before and they recommend it to all junior staff.
Show
I'm working with legacy code for an embedded micro-controller that has no unit test strategy. I would like to test parts of it on a PC and I'm looking to learn techniques to apply.
Show
I would like to expand my toolbox for embedded software testing and learn the skills to more easily integrate TDD into my projects. I also want to learn to efficiently reduce the number and scope of tests requiring hardware-in-the-loop testing.
Show
I want to improve the software quality of our organization. I've tried using TDD on previous embedded projects but the time required to look up how to do things in C and adapt build systems meant I couldn't do much due to time constraints.
Show
To have more formal training on the subject. I really like what I've been able to gain from my own reading but wanted to go further.
Show
Want the ability to run more comprehensive tests on code
Show
Arranged by our company. Although we apply test driven development it would be good to look into what new concepts the TDD can bring in.
Show
Colleague recommended.
Show
Because my boss told me to.
Show
To see if there is a way to improve my test coverage without significantly impacting on the time to run sanity checks.
Show
To enable a common testing methodology in the office as each group has there own way of doing things currently.
Show
There was a spare space at short notice!
Show

Make this into a word cloud

Select text below (triple click), copy, then try one of these tag cloud generators
jasondavies word cloud generator - colorful
tagcrowd - lets you show counts