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

Why are you attending this class?
Boss
Show
I am aware of TDD basics, want to know about the internals or any complexities associated with TDD.
Show
Have been nominated. Would like to know more about TDD
Show
Implement TDD in HARMAN, I need to train the engineers after this training.
Show
To improve unit testing at work
Show
To understand what is TDD, and how to apply in my daily work
Show
TDD let you write better code. I want to learn more
Show
To improve delivery time and quality
Show
Invited to join. Want to guide junior engineers to focus more on tests, not just because told.
Show
Get kown to TDD, incorporate it into software construction process and act as a multiplier in team.
Show
To improve upon my coding skills and reduce time on debug issue.
Show
To learn about TDD and how to use it practically
Show
I think it might change the way I look towards developing a code. Fewer bugs than the usual way.
Show
learn about TDD
Show
learn about TDD
Show
To understand and implment TDD in our organization
Show
I was asked by the manager and I agreed.
Show
I was chosen to take part in this course. I have hope, that it can speed up my work
Show
I dont have much idea about tdd. Would like to know more about it and how to achieve a better coding
Show
Because my boss made me. That guy is a real jerk!
Show
To get an introduction into the process side of the software development.
Show
My manager requests me to learn it.
Show
to get a holistic understanding of the problem solving approach and apply tdd to it
Show
I want to make my code less buggy.
Show
So I can teach it :)
Show
I read your book and I want to learn how to implement your concepts in my daily work
Show
Wanting to decrease time spent on test and debug. I'm hoping to accomplish with TDD.
Show
Process improvements to catch issues earlier
Show
Want to broaden my knowledge on different design philosophies.
Show
Requirement
Show
I think TDD is a good way to combine test with development. I like that it's a process, not a tool.
Show
I think TDD is a good way to combine test with development. I like that it's a process, not a tool.
Show
I'm not.
Show
To learn more about how to apply TDD to firmware development.
Show
50% to support the team direction, 20% curious, 30% skeptical.
Show
boss required it
Show
To learn from someone who knows their stuff about how to write really good firmware code
Show
space programs certification
Show
Mandated by my company.
Show
The rest of my team have become true believers and I am the lone holdout.
Show
I want to create high quality project by reducing the number of bugs our teams are producing
Show
To establish mental model how to apply TDD in everyday development tasks.
Show
I want to master TDD and improve my development toolset
Show
Hear the pitch for TDD to see if hype is real See example & understand methodology/thought-process
Show
- I have heard good things and want it in my tool kit. - I want to be a better programmer
Show
To help inform best practices and improve code quality
Show
I want to find out how to write tests efficiently so I can get the benefits of TDD
Show
To see if my ideas of TDD match up with industry standards and scoff at the deltas :)
Show
When working in application development (C# .NET) unit/integration testing was integral to software development workflows. I would like to bring that into my current role of developing embedded development.
Show
Increase fluency. What to get better at making rapid TDD progress in legacy codebases. Less late nights and weekends getting a framework in place...
Show
Interested in learning more about TDD
Show
In previous organizations I've worked, there wasn't a focus on testing. My co-worker shared 'Test-Driven Development for Embedded C' when he joined the org and I ended up purchasing a copy. After found this training while looking for more resources.
Show
I'm interested in TDD, and especially interested in bringing it to embedded systems programmers. I've used it in my projects, and have had success bringing it to my group, but I want something to be a success story for TDD in other projects.
Show
I want to make better software, faster. I want to spend less time doing manual testing.
Show
Required training for my position.
Show
I am a new hire in the Engineering organization and eager to start learning and adapting to including these important concepts in the projects that I get to participate in.
Show
My boss signed me up, but I am excited to gain a new skill and learn something new.
Show
This training was assigned to me by my boss.
Show
On advice
Show
I get the chance to do this. Being a senior engineer team members ask me each day for help. If I am not trained I cannot tell what is useful and what is not useful. It is not the question whether it makes sense. I am convinced that it make cents :)
Show
Company training plan
Show
I have no choice.
Show
1. boss told me so 2. see the chance that I can learn something or get some new ideas
Show
-
Show
For work and to learn =)
Show
I've used TDD before, but I wanted to get a real understanding of what that means to become a better developer.
Show
i think that i previously have worked a little bit like this: adding a litte functionility => testing => adding a little more functionality. it would be great to work according to a "professional" method, to get better
Show
i think that i previously have worked a little bit like this: adding a litte functionility => testing => adding a little more functionality. it would be great to work according to a "professional" method, to get better
Show
I am very interested in the TDD approaches, but I am still not sure about the limitation and challenges of this approach.
Show
I want to have a proper reference of what TDD means and which news and advantages brings, including the practices on what is the best way to apply the TDD theory.
Show
Mandatory by the company. I'm also personally invested as TDD is a standard we've been using and I'd like official training on it to improve my understanding.
Show
I want to learn TDD in embedded rust; I've a hunch the principles are the same (decouple I/O from branching logic) but, looking at our code base, shake my head: why are we so dependent on hardware for every little thing? What am I missing?
Show
i am still a newbie in TDD. would like to learn more
Show
Got an invitation from my contractor. Remembered your name from the book I bought maybe 5-6 years ago. wanted to attend.
Show
There was a single free slot, and it is a class, where I can learn a lot. I have been working at Siemens also on the automatisation of the debugger and had to use code coverage to generate IDS rules, but TDD is new to me.
Show
To grow more fluency with TDD for embedded. To grow techniques. To learn ways to explain and motivate the use of TDD.
Show
I am a software verification engineer and I hoping that TDD will be beneficial for me from testing and automating tests point of view.
Show
We were just doing unit testing for my project and I struggled with writing them
Show
Developer testing is very ad hoc and I'd like better methods
Show
I want to move my team to use TDD correctly and to address some of the inherent difficulties to use the concept in C Embedded environments. Need the suppor tof an expert
Show
Training organized by my new boss for his whole team.
Show
There was a single free slot, and it is a class, where I can learn a lot. I have been working at Siemens also on the automatisation of the debugger and had to use code coverage to generate IDS rules, but TDD is new to me.
Show
R&D Director (at the time, he is no longer with us), encouraged that the Verification Team attend along side the the Development Team due to how valuable it could be for overall progress made.
Show
To learn about TDD and how it can be applied to automated testing.
Show
Because my boss signed me up. But it certainly makes sense to increase our quality.
Show
In my small exercices with TDD i saw the benefit of thinking about testing in advance to not get untestable code in the end. It even influenced the way to design software items. I would like to get a deeper knowledge ecspeccialy when it comes to HW.
Show
It is part of the companies strategy to allign the development approach, therefore it is mandatory for every new developer. I'm glad about that, as it is hard to convince a non-software aware manager of the importance of such a training :)
Show
As a new technical lead at the organizational level, my goal is to bring automated testing into our processes at every level. I see code-level TDD as one piece of that, and I'd like to get ideas for extending those techniques to higher levels.
Show
My manager thinks it is good that the entire team attends it so that we will work better together.
Show
as a tester, I want to use proven method to deliver quality software with less bugs and in short time.
Show
To learn how it should be used in embedded sw
Show
I am curious to learn about TDD and I would like to introduce it from the start of the next project (which is coming up soon).
Show
I was asked to join the course. I was happy to join because I always strive for self improving my coding skills to become a better programmer
Show
incorporate ideas to allow parallel developments, reduce test at each release and delivering something that i can be proud of.
Show
I've been doing TDD for about 15 years, but I want to make sure I am doing it properly, and learn more techniques (test-wise and design-wise) to build up a catalog of strategies to use for new designs so I don't burden the business with risk/cost.
Show
Want to learn the agile concept and apply in work
Show
checking my self trained skills
Show
hecking my self trained skills to
Show
As part of the Meggerwide SW Group and as a firmware developer I am interested in improving code quality and easing the test procedure.
Show
The company is looking to adopt Agile processes for software development. TDD is a crucial part of this. I have shown an interest in the subject, so was nominated for the course.
Show