| 0 |
4 |
python |
c++ |
test, cmake |
im excited to learn about test driven development because I'm just someone who likes to learn |
unit tests |
ai system |
git, jenkins, vs code |
5-30 minutes |
I make sure that the code is clean and passes all the tests |
when its hard to follow |
I check for clarity and readability |
50 |
25 |
25 |
It challenges me and its fun to build things |
I don't like when one small bug drives me insane because I enjoy the creating something part more |
from what I can see, it seems like you should have test cases before you even write code |
my job nominated me |
Show
|
| 6 |
19 |
C++ |
C, Python |
gtest/gmock |
Previous TDD convert! |
Write unit/component tests after coding completed (in current role, previously used TDD in another job) |
C++ firmware |
Visual Code |
1-5 minutes |
Internal standard, based on Misra |
Gut feel/review |
GitHub reviews |
20 |
30 |
50 |
Designing new components |
Bug fixing |
Used in previous job fir 2 years |
Refreshed, want to introduce TDD into current team |
Show
|
| 4 |
14 |
C |
c++, python, Go |
Gtest |
i am a software engineer with 8 years exp like to do codding in c, c++, python and go. working on AI projects |
Unit test and integration test |
s390 |
VS code, IBM bob |
1-5 minutes |
depends on the project |
if its big and unable to understand the context wen reading |
2 round of manual code review by sme |
30 |
30 |
40 |
problem solving |
debugging issues |
better practice |
learn and get something new from this |
Show
|
| 4 |
14 |
C |
c++, python, Go |
Gtest |
i am a software engineer with 8 years exp like to do codding in c, c++, python and go. working on AI projects |
Unit test and integration test |
s390 |
VS code, IBM bob |
1-5 minutes |
depends on the project |
if its big and unable to understand the context wen reading |
2 round of manual code review by sme |
30 |
30 |
40 |
problem solving |
debugging issues |
better practice |
learn and get something new from this |
Show
|
| 30 |
5 |
C |
Python |
none |
I took a long break from C development and recently got back into it. |
Typically, it is best to test on the actual hardware if available. If the actual hardware is not available, we have evaluation boards that have the same controller and we are able to scope pins. |
Our fw runs on a Renesas 'S5' microcontroller w/ a 32-bit Arm proc. Target is ZSeries Power supplies |
MS Visual Studio, Renesas e2 Studio |
1-5 minutes |
Conventions developed overtime by this small group of fw developers documented in firmware specs. |
If it does more than one thing |
We have periodic code review with our small team, especially at the start of new programs. |
30 |
50 |
20 |
It is never boring. FW is smaller scale, I get to own design and implementation. |
Some issues are not easy to debug, some problems are seen rarely or intermittently. |
Not much |
I was asked to join, but this seems like a good opportunity to harden my fw development skills |
Show
|
| .4 |
5 |
C++ |
C
Java
Python |
CTest
GTest
JUnit |
Had previous role out of college doing SW Verification Testing in Aerospace industry before coming to IBM |
Build Gtest suite w/ unit tests for new code coverage, then run existing unit tests and integration tests, team Jenkins pipeline tests on PR submission (end to end, smoke tests, integration) |
Software stack for Z AI Enablement |
Bob, VSCode, git, github project board, jenkins |
31-60 seconds |
Team uses Google C++, personally I think through solution paths, prototype integration, then test |
>3 nested loops, repeated logic, function has multiple responsibilities |
submit pr w/ template, include any necessary comments and output, Leads/Stake holders leave comments |
30 |
30 |
40 |
Problem solving, learning about/considering tradeoffs, building and seeing updates in real time |
Bad docs between teams, unclear requirements |
Write tests describing intended behaviors and failures first, then craft solution |
Nominated for class, good learning experience as new hire |
Show
|
| 1 |
3 |
C |
Python |
Pytest |
I'm excited to learn more in this course! |
Pytest scripts and a regression suite |
Our systems are used for Qubit control |
GitHub |
5-30 minutes |
We have a loose set of standards detailed in our repos |
When you have repeated code that should be pulled out. |
We add who we think knows the code as a reviewer and need just one approval. |
30 |
30 |
40 |
I enjoy the engineering challenge of it. I like developing code from the ground up. |
The overhead time not used for coding. The testing, reviewing, etc |
Not much |
I was nominated by my manager, but I am looking forward to it. |
Show
|
| 20 |
30 |
Python |
Java, C/C++, PLX |
PyUnit, JUnit |
What would like to know? |
Python |
z/OS, Linux |
Eclipse, IDZ |
5-30 minutes |
We follow standard PLX, and Shell Scripting standards. |
Haven't thought about this. |
For small code changes - GitHub reviews.
For complex code changes - live code reviews. |
0 |
90 |
10 |
Everything... ok I take it back... there's some things I don't like, but writing software is a hobby |
Nothing... ok, I don't like code reviews and long planning meetings. |
Officially not much, but I've been pushing developers to write tests. |
Besides being signed up, I'm in a function test role and Test Driven Development sounds interesting. |
Show
|
| 4 |
10 |
Python |
C++ |
None |
When I write code, it's mainly for research purposes which can differ from traditional SWE |
I usually check my outputs match my expected outputs given the inputs (I am a researcher). |
Don't have one |
Jupyter Notebooks, Python |
Under 10 seconds |
Write clean code, make things reusable (OOP) |
When it does more than one the name indicates |
I am the only person writing code and reviewing my own code |
60 |
10 |
30 |
I like solving real problems thorough code |
I am forced to use AI
Some issues take longer to debug than others |
None |
To learn about TDD, since I don't know anyting |
Show
|
| 0.5 |
10 |
Python |
C, C++, C#, Java, Scala, x86 Assembly, RISCV Assembly, Go, Dart, Javascript, Ocaml |
CUnit, JUnit, pytest, scalatest |
I'm not that interesting. |
Almost all of my code runs through functional/blackbox tests with minimal unit testing. |
My target system is an IBM Z Mainframe |
Mostly Bob/vscode and its extensions, not much else. |
1-5 minutes |
Logic must flow well and things should be easily read on first pass with comments. |
When you lose memory of previous items in the function while reading it. |
We need at least our feature leads and integration managers to review code to merge in. |
70 |
10 |
20 |
Making complicated stuff with spaghetti logic magically work. |
Constant changing of scope and requirements. |
Only by name, test driven development. |
Being exposed to new and possibly better coding practices always interests me. |
Show
|
| 18 |
24 |
C++ |
C,python,Java |
JUnit |
I have two boys, in second and fourth grade. |
Static test regressions |
Code is built for simulation with HDL RTL models to stimulate, inspect, check RTL model against code |
IBM Bob (VSCode-based)
CMake |
1-5 minutes |
Team has changed/evolved over years, not too strict/fixed, besides avoiding code smells. |
When you don't remember something from the top by the time you get to the bottom or reading it. |
GitHub-based PR reviews for involved team. |
20 |
20 |
60 |
Being detailed and improving ability to maintain and build-up. |
Maintenance and debug issues related to changes that could have been addressed with better testing |
Use fakes/stubs to reduce/remove dependencies and speed up test and iteration cycles. |
Trying to see if there are better ways to incorporate TDD into our complex code + test structure. |
Show
|
| 4 |
19 |
C |
C,C++ |
GTEST |
I am a firmware developer |
In real environment |
Embedded System |
C++ Development Kit |
31-60 seconds |
Huffman Coding Standard |
If a function becomes difficult to comprehend and does more than one task, this function is long |
We do peer reviewing of the GitHub PR |
50 |
30 |
20 |
Integrated Development Environment |
Design keep Changing frequently |
NULL |
To ensure quality of the code written has less bugs or bugs be caught early |
Show
|
| 4 |
10 |
C |
C++, Java, PL/X, HLASM |
Jenkins test harness |
I have 2 cats |
Create tests that drive code paths of what I am adding/changing |
z/OS |
. |
1-5 minutes |
Be consistent with codebase; always add change activity and flags to show where change was; comments |
when it becomes difficult to understand what a function is doing, even with sufficient comments |
Provide team with background of code change, then go line by line and review, rework offline |
20 |
50 |
30 |
always learning something new, satisfaction when solving a difficult problem |
a lot of repetitive tasks, creating design documents and maintaining documentation |
that is stands for Test Driven Development! |
it seems like a good opportunity to further develop my testing skills |
Show
|
| 1 |
7 |
C++ |
Python, C, Rust, Go, SML |
Pytest |
I grew up in Bainbridge Island, WA |
We currently use pytest in our test framework |
Embedded software for control systems |
VSCode, Claude Code |
5-30 minutes |
I'm not sure how to answer this |
I try to keep it under around 100 lines |
We have code reviews on Github from other members of our team |
20 |
20 |
60 |
I like the problem solving aspects. |
I don't usually like writing tests. |
I have touched on TDD in school. |
I was nomitated by my team to attend this class, but I want to see how these practices can be used |
Show
|
| 30 |
30 |
pls |
rex |
unsure |
I do cybersecurity analysis and test |
module trace |
z/os |
vscode |
5-30 minutes |
z/OS conventions |
insufficient registers for compilation |
required |
3 |
3 |
3 |
design |
debugging |
Heard about it in years past |
management-directed |
Show
|
| 2 |
11 |
Rust |
C++, Python |
Catch2, Rust |
No |
Just run the unit tests generated by Catch. And hope Jenkins stays green |
A Linux installation |
CLion, Emacs (Magit), Git, CMake |
Under 10 seconds |
A Word document |
When its behaviour is not fully expressed in the type signature |
Pair program everything, no formal review |
1 |
8 |
2 |
Puzzle solving. Complaining about other people's code. |
Writing tests. Having to figure out undocumented code where the intention isn't clear. |
Doing it daily for six months, nobody has explained it to me with words yet. |
I want to hate writing tests less. |
Show
|
| 1 |
20 |
c++ |
python
java
rust
|
catch
gtest
pytest
jtest |
Favorite food is sushi. |
unit tests
integration tests
end to end tests
all run every build |
embedded linux device with supporting PC work. |
clion |
31-60 seconds |
Not sure what sort of information you're looking for? |
When it doesn't fit on a screen |
Pair programming only. |
30 |
40 |
30 |
The designing of complicated systems. |
Any churn around boiler plate. |
Ideally, write tests before the code. |
No one has 'the best way' but learning how others do things can make my way better. |
Show
|
| 1.5 |
27 |
C++ |
C, Python, Java, *nix Shell |
Python built-in |
ECE Major not CS - always left holes in my learning. |
Unit-test, static analysis, Custom automated tests of various kinds. |
Arm V7 with Linux and OpenRtos. |
IDE (code completion, debugger), automated CI/ Build-Systems, AI assistants, |
31-60 seconds |
Custom Best practices for C++14 shared by existing team leads (Not sure what standard it's based on) |
Number of lines, general reability, doing too many (differnt) things etc |
Git/PRs, used to be SVN/Code-collab |
60 |
5 |
35 |
You can make the same chip/System do different/multiple things by changing the instructions |
Explosive growth/ const disruption in every aspect - can't master all, one isn't enough! |
It's a great idea. "Thank you, Zebra!" for prioritizing it enough to sponsor. |
Luckily got scheduled-in by a well-wishing supervisor. |
Show
|
| 2 |
7 |
C/C++ |
Python, Java, Some Javascript and its framework |
CPPUTEST |
hi |
Unit test, automated test, |
printers |
NA |
31-60 seconds |
NA |
NA |
NA |
3 |
5 |
2 |
complex business logic into programming. |
I like it |
my architects told me to use it |
to learn |
Show
|
| 1 |
11 |
C, Python |
C++, Bash |
CppUtest |
I get funny looks from people when they see that I am not using visual studio or some other IDE. |
Unittests when practical. Manual testing for things that involve hardware in specific states. |
Embedded QNX or Linux systems running on NXP IMX or STM ARM SoCs. |
GCC, CMake, Yocto |
1-5 minutes |
We have a long list of C++ coding standards enforced by peer reviews, more than fit in 100 chars. |
If you need more than 3 levels of indentation you probably need multiple functions. |
All commits must pass two peer reviews before merging into main |
25 |
25 |
50 |
I enjoy the technical creativity I can exercise and solving complex problems. |
Getting bogged down in I.T. world. |
You develop tests before writing code and then write your application code after. |
To learn about test driven development and the wisdom of all the CppUtest files in the repo. |
Show
|
| 0.8 |
1 |
python |
SQL, RUST |
none |
I have an engineering backround, not computer science, so the art of software is something I'm still picking up. |
unit tests, pyttests |
I've worked a lot with backend data systems. I want to learn testing for live, real-time systems. |
VScode |
11-30 seconds |
beginner |
I don't |
not frequent enough |
50 |
10 |
40 |
solving problems efficiently |
debugging, refactoring |
feels tedious as a concept but makes things easier in the long run. |
I messed up a project with very untestable code. don't want that to happen again. |
Show
|
| 3.5 |
7 |
C |
Python, C++ |
gtest |
I like turtles. |
General, non-standard methods. |
STM32 |
IAR, gcc toolchains. |
Under 10 seconds |
No explicit coding standard. |
Long as it needs to be. If components can be modularised and reused then do so. |
Done on Bitbucket, has CI/CD. |
50 |
20 |
30 |
Solving problems with minimal changes. |
Fighting archaic, clunky IDEs. |
Writing tests before developing to gain confidence that changes truly work. |
Because I want to be more efficient at writing software.
|
Show
|
| 3 |
3 |
C++ |
C#
Python |
I have not really used any test harnesses. I have seen some CppUTest and done manual testing. |
I like old US silver coins. |
Mostly manual testing. |
Printers and sometimes a Windows computer. |
I mostly use VS Code or QNX Momentics IDE. |
5-30 minutes |
Focus on writing simple, fast fixes or features for customers. |
When the single goal of the function starts doing more than that one thing. |
Almost never do any code reviews as we optimize for fast customer solutions. |
40 |
30 |
30 |
Figuring out the best path forward to get to the intended solution. |
Having to figure out what the issue is related to bugs. |
Write a test first, then develop a piece of code that passes that test. |
It is required. |
Show
|
| 2 |
2 |
C |
Python |
Unity |
N/A |
combination of static analysis, unit tests and functional testing. |
Embedded medical devices |
Common embedded C IDEs |
31-60 seconds |
MISRA |
Excessive levels of nested conditions. |
Code always reviewed by multiple members of the team before merging. |
30 |
30 |
40 |
Challenging and varied problems to solve everyday. |
Finding very niche unreproducible edge case bugs! |
Minimal as I am early in my SW career. |
To improve my overall SW dev skills for the entire product development cycle. |
Show
|
| 1 |
3 |
Java |
Javascript
Python
C# |
NA |
visual learner - I understand stuff better watching someone do it first rather than having to read a block of text |
Unit tests only |
NA |
WSL, VS code, git, docker, jenkins, jira |
Under 10 seconds |
Just standard procedure a minimalist so minimal comments and try not to cross DRY standards |
too many arguments, function is doing more than one thing |
Pair programming or AI review my code |
20 |
20 |
60 |
The satisfaction of working on a complex problem and finally solving it |
documentation |
reassurance that my code is still working with new features |
To learn to tdd better, I always default to writing code first then writing tests after |
Show
|
| 0 |
25 |
C++ |
Python
C |
Some experience of Google Test, but very limited |
I live in the UK and have spent most of my career working on Telecoms equipment, mostly embedded multiplexers and controllers for cabinet based equipment. I have little experience in Mobile base stations, but only from the high level design. |
Writing system Tests based on customers use cases. |
Telecoms multiplexer equipment. Embedded Linux. |
SVN, IAR Studio, VsCode, QtCreator |
1-5 minutes |
Generally try to follow the MISRA standards which are built into IAR Studio |
Usually when it disappears of the page or its complexity figure is too high. |
Use the Atlassian Crucible tool which allow comments to be added to individual lines of code |
60 |
20 |
20 |
I enjoy embedded programing, especially when get close to the hardware interfaces and registers. |
Bugs !!
Especially bugs that aren't caught and make it to customers. |
I am aware of the concepts having Googled it, but have no experience of it all. |
Currently between employment, and want to use time for personal development. TDD looks interesting |
Show
|
| 0.5 |
10 off&on |
Python |
Embedded C (it's been a while) |
Pytest |
I love hiking |
Pytest |
Currently cross-platform Python. In the past, PIC or PSoC. |
VS Code, Git. For embedded: MPLAB X IDE, PICkit, PSoC Creator, oscilloscope/logic analyzer, etc. |
11-30 seconds |
based on PEP 8 |
if it is playing more than one role |
~weekly meetings to go over updates and discuss changes |
30 |
45 |
25 |
It's fun turning abstract ideas into defined logic |
Having to make sure the environment is all set up correctly. And also staring at a screen. |
You write tests for expected outcomes, then write/adjust the function until the test passes. |
Our team is moving toward doing more TDD. |
Show
|
| 3 |
3 |
C |
C# |
Unity |
n/a |
n/a |
n/a |
n/a |
11-30 seconds |
n/a |
n/a |
n/a |
n/a |
n/a |
n/a |
n/a |
n/a |
n/a |
n/a |
Show
|
| 0 |
4 |
C/C++ |
Python |
JUnit, Pytest |
I came into to tech from the Marines |
Not sure I just started |
Python wrapper around a C++ api |
VSCode |
31-60 seconds |
I like to keep to a 1 responsibility per method as much as possible with good OOP |
I see more than 3-4 actions on a piece of data |
not sure I just started here |
3 |
3 |
4 |
Making things |
unclear requirments |
we create standards that can be tested then write the code to meet them |
Job said to and so I will |
Show
|
| <1 |
5 |
C |
C++, Python |
I worked on module-level testing, writing unit tests for individual components in isolation. |
I enjoy practical, hands-on work more than purely theoretical topics |
I currently test code manually on the vehicle or Testsetup and verify module behavior and outputs. |
The target system is a vehicle embedded controller interacting with sensors and actuators. |
MATCH tool chain |
5-30 minutes |
I follow company coding guidelines focusing on readability, naming and conventionss. |
A function is too long when it does multiple tasks or becomes hard to read and maintain |
I follow Google's code review guidelines to review code quality, readability, and correctness. |
60 |
20 |
20 |
I enjoy solving technical problems and seeing my software work on real systems like vehicles. |
Unclear requirements can be challenging |
TDD means writing test cases before development to guide and verify the code |
I want to learn TDD practices so I can improve how I write tests and build more reliable code |
Show
|
| 1 |
12 |
now C |
I mostly used ST (CODESYS)
I mostly learned C++ in my studies |
none |
I have perfectionistic traits and am worried about taking tdd too seriously, or clashing with others who don't want to use it as much as I would like it to be used. |
directly on the machine |
machine |
MATCH toolchain
VS Code
Github Copilot
Github
Jira
Confluence |
1-5 minutes |
we have one newly. Still finding out how to thoroughly manage to check if we comply with it |
I don't know |
only starting
in github in pull request
two AI agents (still not configured right)
manually |
40 |
30 |
30 |
creating new functionalities
giving "live" to a machine
optimizing systems
being creative |
trying to manually check compliance with coding rules
writing documentation |
write test first
make test fail
write code only to pass the test
clean up code |
become a better software engineer
learn best practices
find out how, when and where to use tdd |
Show
|
| 4 |
9 |
C, C++ |
python, rust(just started) |
vectorcast, internally developed test suites |
I have a dog, Lyla, and a cat, Luna. |
Unit tests, manual tests, automated tests |
ble, arm |
gcc, nvim/vscode, jtag debuggers, simulators |
5-30 minutes |
Divided into three categories, Effective, Stylistic, and Documentation |
when it can be split into multiple pieces for better readability. |
mostly performed per pull request. We have been mobbing pull requests |
10 |
60 |
30 |
It's flexible in terms of solutions and each new feature is like a mini puzzles. |
All the documentation or processes surrounding the code. |
Write the tests first, then write the code for that test. |
I volunteered to take this class to better grasp tdd. |
Show
|
| 7 |
35 |
C |
Python |
Robot Framework |
I like to mountain bike, do DIY projects around the house (ie install ceiling fans, shoot things with my brand new nail gun). Make pizza in our pizza oven. Sun and swim in the backyard. |
Run PC-Lint static analysis. Home grown unit tests that call into each function in a file and test inputs, branches and lines of code. |
Poor use of semaphores, delays, timers all over the place. |
IAR Workbench, STM32Cube, GCC, Saleae logic analyzer, PC-Lint |
11-30 seconds |
x |
Duplication in it. Too many branch paths. Side-effects. |
Performed in GitHub. |
50 |
25 |
25 |
Structured, truely event driven state machine design, readability, modular and it works. |
Hard-coded unit tests. |
Very little |
I was asked to rate it usefullness for our developers. |
Show
|
| 5 |
10 |
C |
JS |
custom Unit Test framework developed in the company.
Automation framework
IAR
|
I have been working on Embedded Software all my career - for a variety of platforms |
Write UT code along with the Feature. Make use Unit Test passes. Then test using breakpoints
Perform Software Validation tests as well as Software Verification Test |
Multi-processor platform using BLE to communicate with other system components. |
VS, IAR, custom Automation tool |
1-5 minutes |
We have a published coding standard for C which developers need to adhere to. |
When it is serving more than one purpose. When it is longer than about 100 lines. |
Code reviews are done via PRs. Also use Mobbing style for code walkthroughs |
60 |
20 |
20 |
The feeling of problem-solving, creativity, translating set of a requirements
|
At times post-development issues are difficult to analyze to establish root cause |
Have had an introduction to TDD basics. have not practiced it extensive.ly |
I would like to avoid coding issues escaping into the field |
Show
|
| 7 |
10 |
C |
Python
Javascript
Go
|
internal
jest |
I love pickleball! |
unit tests after development |
embedded systems (insulin pumps) |
IAR
PC Lint
internal unit test framework |
11-30 seconds |
It's internal but has some influence from Barr Group |
If I scroll the page and notice it does multiple independent tasks that can be encapsulated |
Take too long to get done! A lot of design controls which are needed in the regulated space. |
40 |
20 |
40 |
I love solving puzzles and seeing the outcome |
Long lead times to make minor changes |
I have done some sessions with our manager Phil and have enjoyed it |
To understand the philosophies/workflows better to grow and to create agentic workflows for TDD. |
Show
|
| 14 months |
20 years |
Embedded C |
- python
- java script |
- unity |
i like playing indoor soccer and i try to learn playing the piano from time to time. |
- unit test framework developed by the company
- a simulator developed by the company
- debugging with an emulator if necessary
|
system contains THREE processors. (1) the main ARM processor (2) nRF BLE processor. (3) i don't use. |
- VS code: Source code editor
- IAR: build and link the code
- GIT: source code control
|
5-30 minutes |
The company has a coding standard document that we follow. |
Usually if i see too many if/case statements and/or the func is doing more than one thing. |
We use GitHub and live mobbing for code reviews. |
50% |
25% |
25% |
I like embedded development specifically because it interacts with the hardware directly. |
unexpected failure that may be caused because of untested corner case or unknown behavior. |
writing the test code iteratively with the production code until we can't think of a test to write. |
i find it hard to think about writing the tests first before writing the production code. |
Show
|
| 4 |
4 |
C |
Python |
Custom in-house harness for embedded C |
My background isn't computer science, I studied EE back in undergrad and worked in the industry for it. My current job is my first real exposure to software engineering. |
We unit test our embedded C code on the host using a custom harness with type-specific assertions. Tests run via CMake/CTest with gcov coverage tracking. CI runs everything automatically on every change.
|
We have ARM and NRF processors. |
IAR Embedded Workbench, CMake, GCC, Git, Python scripts, gcov/lcov, Bamboo CI, JTAG debuggers. |
1-5 minutes |
Fixed types, null checks, short functions, no magic numbers, zero warnings, consistent formatting. |
When it's hard to understand, has multiple responsibilities, or becomes difficult to test. |
If a code change is large, we have PR review to go over ti changes. |
10 |
5 |
20 |
Seeing code work properly on the hardware. |
Maintaining legacy code without clear documentation. |
I don't know much except it's a type of development where we write tests first. |
I want to become a better software engineer. |
Show
|
| 1 |
10 |
C |
Python
Java Script |
n/a |
n/a |
Unit tests |
Complex med device multi chip system |
IAR, VS Code |
1-5 minutes |
Common standards, casting is used quite often though |
Depends, sometimes length is ok as long as it is performing a single objective |
Decently well structured usually containing changes to software and unittests |
20 |
40 |
40 |
I enjoy solving problems and finding efficient solutions. |
Random problems such as builds randomly failing due to unrelated issues |
It's a strategy for development by first defining the test cases necessary for successful design. |
I want to improve my abilities as a software developer. |
Show
|
| 6 |
8 |
c |
JavaScript |
Only used in-house tools - behavior driven testing and code coverage |
I started out writing Android applications in college. I worked at a few startups prototyping on development boards and raspberry pis. I enjoy fast (and safe) software development because there are more challenges. |
Unit tests, on target tests, automated tests (via a simulator) |
It's an embedded system that primarily uses two processors. |
VSCode, IAR, Git, GitHub |
31-60 seconds |
Company specifies styling and general guidelines for formatting code. |
It starts to be come a function that has many functions. |
They can take awhile since that's the first time some people see the code |
40 |
30 |
30 |
It is like solving a puzzle where there are dozens of solutions but only a few good ones. |
Sometimes there is too much bureaucracy involved in making a change. |
It's a development strategy where tests are written before code. |
To learn about a different way to write code to increase efficiency. |
Show
|
| 4 |
8 |
c |
Javascript, Python, C++ |
Custom |
Avid bicycler and climber |
Unit tests, automated tests, manual tests, static code analysis |
Embedded device with three independent processors |
VSCode, GCC, IAR |
5-30 minutes |
Mostly stylistic; some constraints for how many actions single functions perform. |
Functions should do a single action; otherwise they are usually overly complex |
Github PR reviews, invite team of 6 devs and 5 testers |
40 |
50 |
10 |
The puzzle and challenge to design a new feature and get it working. |
Nothing about the actual development; around development there is bureaucracy and hierarchy |
Testing, requirements written before development starts to ensure implementation follows design |
Continued education |
Show
|
| 3 |
9 |
C |
Assembly, C++, Python |
cpputest, unity, pytest, custom |
I like rock climbing and electronic music. |
As ASPICE mandates (3 layers) |
It's a Bluetooth SOC. |
cmake, clang goodies, CPU supplier toolchain, IBM DOORS, Azure devops, etc. |
Under 10 seconds |
MISRA 2012 |
When our HIS metrics tell us so |
Formally, there is a checklist. Practically, we use our engineering judgement. |
2 |
7 |
1 |
Doing actual development and solving engineering problems |
Paperwork, wrangling infrastructure, strict processes |
You have unit tests as the first consumer of your code. They sort of work as requirements. |
We are adapting TDD on the company level. Always nice to learn something new. |
Show
|
| 3 |
10 |
C |
Python, basic C++ |
N/A |
I hope this training goes well |
using the bluetooth qualification tests and verifying manually in specific instances |
an embedded firmware system written in C running on target |
visual studio code as an IDE, cmake to build the firmware, ninja as a compiler |
Under 10 seconds |
loose, I am not sure we have a formal document at least that I have seen. But generally consistent |
when a function generally does more than one large task, or can't be described succinctly |
code reviews happen in PRs by the people reviewing the change, rather informally done asynchronously |
50 |
20 |
30 |
I like the "puzzle solving" aspect, as well as knowing that everything happens for a reason |
wasted development and broken code as a result of not understanding the whole complicated system |
I am aware that it is a practice where the test case is written before the code is changed to pass |
Because I was invited mostly. I would like to learn about TDD, but unsure how I will actually use it |
Show
|
| 4 |
12 |
c |
python
java
c++ |
ceedling
unity
pytest |
I don't really know if I want to do TDD. |
depends on the project.
- on target with unity
- off target with ceedling
- system level integration tests |
it varies
- arc core (ASICS and general SoC)
- risc V core (ASICS)
- some assembly (custom ISA) |
ci/cd pipelines
clang format/tidy
code coverage tools
MISRA etc...
requirement management |
31-60 seconds |
allman style. strict naming scheme for everything. enforced automatically somewhat. |
cyclomatic complexity is above threshold. Also gut feeling. |
lacking. It seems we never have enough time for good reviews. |
5 |
3 |
2 |
solving hard problems and making hardware do stuff. |
tedious stuff and busywork sometimes. AI has been helping with this. |
i learned the process in college. haven't applied it in my career at all. tests first... |
we are trying TDD with latest development effort. |
Show
|
| 2 |
20+ |
C |
Objective C |
Unity |
I actually enjoy writing tests! |
Manually
Unity |
ARC MCU |
vscode
clang-format
|
Under 10 seconds |
Company defined |
When it tries to do more than 1 thing |
PRs must have 2 approvals |
20 |
40 |
40 |
Solving puzzles. Learning new stuff. |
Pretty much like it all |
Test Driven Development |
To learn TDD. |
Show
|
| 5 |
35 |
c |
C++, python, ruby, perl |
Internally developed and the Bluetooth qualification test suites |
I like challenging technical problems and enjoy hardware and software development. I'm interested in this topic look forward to learning more about it. I think these courses often add too many exercises mostly to fill the allotted time. |
Unit testing, integration testing, qualification tests, and with an internally development test system. |
Embedded ARC |
VS Code, Metaware development environment, python |
31-60 seconds |
Coding standard is documented and generally followed. |
There are many factors, does more than a primary task, multiple screens of text |
Code reviews are preformed on an informal basis, but are required. |
25 |
40 |
35 |
The creative process, seeing the successful outcome, and challenging problems. |
Testing |
Basics |
I was signed up for this training class. |
Show
|
| 2 |
20 |
C |
C++, Python |
Unity |
Working on different protocols and embedded systems. |
Unit testing, functional testing, manual testing, regression testing |
wireless embedded systems |
VSCode, Linux, IDEs |
11-30 seconds |
Clang and standard agreed with the team |
multiple functionalities happening |
peer reviews and SME approval |
5 |
6 |
8 |
Get to develop and see new features working. |
manual testing of the same features when the testing should have been automated. |
writing test cases first and then developing software against it to pass the tests. |
company organized it |
Show
|
| <1 year |
10 |
C (Embedded) |
Python, C++, Rust, Bash |
CMocka, Twister, Unity, Pytest, and in-house Rust/Bindgen C framework. |
I'm a big sci-fi/fantasy reader, love Sanderson books. Also big into video games and going to concerts! |
Ideally, unit-testing off target HW, if "required", on HW. Integration testing using our QA team's harness, then any BLE SIG tests. I also will do some basic personal smoke testing of my features iteratively. |
ARCv2 ASIC running BLE stack. |
VS Code, GDB, gcc toolchain when building on Linux, Docker, Metaware toolchain when built on target. |
5-30 minutes |
I try to prioritize readability and testability over any arbitrary cleanliness/conciseness. |
If a function can be broken into multiple logical chunks or operate on semi-independent data. |
First, I review over the intent of the change, then I go over other things like readability, tests. |
40% |
30% |
30% |
Just a fun way to solve problems, feels very math-y to me which is a passion of mine. |
Resolving/investigating extremely long linker dependency chains. |
I've learned about it in the past and tried using it on smaller personal projects, not professionall |
Generally our FW team could attain a higher degree of testing discipline. |
Show
|
| 5 |
30 |
C |
Python, C++ |
Unity, Google Test |
I'm a beginner photographer, mostly landscapes. And I have an interest in learning the Rust programming language. |
Bluetooth Protocol-level test suites |
System-On-Chip with Bluetooth stack |
CMake, cross-compilers, debugger, protocol analyzers, conformance testers |
11-30 seconds |
C99 compliant with an increasing interest in Automotive Quality initiatives (MISRA, code coverage) |
No company mandated directive here, however, it should perform a narrowly-defined single output |
Reviews performed thru Azure DevOps with two reviewers required to push a PR. |
20 |
50 |
30 |
Solving problems and delivering robust solutions for our customers |
Ambiguous requirements and unrealistic expectations |
A little exposure in regard to writing negative UT followed by positive UT and, finally, code. |
Training was recommended by the Swiss team and a desire to improve product quality |
Show
|
| 0.125 |
6 |
C |
Java, C++, Python, R |
n/a |
I am an intern, currently attending UT-Austin CS. |
Test cases |
EM made SoC |
VS Code, WSL2, Confluence |
1-5 minutes |
Consistent variable names, enough comments modular code. |
More than 30 lines around. |
n/a |
8 |
8 |
10 |
I like implementing different features given constraints and considering tradeoffs |
Build times and having to wait between testing. |
n/a |
Required by company. |
Show
|
| 3.5 |
40 |
C++ |
ASM, C, LUA |
GTest
Many Proprietary |
I have worked in games and defense - simulation for 30+ years. |
Combination of unit and functional tests |
Game Engine |
Visual Studio
VS Code
Visual Assist
Perforce
Proprietary |
11-30 seconds |
Not sure what you want to know? |
When I have to scroll back up to the top of the function |
We have them for every checking from a selection of SME's team members |
60 |
30 |
10 |
Solving problems |
typing |
I have developed TDD culture within new software teams in the past due to project SDLC requirements. |
To see if this kind of training is useful for my teams |
Show
|
| 0 |
30+ |
C/C++ |
HLSL, C#, Python, assembly |
Some, I forget the names. |
I seem to believe in (and have had great success doing) a rather different version of agile development to most people. |
Ah-hoc playthroughs. |
PC games, typically low-end machines e.g. older laptops. |
VisualStudio + in-house tools. |
11-30 seconds |
Thorough - half of C++ is disallowed, strong typing heavily encouraged. |
No such thing. |
2-4 people review with discussions. |
30 |
30 |
40 |
Shipping to people. |
Not much. |
Quite a bit. I have seen it taken way too far. |
Because I was asked to. |
Show
|
| 15 |
28 |
JS |
Python
c++
Actionscript
java
Various embedded |
FlexUnit
JUNIT
Mocha
Puppeteer
Cypress |
I run/design/play tabletops and LARPs |
Mostly manual with occasional integration/unit testing |
Internal Engine Tooling |
VS, VSCode, Intellij |
Under 10 seconds |
Strict coding standard defined by riot. Otherwise community standards for the language. |
Preferred is 20 lines max, 1 screen as an extreme. Anything over is too long |
Custom tool for code reviewws |
2 |
3 |
5 |
Discovery and deep learning |
Inconsistent standards |
Used to teach Flexunit testing with a focus on TDD. Helped write flexunit 4. |
Understand c++ testing space better |
Show
|
| 7 |
20+ |
C++ |
Python
former fullstack .net |
GTest
Pytest
xunit
mspec
specflow |
I'm looking forward to this class |
n/a |
PC |
Jetbrains
Visual Studio |
1-5 minutes |
internal standard that documented and shared |
the length of it. Should be ~30 lines or less |
All check ins require a code review |
6 |
1 |
3 |
Writing code |
stepping through code to troubleshoot |
Read several books |
I put it all together and I'm a big believer. |
Show
|
| 16 |
24 |
C++ |
C, Python, Lua, ASM, JS |
Homespun |
I've never made anything but games since the Playstation 2 era. |
Mix of manual and unit tests |
PC |
Visual Studio |
11-30 seconds |
We have a strong coding standard focused on consistency and readibility. |
When it does 2 or more unrelated tasks, or requires a sitemap to keep track of. |
Mostly used to spot architectural inconsistencies and standards deviations. |
60 |
10 |
30 |
Helping artists and designers make cool shit. I like building things in general (physical as well) |
Nothing glaring stands out in particular. |
High level concepts, but I've been in Old School games too long to have much experience with it. |
Boss thinks it's a good idea. (I don't particularly disagree, but I wouldn't have prioritized it). |
Show
|
| 5 |
30 |
C/C++ |
Python, Rust, Javascript |
Google test, built in rust test harness, some python ones I don't remember |
I do HDL verilog development as a side project which in professional settings is heavy focused on TDD. |
Usually running in a debugger. |
Windows and Mac PCs |
Visual studio, neovim, vscode, xcode. |
1-5 minutes |
I pay attention to the parts that focus on safety, clarity and debuggability. |
Length doesn't matter, complexity is what is important. |
When reviewing I focus on potential issues/bugs and maintainability. |
20 |
30 |
50 |
Challenging, problem solving. |
Not making progress. Boilerplate. |
I hear a lot of zealotry, but have little real world experience with it. |
A bunch of engineers from a central team that I depend on are doing it so I wanted the context. |
Show
|
| 4 |
12 |
C++ |
Python, C#, TypeScript |
GoogleTest, PyTest, JUnit |
I'm a big fan of ducks and can make a decent quacking sound |
Primarily manually with some unit tests |
Cross-platform for Windows and macOS |
Visual Studio |
11-30 seconds |
Standard heavily opinionated C++ |
Too many responsibilities or raw lines of code |
Often asynchronous, sometimes used for spotting bugs as opposed to purely for alignment/sharing |
5 |
2 |
3 |
Instant feedback, much lower risk of breaking something physical or expensive while iterating |
Setting up a new dev environment and forgetting all your macros, keybinds, etc. |
Red, Green, Refactor |
Want to learn how to adapt a legacy codebase to make software dev easier, too many regressions now |
Show
|
| 8 |
35 |
C++ |
C#, python |
tcl/tk, gtest, many custom ones |
I lived on a sailboat for half of my childhood. |
gtest |
windows/linux/osx/ios/android |
Visual Studio |
11-30 seconds |
It is quite extensive, but does allow for exceptions where pragmatic. We automate many checks. |
When it's not easy to understand. |
Every change is reviewed, but not blocking. |
7 |
1 |
2 |
Understanding a system and creating it, adding to it, fixing it, making it faster, or deleting it. |
Hype cycles. |
It should be capitalized :)
I did a course on it a long time ago, but have not used it much. |
My manager suggested it, and I haven't done a course for a while, so why not? |
Show
|
| 12 |
40 |
C++ |
For work, SQL |
Nothing extensively |
|
Initially, personally against requirements. Then some basic CID tests, then via games played on internal regions, then more extensively via Public Beta games. |
All flavours of PC/Mac and mobile. |
Visual Studio |
31-60 seconds |
Extensively documented and mandatory. |
If its a page long, its probably getting too long. Depends on functionality. |
1 - 4 reviewers required per change. Reviews via Swarm |
50 |
10 |
40 |
Getting code working |
Code not working due to opaque infrastructure bugs |
Just that its test driven development. |
Because I was enrolled in it. |
Show
|
| 12 |
40 |
C++ |
Pretty much anything but I have a soft spot for Perl |
gtest but there was probably some Java ones I forget about |
I have a rabiit |
Unit tests, functional tests, manual QA |
Desktop and mobile devices |
Visual Studio
Qt Creator
Emacs
Renderdoc |
Under 10 seconds |
Well documented on the internal wiki |
when it does more than you can describe in one sentence |
Perforce Swarm |
5 |
1 |
4 |
Solving problems - every new task is a puzzle that needs to be solved with efficiency and elegance |
Short term thinking, fragility, and recently the "AI" push |
Tests first - they are expected to fail, and then write the implementation until the tests pass |
My manager signed me up |
Show
|
| 3 |
14 |
C++ |
Python
C# |
We have a CID system that runs some basic tests |
I like the P-38 on your Logo, just made it out to Oshkosh airshow last year for the first time. Used to fix avionics on the A-10, and would love to get my pilot license some day. |
Run through a series of test in editor and game to confirm expected behavior, and identify any edge cases |
We develop for PC, Mac, Android, and IOS, but primarily target PCs. The codebase is > 18 years old |
Visual Studio, RenderDoc, Sublime Text, |
1-5 minutes |
We've got a pretty lengthy doc covering everything from syntax to use cases |
Gut instinct, or when it gets frustrating to work on |
We use Swarm, and Peer review our code, requiring at least one SME sign off |
3 |
1 |
6 |
Solving problems and exposing new functionality for artists and designers. |
Managing constantly shifting priorities while trying to debug a bunch of loosely documented code |
You design a test for the thing you want to accomplish, write code to pass the tests, repeat |
Our manager scheduled it labeled as Unit testing. I'm interested in how to better test our code. |
Show
|
| 3 |
8 |
C++ |
Python
C# |
Catch2
Google Test
pytest |
I like playing League of Legends. |
Scenario testing with scripted events, verfying certain outcomes.
Automated testing with mouse / keyboard interactions. |
We test video game functionality and windows programs. |
Visual Studio |
5-30 minutes |
We have a shared standard for C++. For smaller utils there isn't a qualified standard. |
It's usually done via best judgement. |
We have SMEs look at code as well as TLs. We have a system for people to become reviewers. |
60 |
15 |
25 |
Empowering users with the tools they need to improve the content within our game. |
The finnicky moment of turning an idea you know should work into paper. Reproducing complex bugs. |
Writing the failing test first and then writing code. |
A requirement from my initiative. I'm looking for ways to apply methodologies in hard to test areas. |
Show
|
| 2 |
12 |
C |
Python |
CppuTest |
Got into embedded software developemtn when doing my bachelor studies; fell in love with it and been doing that ever since. I like when things interact with real world and you can see the outcome.
Love to read books |
Static analysis, system test, integration test |
Low power MCU, modem, RF chip |
Cmake, gcc compiler, vs code, st-link, cubemx programmer |
1-5 minutes |
I mostly follow coding standard released by Michael Barr, Embeded C coding standard |
It is longer than 100 lines |
It is mostly to check if changes are made in line with acceptance criteria |
30 |
20 |
50 |
Solving problems and seeing their solutions in real world environment |
Probably mostly the documentation part |
I'd say pretty much nothing, bare minimum |
I believe TDD is the future where most of the code will be generated by AI |
Show
|
| NA |
12 |
C/C++ |
Python, Ruby, Javascript |
Unity, CppUTest |
I'm an electronics engineer and a musician, interested in embedded systems and real-time applications. |
Running it on the target machine and exercising it manually or hard coding stuff to test corner cases.
I've written some developer tests using CppUTest and Ceedling on different projects, but they are very immature and there are too few of them. |
Main project is 32-bit arm embedded linux device and there is a side project based on a dsPIC device |
CMake, GCC, XC-DSC, VSCode |
1-5 minutes |
Undefined |
When it does more than its name says. |
Just quick looks at PRs. |
30 |
35 |
35 |
The satisfaction of seeing that I can tell a computer with some precision what to do. |
It's difficult to find a job in an area you really love. |
It's a practice for building software incrementally guided by tests. |
Personal interest. |
Show
|
| 1 |
17 |
Python |
C, C++ |
CxxTest |
I’ve been programming for a long time, but never specialized in one language. I’d love to focus more on writing clean, functional code and planning for potential issues before coding. |
Using test suites with CxxTest |
I don't understand the question |
Microsoft Visual Studio Code
Microsoft Visual Studio |
1-2 hours |
MISRA C++ with IEC 61508 SIL2/4 safety standards |
"Intuition" (no more than 50-80 lines) |
Tools: QAC++ static analysis, CxxTest framework, Make build system, integrated regression testing |
60 |
10 |
30 |
I love the feeling of building something from scratch and seeing it come to life |
Spending hours debugging just to find the error was a tiny typo—so frustrating! |
Nothing… my mind is a blank canvas ready to learn! |
I’d like to be more efficient and have a more preventive attitude rather than a corrective one |
Show
|
| 4 months |
3 years |
C++ |
C, Python |
I use CxxTest with custom stubs for unit testing in embedded C++ projects. |
I work on embedded C/C++ development for safety-critical railway systems.I enjoy learning new practices to improve reliability. |
I run automated unit tests using CxxTest and stubs. |
We develop the ERTMS on-board system for railway applications. |
I use Visual Studio Code and Visual Studio 2022. |
1-5 minutes |
We follow MISRA C/C++ guidelines and internal rules and use tools like QAC++ to enforce compliance. |
If QAC reports an error (e.g., excessive length or complexity), the function is considered too long. |
We make peer reviews for every change |
50 |
30 |
20 |
I enjoy solving complex problems, creating reliable solutions, and seeing code work in real systems. |
I don't like managing complex dependencies and debugging issues or waiting for long build times. |
I know TDD means writing tests before code, ensuring requirements are met and reducing defects early |
My company proposed this training to improve testing practices and adopt TDD for our system. |
Show
|
| 2 |
26 |
C/C++ |
C#, python |
cUnity, cpputest, gtest, cxxtest |
I've been working for 20 years with embedded systems in risk-oriented developments. Unit Testing was a game changer for me. I do not fully agree with everything TDD proposes, but I successfully integrated several approaches into my development cycle. |
First unit testing, then integration tests (automatic when possible), and finally manual system level partial testing (full system level verification and validation is done by other departments). |
Usually embedded systems (RTOS or linux), but sometimes PC |
Visual Code, makefile, cmake, propietary compilers, git, QAC static analyser |
1-5 minutes |
Primarily MISRA-C/C++, plus in-house rules for defensive programming |
It does too many things or you have to scroll to see all of it |
Our processes include peer reviews before the feature branch is merged. |
30 |
30 |
40 |
it is fun!! |
When you spend days and days looking for a bug you could have avoided |
I've read a few books, including "Test-Driven Development for Embedded C"
|
I am not fully convinced with the TDD approach. Looking for more in deep learning. |
Show
|
| 1 |
8 |
C |
C++ |
CxxTest |
|
Using unit test and developer tests. |
|
Programming using Visual studio code and compiling debug code with MSVC/MSVC++ |
31-60 seconds |
|
We have a QAC program that sets a limit on the maximum number of lines that a function may have. |
|
5 |
2 |
3 |
|
|
I took a course on TDD at university. |
I feel that I can improve my testing skills |
Show
|
| 20 |
27 |
C++ |
C, python |
boost.test, catch, catch2, xUnit, pytest, gtest/gmock |
I work remote, somewhere in the middle of the Atlantic. |
- Primarily unit tests (in gtest)
- Secondary: system tests using a python based framework (built on top of pytest).
- Manual tests on running system |
Distributed embedded system (but no real limitations to memory allocation or exceptions). |
IDE (Clion+IDE), sourcetrail, main project toolchain (debian12 gcc).
Codescene, Coverity, copilot |
1-5 minutes |
C++17 |
Starts to feel too complex (over a screen, too many control-flow branches). Codescene also warns. |
Our agile team is heavily invested in code reviews. |
60% |
30% |
10% |
Allows me to express my creativity, feels like LEGO for adults (it we get the modularity right). |
Lagging tools (C++ was stale for too long), debugging, memory corruption ... |
I have been using it for over 15 years, also am aware of ATDD (not using it now) |
Got asked by management, personally hoping to learn (or refresh) my knowledge as well. |
Show
|
| 11 |
25 |
c++ |
c, python, shell script |
google test |
I'm looking forward to this training. But I'm not much of a morning person, please bear with me :) |
unit test, integration tests, system tests |
Card Application SW running on zync ultrascale arm cortex core processor |
bitbucket, eclipse, ms code, various plugins |
1-5 minutes |
company specific |
does too many things |
in bitbucket. Required review and approval for all PRs |
30 |
40 |
30 |
The challenge and collaboration involved |
too many bugs |
Not much |
Company enrolled me but I am looking forward to learning something new |
Show
|
| 9 |
20 |
C/C++ |
Python, Java |
Google Test |
Married, two kids. Recently started to run. Benfica supporter. |
Management Framework Integration Tests (MFIT), python scripting end2end tests.
Unit Tests (Gtest) |
Debian OS for Telecommunications |
VSCode, with some extensions |
1-5 minutes |
Format is enforced by AStyle.
Should have comments, Doxygen compatible.
Code coverage test 75% |
It is bigger than my editor in VS code :) |
At least one reviewers must approve before delivery, and none can disapprove. |
20 |
60 |
20 |
See the things I created come to life. |
When it starts to be mechanical work. No thinking. |
Test Driven Development, is when you write the tests from the requirements prior to the code. |
Check if I can get some tools to (change/bring some insight) to my team. |
Show
|
| 6 |
20+ |
C |
Python |
CppUTest |
I dislike answering survey questions. |
Unit tests and manual testing. |
A55 and Nordic processors running Zephyr. |
VS Code, gcc, git. |
11-30 seconds |
https://barrgroup.com/embedded-c-coding-standard with some modifications. |
If the function name can't capture all of what the function does, the function is probably too long. |
All pull requests are reviewed by another person to check basic functionality and completion of DoD. |
60% |
20% |
20% |
Solving problems. Writing code that is clear, easy to use, and easy to change. |
Shifting priorities caused by poor planning or lack of focus/commitment from the business. |
I familiar with the TDD process and have applied it to simple examples. |
I want to learn how to write good unit tests and see if TDD will work for me. |
Show
|
| 1 |
15 |
C |
C++, C#, Python, Javascript |
AceUnit, CppUTest, Zephyr's ZTest |
I like hiking outdoors. |
TDD |
Battery-powered, embedded ARM A-core device |
VSCode and open-source compilers |
Under 10 seconds |
Pulled from some standard somewhere. Seems pretty typical. |
When I can't see everything it is doing in one screen. |
Quick checks of functionality and making sure the objectives of the task/story were accomplished. |
40 |
40 |
20 |
It is fun to see the realization of objectives come into being. |
Nonsensical directives being forced on a design, without justification. |
I've taken this course before, about 7 years ago with a different employer. I've practiced it since. |
Refreshing TDD. Hoping to get co-workers on-board with it too. |
Show
|
| <1 |
9 |
C |
Java
C++
C#
Python
VHDL |
None |
I come from the defense side of embedded systems, so I've had a lot of experience with waterfall development. I am overwhelmed by the speed and complexity of the private sector, but am excited to become better under the pressure. |
Build it and run it. |
nRF54 and nRF52 devices and iMX93 devices. |
vsCode
Zephyr
West
|
11-30 seconds |
We have a coding standard that we follow pretty well |
Typically if a function goes longer than a page, I take a second look to see if it can be "helpered" |
We have a pull-request system and reviews must be done. |
3 |
2 |
5 |
Making things work and building cool embedded projects. |
Build issues. Getting stuck debugging when no solution can be found. |
I understand its power and utility. I've heard it talked about. I have never seen it executed. |
My team is doing the class together to hopefully start doing TDD for all of our projects. |
Show
|
| 4 |
7 |
C |
Python
JavaScript
C#
CMake and Linux scripts (if they count) |
A little bit of CPPU Test |
I'm always happy to learn new ways to improve my processes and write better code |
Using prints and testing behavior |
Embedded system running Zephyr |
VScode
JLink
StateSmith |
Under 10 seconds |
Largely based on https://barrgroup.com/embedded-systems/books/embedded-c-coding-standard1 |
I don't like when a function gets longer than the vertical space on my screen with some exceptions. |
All code is reviewed before merging to master. Code is reviewed and tested |
50% |
25% |
25% |
I like seeing things come together and work. Writing code I'm proud of is also a big plus |
Trying to get 3rd party things working and fighting with their documentation or code. |
I understand the idea of building and testing smaller chunks of code incrementally |
I think TDD will be useful. Slowing down progress at work to learn it hasn't felt feasible until now |
Show
|
| 3.5 |
8 |
c |
python |
cpputest |
I am a hard worker. I would love like to take up more challenges at work. |
using shell on zephyr |
imx93 platform running Zephyr RTOS |
VSCode, GIT and bitbucket |
11-30 seconds |
C11 |
When no. of lines are more than 100 |
Average 50 hours we spend for every sprint of 2 weeks length. |
10 |
5 |
5 |
The joy of solving problems using coding. |
Testing |
I believe development and testing goes hand in hand. |
catch the bugs earlier so that our customers will be satisfied about our product quality. |
Show
|
| 3.5 |
15 |
C |
C#, python |
cpputest, nunit |
I care a great deal about the quality of my work. |
manually |
ARM Cortex-A55 running Zephyr RTOS, and an ARM Cortex-M device (BLE radio) also running Zephyr. |
VSCode, gcc, git/bitbucket |
11-30 seconds |
Based on Barr Group's Embedded C Coding Standard, with a few modifications. |
Coding standard says "maximum of 100 lines" with exceptions. |
Code reviews are done manually for every pull request. |
25 |
50 |
25 |
Problem solving is deeply fulfilling. Continuous learning. Pay. |
Code reviews, waiting for builds, vague/misleading build errors. |
I've taken your in-person class before (about 8-9 years ago) when I was at Cirque Corporation. |
Someone mandated that we all use TDD, but they don't want to teach it. |
Show
|
| 3 years |
20 |
Java |
C,C++ Python. |
JUnit |
Despite my role as Sr SW PO,I continue to try involving myself in development. With the training it is an opportunity to change our work of developing by adopting TDD |
Iam not doing currently heavy programming. But I did test using automated unit tests with JUnit |
TDD as mindset to develop embedded app. |
Visual Code,
Unity... |
1-5 minutes |
we defined internally coding standard that every developer should follow.. automatic checks. |
function that is doing more than what is expected. |
using primarily Pull request. |
XX |
XX |
XX |
Use of design Pattern to model a use case. |
Lack of flexibility. Lack of separation of concerns. |
Using it during my previous projects.This is the reason of introducing it in our development |
TDD for embedded system. |
Show
|
| 1.5 |
9 |
C |
C++
C#
Python |
Specflow
RobotFramework
GTest |
Got into programming due to robotics. Making something in the real world move was incredible, led to embedded systems, LEDs are almost as good :) |
Blackbox System Level Test |
Multiple Cortex-MX devices |
VS Code + extensions
Salea |
31-60 seconds |
Try to adhere to Google C++ Style Guide, but as far as standard I would call it.... loose. |
It depends on the context but generally for me its when there are too many exit points. |
I am the only Embedded Developer on my team currently. I need better tools for test/etc |
50 |
10 |
40 |
Solving puzzles and interacting with the real world. |
Unclear legacy code, Bad Debug tools, Environment setup/issues
Really debugging unexpected issues |
A little. Write tests before starting, develop, pass tests.
1st module of self-paced |
To make my own coding more reliable and have something to hold up for checking my own work |
Show
|
| 3 |
30 |
BASIC |
C, C++, Python, Java, Javascript, GDScript |
VectorCast, Unity |
Used to work in SW dev in aeronautic and space fields of application with highly constrained standards. |
Printf statement to follow-up code execution, toggling GPIOs when performances are requested.
Used VectorCast for unit and integration testing (long time ago). |
ARC CPU with few KBytes of memory. |
Synopsys ARC toolchain and debugger.
Git for source code management.
Digilent Digital Discovery |
11-30 seconds |
MISRA C 2012 along with custom internal coding rules. |
Cyclomatic complexity, and personal feeling. |
Pull requests done when a branch has to be merged within the develop main branch. |
30 |
30 |
40 |
Innovative tasks, algorithm elaboration.
|
Experiencing non deterministic bug that arise very seldom after quite a very long time to reproduce. |
Almost nothing. |
To foresee how TDD can help reducing test and debug time, or if we can be more efficient. |
Show
|
| 3 |
10 |
C |
Python, C++ |
VectorCast, Unity, Ceedling |
I like playing tennis and mountain biking |
We can execute unit tests on the target or without the target.
|
Bluetooth SOC using ARC CPU and our custom IPs.
We write all the drivers and integrate a BLE stack. |
Metaware compiler/debuguer with Visual Studio Code |
30-60 minutes |
A coding standard is defined for all the developers in our team |
No detection for that in our development environment |
Using Azure Devops pull request to make the code review |
40 |
40 |
20 |
Designing, Coding and Testing software are interesting part in software development |
Making the documentation for a user level and managing requirement could be difficult to handled. |
Not so much, I guess it is a methodology to develop software by defining test first. |
To learn methodology to improve the development of software |
Show
|
| 3 |
30 |
C |
Objective-C, C, C++, C# |
Ceedling, CMock |
I like traveling and discovering the world. |
Unit Tests, we are able to run them on the target or without the target.
Regression (Integration) tests.
We write python tests which send HCI commands over SPI to the target. |
Bluetooth SOC using ARC CPU and our custom IPs.
We write all the drivers and integrate a BLE stack. |
Metaware compiler/debuguer with Visual Studio Code. |
31-60 seconds |
We have our custom rules that each developer shall use. |
We use LDRA, but in general it's up to the developer to try to write not complex functions. |
We use Azure DevOps and git for pull requests. |
30 |
50 |
20 |
Writing clean code, easy to understand and working well without any major trouble to make it working |
Using debuguer to understand the issue. |
We already use TDD but we want to be sure that we use it correctly. |
Increase my knowledges and use TDD correctly. |
Show
|
| 2 |
18 |
C |
Assembly, Python |
Unity |
I like assembly :-) |
Unity test on target.
We are slowly shifting to the Ceedling framework to run unit tests on PC. |
RISC microcontroller. ARC EM7D CPU. |
CMake, Synopsys ARC toolchain, VS code. |
5-30 minutes |
Not sure to understand this one. |
>80 lines |
Pull request reviews within Azure Dev Ops.
At least 2 approvals, resolve comments, test passing. |
45 |
10 |
45 |
Deliver robust and reliable software.
Enable the client to make great products. |
Dependencies between software modules. |
I read the bee book :-) |
I asked for it. I want our software to be better tested. |
Show
|
| 8 |
20 |
C |
Python, C++, C# |
Google Test and Unity (Throw the Switch) |
I'm not coding on a daily basis... mostly doing proof of concept. Some given answers might not reflect the team |
Unit Test (unity), integration tests (Python), code coverage currently performed on FPGA with LDRA, moving to GCOV and CMock. |
Embedded system based on ARC CPU for Bluetooth LE SoC. |
Metaware C Compiler/Debugger.
Python |
31-60 seconds |
Misra |
Cannot be read on a single screen (in landscape mode!) |
Done via Azure DevOps during Pull Request integration. |
30 |
40 |
30 |
It's creative! |
bad architecture might have a cost during the development or in project (e.g., limited reusability) |
Write test first! |
Proposal from a team mate. This seems fantastic to strengthen our team for better code quality. |
Show
|
| 5 |
6 |
C |
Python |
None- brand new to unit testing |
I have a computer engineering degree. Then, I moved into analog EE world. Now, I’m a mix between the two. |
C: flash it onto an MCU , step thru with debugger until something goes wrong. In RTOS, hopefully with logging messages |
CC2340, MSP430, python is for automating my lab |
Visual studio + copilot
CCstudio |
11-30 seconds |
Unsure what this means, so I don’t have one |
Never considered this before; perhaps when too long to understand |
None, solo |
40 |
10 |
50 |
Pays the bills ;) , plus automating my lab makes life easier |
In an RTOS environment, I struggle to debug where specifically a race condition / fatal error begins |
Zero- we talked briefly about the idea of testing in chunks as you code |
Met you in a bar, I am very curious. I am young and new, and hoping to launch my first product |
Show
|
| 2 |
15 |
C |
C++, C#, Rust |
gtest |
Been coding for a long time in C, but only done TDD (self imposed) once. Keen to do it more often |
function and some gtest |
Embedded STM32's, esp's and nordic series of ICs. Bare metal, idf or Zephyr RTOS |
Jlink ultra, salea, scope, multimeter, SCA tools, lizard cognitive load |
11-30 seconds |
c11, MISRA |
lizard/sonarqube cognitive load review |
Mob review, AI supported and PR with context |
50 |
40 |
10 |
problem solving and new stuff |
difficult bugs and customers |
learning more about testing and changing my coding style |
Keen to try and change the way I code to enable TDD and general unit testing. |
Show
|
| 1 |
5 |
python |
r, julia, c++ |
unittest, pytest, nose2 |
not much to say, i just gym, surf and do exercise besides work, i do alot of research into ml as its my academic focus |
mainly ml code, so includes validating data pipelines, model performance, and reproducibility using the unit tests, integration tests, and metric based evaluations |
microcontrollers, embedded devices, edge ai accelerators and npus |
pytorch / tensorflow, huggingface, scikit, xgboost, mlflow, onnx, nvidia |
1-5 minutes |
clean, modular, pep-8 compliant, type hint, config driven designs, and seperation of concerns |
too long when it tries to do more than one logical task, over 40-50 lines approx |
focus on code clarity, reproducibility, data handling, evaluation logic. mix of software and ml |
50 |
30 |
20 |
the freedom, and creativity you can explore with code, ml a mix of machine learning and standrd code |
sitting on my chair too long, back posture issues mainly |
test driven development is where you write tests before writing the actual code |
want to expand c++ testing as i dont do any, just python |
Show
|
| 2 |
10 |
C++ |
Python, MATLAB, C |
None |
I like robots |
Manual, SITL, HITL |
Embedded linux or embedded |
VSCode |
5-30 minutes |
We have a coding style guide for C++ |
It becomes too confusing to interact with |
We have peer reviews by a senior person |
40 |
40 |
20 |
Iteration and problem solving |
Can be a bit tedious at times |
The tests come first before the development |
Was offered by company and sounded interesting |
Show
|
| 1 |
14 |
C++, Java |
C#, Python |
GTest, JUnit |
My favorite color is blue. I like space exploration. I'm introverted. I wish I did more AI projects like reinforcement learning. |
Manually... I wish we had a pipeline |
X86 laptop, or x86 NUC on a UxV |
Clion, VSCode |
1-5 minutes |
Clean code, very close to Google style guide |
Has more than one responsibility, or does not fix 1-2 screen worth of space. |
1 in process review at 50% completion, 1 at pull request with run testing |
50 |
30 |
20 |
Complex problems, lot of different solutions, making intelligent and automated things. |
Management over-promising then pushing us to the brink, not consulting us on time needed to deliver. |
A lot, worked at EPAM, tried it at workshops. |
I want to make a pipeline with tests at work, but the legacy project is huge and need best practices |
Show
|
| 0.66 |
3 |
C++ |
C#, Qml |
None |
I enjoy philosophy. |
Manual |
Platform? Windows/GNU+Linux |
IDE, clang-tidy |
Under 10 seconds |
No formal standard. Whatever looks robust, clean, elegant, with sufficient compromise to the ideal. |
Doing too many things at once. |
Good. Learning a lot from them. |
5 |
2 |
3 |
Art form of making things beautiful, elegant, robust, and clean. Seeing the fruits of your labor. |
The occasional bureaucracy. I enjoy being solo, breaking things to find the best way. |
Very little. Think of what the output should be, write the tests, then the function. |
Team lead/manager signed many of us up. |
Show
|
| 1 month |
roughly 20 |
C# |
C++, Javascript, Java |
NUnit |
I prefer design and collaboration to coding. |
I haven't really done much development work at my new company yet, so I'm not sure... |
Software running on a laptop, sometimes in areas where internet is spotty or non existent |
CLion |
11-30 seconds |
I haven't had much time to familiarise myself with it much yet |
Rule of thumb - if I have to scroll, it's too long. If it does more than one thing, it's too long. |
At least two people must review the code. The reviewer should test the code to ensure it works. |
40 |
40 |
20 |
The planning and problem solving. Finding an elegant solution to a problem. |
The grind - looking for hours to try to find a problem in code that is needlessly complicated. |
No code written without a test for it. So far love the theory never been able to achieve practically |
I like learning new stuff, and I was asked to. |
Show
|
| 0.24 |
20+ |
C++ |
C, Python regularly
Go occasionally |
CppUnit, GTest, Catch2, doctest, but not extensively or any of them. |
Most of my career has been in small companies and I'm usually drawn into leadership/manager roles. |
Occasional unit tests. By running the code. |
Mostly STM32 based boards. PX4 Autopilot. |
VSCode, Emacs occasionally. GDB, some of the simple SWD probes, STLink. |
11-30 seconds |
Still under development for the company, follow conventions/standards in frameworks we use. |
Personal preference. |
A team member or lead reviews a pull request. Not done as a group. |
80% |
5% |
15% |
It's the power to make machines do amazing things
It's satisfying to create solutions to problems |
Deadline pressure, poor documentation, and people who don't care. |
A read James' book many years ago. |
I want to have confidence that what I am creating will work. |
Show
|
| 2 |
5 |
At work C |
At home python and circuitpython |
CPP U-Test |
Love doing robotics |
I run it on the hardware and test for functionality |
Mostly STM32 |
Mostly STM32 |
Under 10 seconds |
None |
? |
Done more senior coders |
30% |
20% |
50% |
NA |
STM IDE bugs |
I took your class last year |
My boss signed me up |
Show
|
| 5 |
8 |
C and C++ |
Python, Visual Basic, PLCs(Siemens, GE, etc.), HTML/CSS/Java, C# |
Only self constructed so far with unity, started using c unit testing framework based on this class |
I have way to many hobbies and am constantly shifting gears. Right now I'm writing a Lovecraftian horror novel using Scrivener for my character write ups. |
Mostly through firmware level verifications with hardware to sus out edge cases. Core functions are identified and individual development tests laid out. This often happens after much of the code is written though. |
Low level firmware in microcontrollers (AVR,ARM, PIC), but also GUI dev, webservers, embedded |
STM32 IDE, Microchip Studio, Visual Studio, Espressif IDE, Arduino IDE, MPLabs |
5-30 minutes |
None for formatting, but we follow an Azure DevOps layout using GIT |
When it doesn't compile in my 2KB Atmel chip |
Code reviews are organic and change from project to project based on available senior developers |
50 |
10 |
40 |
Every puzzle is unique, but they get easier and more complex solutions present themselves over time |
Getting stuck in a bubble alone while the team is testing |
I know our Embedded/software personnel are adopting it based on wingman training |
I am an electrical engineer with a hodge podge of code background. I want to become professional |
Show
|
| 0.5 |
15 |
Python |
C#, C++, Rust, Java, Fortran |
Rust test, pytest |
- |
A mix of unit tests and manual testing |
- |
VSCode, Visual Studio |
11-30 seconds |
- |
- |
- |
4 |
2 |
4 |
- |
- |
- |
- |
Show
|
| 1 |
4 |
Python |
JavaScript, C, Java, C++ |
Pytest, Unity (C) |
I just graduated from university |
Writing unit tests, integration tests and end-to-end tests |
N/A |
VSCode |
11-30 seconds |
Good naming conventions, modular programming |
When it becomes too difficult to understand/maintain/debug |
Talking through with another developer |
7 |
1 |
2 |
Seeing the good flow/structure/design in action. I like object-oriented programming. |
Errors |
Writing tests as a means to develop code. If the test fails, the code is wrong. |
I want to learn more about C++ as I am a young developer looking to broaden my skillset |
Show
|
| 1 |
20+ |
C |
Python
Go
C++
Octave/Matlab
|
Catch
CppUTest
Unity
GoogleTest |
I have an above-average number of legs for a living human. |
Off-target unit-testing, on-target HIL tests. |
Distributed system with internal interfaces (UART), external Debug CLI. hard realtime. |
IDE
Code coverage
Lint
|
30-60 minutes |
Non-existent. I'm trying to show best practice. |
It doesn't fit in my head. |
Ad-hoc and retrospective. |
40 |
10 |
50 |
Interacting with the physical world |
Poorly scoped definition of done. |
I've been practicing it for many years. I have a copy of your book that I evangelize about. |
I want to know what the baseline level of competence is in my team. |
Show
|
| 4 |
8 |
Rust |
C++, C, Python |
Rust std, Catch, GoogleTest, nose, pytest |
I have made a handy tool in Rust for building test spies from injected traits! Check it out on crates.io - autospy |
unit tests, integration tests, e2e tests, performance tests |
N/A |
Git, Jenkins, just, GitHub Actions |
Under 10 seconds |
Company quality standard, TDD, pair programming, trunk based development, CI |
When the name is vague, or it does more things than is easily conveyed by the function name |
We do not often have code reviews, we use pair programming |
20 |
60 |
20 |
Solving problems, making code neat, following best practice, learning new techniques |
Nothing off the top of my head! I don't like writing bad code, or not knowing what best practice is |
A fair bit, we use it extensively at PA, I often find the hardest part of TDD is the first test |
I want to be better at knowing that first test |
Show
|
| 0 |
40+ |
C/C++ |
Python F# Forth |
CUnit |
First PL was Fortran, most used C, best F#. |
Unit, integration & end-to-end tests, CI & manual |
Various embedded systems |
Various: VSCode, functional safety compilers, CI |
11-30 seconds |
In-house |
1. when the name no longer describes the behaviour, 2. when the code isn't readily intelligible |
Scrum |
25 |
10 |
25 |
Puzzle solving, learning |
Poor tooling, cargo culting, fanboyism, unrealistic deadlines, ship it anyway, obsession |
Very little |
Find out if it's worth anything - TD development OK, TD design ehhhh. |
Show
|
| 1 |
12 |
C |
C++
C#
Python |
GTest
Specflow
Robot Framework |
My first foray into programming was FIRST robotics where I learned about PWM controls and simple code. Fell in love with code that moves the world. Avid gamer, New 40k player, and read more fiction novels than i should :) |
On Device Black box testing |
Multiple ARM 32-bit systems. One multi core WiFi/BLE, one BLE, one low level hardware driver. |
VS Code
GDB
Various hardware debug tools
|
31-60 seconds |
Nothing Concrete. Loosely following misra, loose linux style, support doxygen with function comments |
When its doing more than the function name describes |
One Person Firmware team. Self Review and sometimes AI tools |
75 |
10 |
15 |
Evolving Challenges, learning new things, and seeing hardware do something with my code |
Legacy Code without comments or documentation. Maintaining Libraries for Legacy Hardware |
Usually used by Software Engineers, not necessarily firmware due to hardware constraints |
I want to learn TDD for better code practices and deliver coverage to gain trust outside my team |
Show
|
| 3 |
3 |
C |
python |
None! |
Hardware engineer that currently work as firmware/embedded engineer. |
build then test on target *_*, if it fails debug then repeat |
MCU based target |
IDE provided by MCU manufacturer |
5-30 minutes |
make the code modular.
readable.
follow best practices. |
It depends. but mostly if it does a lot of things |
there are almost no peer review, if I found something that may cause a problem I will fix it. |
30% |
10% |
60% |
Solving problems, the feelings if something works and fast development cycle unlike hardware. |
- Hardware dependence.
- If software was tightly coupled. makes refactoring a nightmare. |
TDD will:
make development more systematic.
be less debug time.
tackle problems as they appear. |
To get solid understanding of TDD, code refactoring and Enhance the design process |
Show
|