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

Why are you attending this class?
Assigned as a new hire, plus it's good to refresh my knowledge.
Show
Because I want to get better at TDD
Show
Because I won it in a competition.
Show
Company requirement
Show
Company requirement
Show
Desire to improve quality and efficiency of testing, in order to create higher quality products.
Show
Developing firmware smoothly and teach to students or any learners how they develop firmware.
Show
Getting deeper understanding of TDD and practical experience with different concepts related to that
Show
Have been struggling to develop unit test cases in embedded software
Show
Hopefully to find better and easier ways to accomplish the "boring" parts of development
Show
Hoping to gain insight in to faster code development by having some structure in place
Show
Hoping to raise the technical standard of BSU's hardware labs
Show
I am attending the course to in hopes to learn better code architecture strategies
Show
I am familiar with software testing but I can't talk about concepts with peers.
Show
I find embedded C interesting and I want to do more of it. To make that happen, I must improve :)
Show
I have a legacy project that I want to refactor and setup tests
Show
I know there is better ways of writing and testing code, however it is not done yet at work
Show
I like to learn how to apply TDD practically
Show
I see value in TDD, but has/is difficult with legacy stuff
Show
I try to attend all possible trainings to improve myself as a professional.
Show
I want to be more efficient at applying/championing TDD to future work
Show
I want to become better, and make things go more smoothly.
Show
I want to better test my code. To create reliable code.
Show
I want to develop the finest TDD skills I can, and be better able to coach colleagues to do so.
Show
I want to get better at delivering high quality code and I see being an expert in TDD as the way
Show
I want to see generic TDD before figuring out how it was implemented here in legacy code
Show
I want to see if TDD is all that it's cracked up to be (actually useful) or if it's just a buzzword.
Show
I want to understand how to 'think' properly about testing at the macro level
Show
I want to write code that doesnt embarrass me when I share it.
Show
I want, and in extension my company, to start testing our products before QA team gets involved.
Show
I wanted more exercises after reading the book
Show
I was asked to :)
Show
I was asked to and subject is interesting
Show
I was recommended it by Steve Branam and most recently I'm finding it could be useful for FPGA's.
Show
I'm attending because my manager asked, also I'm curious to learn more.
Show
I'm interested in refining my development style.
Show
I'm looking for ways to implement tests and mock drivers on my computer.
Show
In order to get better at TDD.
Show
Information declined.
Show
It was offered to me, and I'd like to write better tests
Show
It was suggested by my manager. I'm not a software developer by trade, but would like to learn.
Show
James convinced me it would be great for me and my team :)
Show
Learn more about embedded development process
Show
Learning the the TDD, and using it when I have to write code. I don't work on big projects though.
Show
Manager suggested it and it sounds interesting to me
Show
Mandated by manager
Show
Mostly to learn more about embedding programming (not so much TDD)
Show
My employer would like me to undertake this training.
Show
My manager set up the training so she encouraged us to attend plus it sounded relevant to my work.
Show
My manager volunteered me for it.
Show
My team enrolled as a group learning project to help our company establish a standard.
Show
NA
Show
Nominated by my Organization
Show
Our firmware group at Whisker plans on adopting TDD to consistently deliver quality firmware.
Show
Out current testing approach isn't working. I am interested in other approaches for testing.
Show
Professional development, and whilst I have learnt TDD on the job, I've never had a formal course.
Show
Required
Show
Slow on work and a good intro to the concept to integrate TDD at company
Show
Standardize how we do testing
Show
TDD is controversial, I want to grow a pragmatic understanding of when and how it should be used.
Show
TDD is great approach.I want to learn it, so I can help my teams to implement it and improve quality
Show
TO IMPROVE MYSELF AND TEAM
Show
The real reason is because I'm interested in learning in general. Especially if it's something good.
Show
To actually deliver high quality firmware.
Show
To deep into the knowledges from the TDD book.
Show
To gain better knowledge about TDD in the embedded space.
Show
To gain some experience in an aspect of software that I have not encountered before.
Show
To get some new or old ideas for testing and developing software more efficiently
Show
To have better tools for refactoring code
Show
To improve my design and test efficiency while creating robust software
Show
To know more about TDD and how to accommodate it in my SW development process.
Show
To know more about TDD and to develop SW with great quality before test cycle
Show
To learn about TDD
Show
To learn better methods of coding - even if I don't agree with them, I would like to understand them
Show
To learn more about automation, left-shift and white-box testing.
Show
To learn more about test driven development, become a better programmer.
Show
To learn new methodology.
Show
To learn new ways to develop more efficiently
Show
To learn something new, to get new ideas for solving old problems,
Show
To see if TDD is better understood, appreciated and internalised through a workshop instead of book
Show
To understand how to code and test simultaneously and deliver the code with high quality.
Show
Volunteers were needed (and I was kind a interested to learn more about TDD)
Show
Want to go from using it a little bit to using the correctly, especially with legacy code
Show
Want to understand tdd properly.
Show
Wanting to gain some insight testing and re-verification
Show
because I am wanting everyone in my team to develop this best practice and culture
Show
desire to learn
Show
employer assigned to me
Show
explore different methodologies, understand if this would fit well in our development process
Show
i have received feedback that I need to improve my TDD skills
Show
learn the art of TDD; how to write tests to drive the code, how to do abstraction/interfacing
Show
my boss said to
Show
seeking to enhance my skill and knowledge
Show
someone signed me up, plus it'll be helpful for a project i'm working on
Show
to learn
Show
to learn a new method to develop software and try to apply it in our project
Show
to learn how my life can be made simpler when coding, and producing good modular code
Show
understanding the test driving code for quality development.
Show
want to learn the fundamental knowledge of TDD, hope it will be used in daily work
Show
what "level" to write the tests at? (e.g. external interface only etc)
Show