| 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
|
| 12 |
40 |
C |
Assembler |
Ceedling |
Most of my background is with "bare metal" programming. When I started programming in the mid 80's, MCU's were small and development tools were sparse. I coded only in assembler, and still find it hard to not worry about wasting bytes when I code. |
Always test behavior in system after code is written. Varies depending on function, but may include using printf statements or debugger breakpoints. |
Asset tracking device using ARM Cortex MCU |
GNU C Compiler, GDB debugger |
1-5 minutes |
We develop an agreed-upon coding standard before starting a project, but it is not enforced |
Probably when it contains elements that can be easily broken down into other smaller functions |
We use a web-based code reviewer to perform peer reviews before every commit to our trunk. |
60 |
25 |
15 |
Finding creative ways to solve problems |
Unrealistic deadlines, unstable requirements, and having too many constraints on how I code |
All I know about TDD is that tests are written before writing any code |
My boss signed me up |
Show
|
| 11 |
28 |
C++ |
C/C++/Assembly(arm)/Python |
gtest |
:) |
unit test (gtest), top level tests (system integratoin tests) |
huge legacy model (several million lines) that has existed over a decade, maintained by many teams |
c/c++/python/assembly |
5-30 minutes |
stringent C/C++ coding standards tailored by our team leads. |
more than a 'page' |
insanely strict; including a must-add test case |
25 |
35 |
40 |
problem solving and delivering value. |
digging through legacy code not undertstood by many |
nothing |
because I think i need to be good at appreciating testing and doing 'real and useful testing'. |
Show
|
| 1 |
19 |
C |
C++, python, matlab |
Custom, Google Test |
NTR |
Unit test, Integration Test, System Test, Regression Test |
x86, arm |
gcc, vscode, make, cmake |
31-60 seconds |
Readable, compact, Simple, Modular |
number of lines, number of goals, number of indents |
NTR |
40 |
20 |
40 |
Create |
The non linearity between the time spent and the impact. |
Swap the development flow and write test first, code second. Ensure quality standard designed aside. |
Explore the benefit for my team |
Show
|
| 2 |
4 |
C |
C, Type Script |
Tried using Unity |
nil |
Legacy code. Only perform UAT for any custom changes made to the code. Tried to implement Unit testing framework unity to the legacy code but didn't go well. |
We use 8bit Pic Microcontroller |
MPLAB X |
30-60 minutes |
I keep my code clean and descriptive by adding comments and using meaningful var and func names. |
When it is hard to understand at first look or when it is performing multiple functionalities |
nil |
5/10 |
3/10 |
2/10 |
I enjoy writing code that is later used in real world environment or that solves a real-life problem |
When the legacy code is hard to understand and has a lot of redundant stuff that can't be removed |
Recently introduced to TDD while working on unit testing |
To increase my skills and to use it in our legacy code as well as to implement it in new development |
Show
|
| N/A |
30 |
C++ |
Python, PowerShell,.NET, bash |
JUnit, Catch, GoogleTest |
Life-long learner. |
Unit testing, Integration Testing, End-to-End Testing |
Windows/AMD64 |
VS Code, CMake, MSVC BuildTools, GoogleTest, Git, OpenCppCoverage, BitBucket |
1-5 minutes |
C++ Core Guidelines |
When it does multiple tasks |
2-person review on pull-requests |
40 |
20 |
10 |
Creating |
Tooling issues in build and CI/CD |
Basic level |
Establish good practices for Embedded Development |
Show
|
| 13 |
25 |
C# / python |
C, php, C++, java, VB.net |
pytest, ceedling, MSTest, phpunit |
I don't write code as my job, but I manage teams that write code. This will be good for me to dive into development practices again. |
I attempt to do TDD, but sometimes revert back to not writing tests (particularly when I'm rushing) |
Desktop, Web, and Embedded Cortex M processor for an IoT application |
Simplicity Studio |
1-5 minutes |
Not officially enforced. |
If it is cumbersome to understand |
Every feature change goes through code reviews before merging with the main code branch |
50 |
20 |
30 |
I've always enjoyed problem solving, and i continue to learn new techniques to solve problems |
It seems too hard. I don't like repeating previous work that I've already done multiple times. |
It's a great method to delivering good tested code, but is a hard habit to maintain |
I signed up our team to try to improve our code delivery by finding bugs early in the dev cycle. |
Show
|
| 0 |
10 |
C |
C#, C++, Python |
NUnit |
I'm a USAF veteran and last week leg pressed 1027lbs for 3 reps |
NUnit |
WINCE, moving to Linux later this year
ARM based |
VS, VScode, Resharper |
11-30 seconds |
This company doesn't have a written coding standard. |
When I have to scroll to read (sometimes unavoidable) |
Jira ticket -> Dev-branch -> PR -> CodeReview |
40 |
50 |
10 |
Making things happen in the real world with lines of code. |
OOP obfuscation |
It reduces time finding bugs so we can code more efficiently. |
Suggested by manager, and maybe I can learn more OOP concepts too |
Show
|
| 10 months |
20+ |
c/c++ |
Rust, Python, C# |
Nunit, boost test, google test, catch |
I like sports, especially english premiership. Family man, love to BBQ and travel if I can. |
Rust unit test, Boost Test |
Linux based embedded system |
Rust standard tools, c/c++ linter etc |
5-30 minutes |
Company laid out standard for C++, Rust follow standard guide and guided by clippy. |
When stays from its purpose, get unreadable or hard to understand |
1) Does it follow the standard 2) Understand the problem 3) Evaluate the proposed solution |
40 |
20 |
40 |
I like creating and gives me satisfaction. I always learn and try to improve |
Standards for C++ changing constantly |
I know about testing software but my TDD knowledge is limited. I understand the concept. |
I really like improving and learning. We as a team suggested doing this |
Show
|
| 8 |
21 |
C |
python, vb |
none |
I'm more of a HW guy then a SW guy but like doing SW. |
in system testing |
various, mostly embedded MIPs |
various |
1-5 minutes |
standard practices |
good question, for me it would be nice if you didn't have to use the vertical scroll bar. |
use codecollaborator |
40 |
10 |
50 |
the ability to see changes and make devices do what you want them to do. |
hard to solve bugs or when the code does not do what you expect it to do |
some exposure to it, took a small course but don't actually practice it. |
I can see where it would be benefical, but I would need to be more efficient at it. |
Show
|
| 1 |
25 |
C++, Rust |
Python, shell |
Boost |
I love guitars. |
Unit tests and integration tests run in CI/CD pipeline |
Linux, running as a controller for attached devices |
VS code |
30-60 minutes |
Not sure what this is asking. |
It's not necessarily the length. A combination of length and complexity would be better. |
Reviews are done by team members before any code is merged into the development branch. |
4 |
2 |
4 |
Creating new things, and solving problems. |
Time wasted trying to debug issues. |
It is a methodology to create software where tests are written before the code. |
I want to learn how to effectively test code and have more confidence in my code changes. |
Show
|
| 7 |
20 |
C |
Qbasic, Megabasic, Rust, C++, Visual C, xaml |
None |
I play any instrument with a string on it. |
Sandbox functions - test functions by writing my own unit tests |
IoT systems |
MPLabX, Cypress Creator (PSOC), Simplicity Studio, Source meters, DMM, |
Under 10 seconds |
MISRA |
5 to 8 lines - give it a name |
Review changes with other programmers. Categorize into low, med & high risk changes |
30 |
40 |
30 |
Debugging/Problem solving. Making the electronics do something constructive. |
Working with previous, ill structured code |
Not much formally but have been doing it informally for years |
To improve my coding and unit test skills. also my supervisor signed me up for it. |
Show
|
| 3 |
10 |
c |
c++ |
cunit/gtest |
I am the agile transformation coach of this R and D org |
I am the coach and faciliator I am not actively programming :) |
x86 |
VScode |
1-2 hours |
there is one for Infinera based on Safe C |
> 1 screen |
we used to 2 level code reviews and prefer code |
5 |
5 |
5 |
building stuff that works |
that AI can do it now |
from what I have read on your blogs and few high level trainings attended |
because I am wanting everyone in my team to develop this best practice and culture |
Show
|
| 20 |
25 |
c++ |
c,python,perl |
gtest,cppunit |
I like to work with wood |
unit tests or python scripts |
embeeded device, with multiple applications mainly coded in c++ |
gcc, gdb, coverity, ctc, valgrind, visualcode, vim, libasan, cppcheck, codescene |
31-60 seconds |
we have some guidelines that everyone needs to follow. |
we have tools that give us warnings about it, but e,g if it does more then it says it does. |
we have code reviews for each pull request |
60 |
30 |
10 |
probelm solving, seeing something working at the end, doing solutions that are future proof |
having to solve other people bugs |
I have some notions I did a trainning 15 years ago. |
I was asked to :) |
Show
|
| 10 |
15 |
C, C++ |
Scripting, Java |
Boost |
I like to learn and use newer tools to ease the software development. |
In simulator with JSON based inputs. |
Embedded system running embedded software. |
VS Code, Git etc. |
5-30 minutes |
I try to follow company coding standards. |
Function is exceeding LoC threshold. |
Code is thoroughly tested and reviewed. |
45% |
40% |
15% |
I like to consider all the scenarios/use cases while designing and code accordingly. |
Hacks, hardcoding, temporary throwable code etc. |
It is about as and when coding is done, testing is also done. This avoids iterative process. |
To understand how to code and test simultaneously and deliver the code with high quality. |
Show
|
| 10 |
15 |
C,C++ |
python |
pytest |
Like to explore new languages and platform for coding. |
json based test input and manual verification of output |
optical embedded system |
visual studio
git
bitbucket |
2-4 hours |
professional |
When I stop following it. Mostly upto 2-3 levels of logic or flow or sequence is acceptable. |
good. |
5 |
5 |
3 |
It feels good when system behaves as its coded.
The user requirements are met. |
Long hours spent in debugging issues some time. |
Heard before. But will learn now. |
Nominated by my Organization |
Show
|
| 7 |
12 |
C, C++ |
Python |
Command line interface is used to execute the SW/APIs added with various arguments. |
I am a SW developer who likes to keep the SW design as simple as possible which helps in debugging issues. |
Yes |
Embedded Linux |
VSCode |
Under 10 seconds |
We follow the coding standards preferred by the organization.
Camel case used for methods, etc. |
Based on the no. of line and the no. of branching conditions used. |
Bitbucket is used for code reviews. |
6 |
2 |
2 |
The automation that SW provides which makes things simple and quick. |
Complex design which involves too much time to debug if its not self written. |
TDD is basically writing SW for the already defined test cases. |
To know more about TDD and how to accommodate it in my SW development process. |
Show
|
| 4 |
15 |
C++ |
Python |
Proprietary tool |
Passionate engineer, part of a team which develops complex SW which wants to be a world class R&D team |
Automated test cases |
Telecom optical equipment |
VSCode, Vim |
1-5 minutes |
C++ 11 |
By number of lines |
Constructive feedback will be provided and most of the corner cases will be evaluated |
60 |
25 |
15 |
Would love to write complex logic and debugging all corner cases |
To debug issues which are hard to reproduce |
Having unit test cases ready before development itself, so that all the modules can be tested |
To know more about TDD and to develop SW with great quality before test cycle |
Show
|
| 5 |
12 |
C |
CPP |
None |
Little busy with office work. Will be giving short answers to completes these tasks. |
UT |
Yet to explore |
normal |
30-60 minutes |
company standards |
By counting lines :) |
Team reviews |
3 |
3 |
4 |
Satisfying |
Tricky at times |
Not yet aware |
NA |
Show
|
| 5 |
9 |
C++ |
C, python |
gtest, Testwell CTC++ |
Passionate about network security |
Most of the times it is manual test. We build and replace the modified binary/library in target system and check. |
SW applications running on Debian |
vscode, tabnine |
1-5 minutes |
C++11 |
We use a tool called codescene which is available as plug-in in vscode |
Bitbucket PR review |
2 |
5 |
8 |
Be thorough with design before starting implementation |
Changing legacy code |
Have been trying to follow this approach since moving to agile teams |
Have been struggling to develop unit test cases in embedded software |
Show
|
| 15 |
25 |
C++ |
C
python |
gtest |
I'm in scrum master role. I like sports. I have a son. I live in Lisbon, Portugal. |
unit tests, script/automation tests and manual tests |
embedded systems running Linux |
VS Code, Pycharm
Colaboration tools: Confluence, Jira, Bitbucket, Jenkins |
30-60 minutes |
following the company guidelines |
when it doesn't fit within the screen |
mandatory in Bitbucket pull-requests |
50% |
30% |
20% |
interaction with the system and HW; finding the best way to implmnt a feature and doing future proof |
complexity that sometimes people do SW, that us caused by a gap in the design and solution grow |
tests are done before the code |
TDD is great approach.I want to learn it, so I can help my teams to implement it and improve quality |
Show
|
| 2 month |
7 years |
Embedded c |
C++ language |
Not yet used my project. |
no |
TDD frame work |
stm32f427 |
STM32CUBEIDE |
5-30 minutes |
MISRA C |
while development |
no |
50 |
30 |
20 |
expected solution when facing some problem. |
Documentation process |
not more |
understanding the test driving code for quality development. |
Show
|
| 1 |
5 |
c |
python, rust, java |
junit |
I like programming for a living but I like also to see the Sun sometimes :) |
manual testing in real products |
linux and freertos environment |
visual studio, logic analyzer, oscilloscope, jtag |
31-60 seconds |
none |
divide in some functions |
none |
50 |
10 |
40 |
transform and control reality, make things easier and more confortable, automatings things |
getting stuck in the same step for long time. In one word, debugging. |
barely nothing |
I want, and in extension my company, to start testing our products before QA team gets involved. |
Show
|
| 1 |
10+ |
C |
JavaScript, C#, C++, Assembler |
none/unknown |
I've spent years doing end user support for nationally distributed products that run software I wrote. If they're gonna hot plug it you should try hot plugging it at least once before it leaves the building... |
some of the legacy code here is tested using tools developed after Grenning training (10+ years ago?). I know zero details beyond: "the tests run at build time" |
various embedded systems, more towards the 32 bit microcontroller |
eclipse, xdc tools |
11-30 seconds |
there is a modified Embedded C Coding Standard (Barr) applied to some legacy code |
too many arguments... runs off the screen in both x and y
directions |
informal if existent |
3 |
3 |
3 |
seeing intuitive, useful electronic hardware work with high performance, despite the complexity |
legacy code mess. lack of documentation. overly complex solutions to simple problems. |
I read the first few chapters of the Grenning book years ago. |
I want to see generic TDD before figuring out how it was implemented here in legacy code |
Show
|
| 0 |
5 |
C |
None significantly |
None significantly |
I enjoy going to concerts and playing sports. |
Creating test procedures based on code features and validating against. |
Embedded devices, iot. |
ide, repository control, text editors, ai, debuggers. |
11-30 seconds |
Follow standard naming and organization practices, attempt to keep code highly modular and readable. |
When the purpose of the function becomes convoluted or easily separatable. |
Have not had any yet with current company. |
33 |
33 |
33 |
Seeing words become functioning products. |
Tedious work like documentation. |
Mildly familiar from college education. |
Company requirement |
Show
|
| 1 |
10 |
C |
C++
Python
Powershell
|
pytest
company uses google test |
no |
pytest + python + powershell |
Arm Cortex M7, comms mostly via CAN |
VS Code
MCUXpresso
Segger J-Link
Picoscope
|
31-60 seconds |
self-defined |
when it scope stops being easily understood |
non exist |
30 |
40 |
30 |
When it finally works |
When it doesn't work + all the legacy crap |
dipped my toes into it, started using it a little bit |
Want to go from using it a little bit to using the correctly, especially with legacy code |
Show
|
| 1 |
5 |
C |
C++, matlab, python |
cFS unit test framework
|
I am a telecommunication engineer, but I work as a software engineer, and I would like to improve my developer skills with this course! |
unit test with cFS, system test with robot framework, "manual" functional test |
spacecraft on-board computer |
git, cmake build system, vscode |
1-2 hours |
none |
when it has more than 3 nested branches and too many lines (>80) |
code reviews are requested by developers when they finish a task, they are mainly based on design |
30% |
30% |
40% |
seeing that my script is running and working in the real word is satisfying |
doing unit tests, sometimes we write tests that are not useful, and we do it only for the coverage |
it helps in writing code and tests in a more effective way |
to learn a new method to develop software and try to apply it in our project |
Show
|
| 2 |
10 |
C |
C++, python |
cFS unit tests framework, lcov |
i really like embedded system, especially if made for the space sector, and critical or real-time system, hope this course may help me to develop a methodology to realese higher quality and more reliable software |
unit tests up to a minimum coverage, robot framework for system level tests, "manual" functional tests |
satellites on-board computer |
git, cmake as a build system, vscode, self-hosted LLM |
1-2 hours |
unfortunately nothing strict, based on most known misra C guidelines |
when it takes more than 70/80 lines or has too many nested branches (> 3/4) |
code reviews are requested by developers when they think they need it, focused on design |
40 |
30 |
30 |
seeing the software execution effects in the real world (e.g. actuators, sensors reading, etc) |
unpredictability, it's frustrating when behavior differs from what you imagined while programming |
it relates to incrementally build unit tests, extending them while the tested feature advances |
explore different methodologies, understand if this would fit well in our development process |
Show
|
| 7 |
10 |
C |
Fortran, C++, Java |
check, gtest |
When I'm neither with my family nor programming, I love riding on bike. |
Tdd mostly since last year, mncks, DLP |
Embedded Xilinx devices |
Qemu, libcheck, mocks |
Under 10 seconds |
Misra C 2012 |
When I'm getting confused about what it was doing since its starting sentence |
Deep code review, understanding of requirements |
50 |
40 |
10 |
Easy to learn every day |
Not understanding what Javier wanted to do some time ago |
I read TDD for C/C++ about one year ago, and It is reducing a lot of uncertainity |
I wanted more exercises after reading the book |
Show
|
| 6 |
>12 |
C |
Python
C++ (very rarely) |
None |
From South Africa, live in Berlin, have 2 cats, still love the Commodore 64. |
Manual tests, custom python scripts, ci-fuzz, cpp-check |
ARM processors (STM32, nRF52) with Ethernet/Wi-Fi and various radios. RTOS or bare metal. |
makefiles, cmake, arm gcc, vim, github |
11-30 seconds |
I like Henning Schulzrinne's style. Tabs to 4 spaces. Consistency with existing code. |
Too complex to easily follow. |
Each PR is reviewed by another developer. |
30 |
40 |
30 |
Solving problems |
Chasing difficult to reproduce bugs. |
Writing tests for all code upfront. Testing first and throughout development. |
I want to better test my code. To create reliable code. |
Show
|
| 25 |
58 |
javascript |
SQL, C ,Java |
none |
most of the time I am a sloppy programmer, but I can prototype like crazy. |
manually |
NetSuite customization and scripting |
gitlab, notepad++ |
31-60 seconds |
an agreed upon set of conventions for naming and structuring code. |
gut feel. |
all code and code changes gets reviewed by at least one person. Code reviewers rotate. |
30 |
40 |
30 |
its like solving puzzles |
gathering requirements |
nothing |
desire to learn |
Show
|
| 1 |
3 |
C |
C++, Python, Shell/Bash scripting |
C- libcheck
C++ - googletest
Python - pytest |
I'm a Telecommunications Engineer, specialized in Electronic Systems, who likes the embedded software.
I work in the Space sector, developing software for GNSS (GPS or Galileo specifically) receivers. |
Unitary tests, corner tests, functional tests and (if applicable) performance tests. |
Embedded Linux-based systems. GNSS receivers. System on chips. |
Visual Studio Code IDE (previously Eclipse).
gcov/lcov, cppcheck, Valgrind, clang-tidy/format |
Under 10 seconds |
Coding, testing, debugging, CI checking, consistency, errorhandling, compliance, cross code-reviews. |
It is not fully shown in a 24'' screen. For sure operations can be moved to functionality groups. |
Deep code reviews about the functionality of the code, and docs, convention, etc done by CI |
4 |
4 |
2 |
I enjoy the creativity and problem-solving involved in developing software. |
Sometimes not trivial at all. Embedded systems present Operating System and hardware dependencies. |
I've read the Test-Driven Development for Embedded C book and took some university lessons. |
To deep into the knowledges from the TDD book. |
Show
|
| 3 |
6 |
C++ |
Python, Java, C#, qml |
CppUTest |
Interested in design, architecting the software in a way that is easily adaptable to change |
Unit testing with CppUTest before merging and periodically performing integration tests |
Testing features of medical devices |
VSCode, IAR, QtCreator, Bitbucket |
1-5 minutes |
MISRA and IEC 62304 |
If the function is doing a lot more than what the name of the function suggests |
Reviews completed before merging code |
35% |
25% |
40% |
You can be somewhat creative with it and I like seeing the impact |
Sometimes it is difficult to jump into a project that has legacy code |
You write a test and then code to make the test pass |
Slow on work and a good intro to the concept to integrate TDD at company |
Show
|
| 4 |
46 |
c |
C++, Python |
Vermont Software, (defunt) Nothing modern |
I have a heavy Database background and like riding a bicycle. |
QA Feature regession testing for functionality. Firmware engineer edgecase testing. |
ESP32 WROOM 32E SoC |
VSCode with extensions for C and python |
1-5 minutes |
I have one, I just can't describe it. Which is not a good sign. |
When it has nested returns. |
Currently we have 1 other FW engineer to a Pull Request |
30 |
50 |
20 |
Getting a piece of refined sand to think it endlessly funny to me. |
dealing with requirements from people that don't fully know what they want. |
It's a paradigm shift in order of operations to writing software. Test first, then code. |
Hoping to gain insight in to faster code development by having some structure in place |
Show
|
| 2 |
5 |
C |
Only C |
N/A |
I love to design on my own embedded system including PCB design and firmware development. But I need definitely learn how I should do it systematically. |
With IDE. |
STM32 Microcontroller. |
STM32CubeIDE |
1 day or more |
C99 |
Number of lines |
I don't have a code review experience. |
10 |
10 |
80 |
Nice to see for controlling designed hardware. |
No one can help me to debug the issue due confidentially of my projects. |
There is a book related this book from James Grenning. |
Developing firmware smoothly and teach to students or any learners how they develop firmware. |
Show
|
| 4 |
6 |
c |
python,C# |
None |
I am active in jiu jitsu outside of work. |
Debugging tools |
STM32 and ESP32, we will have some other chips in the future. |
STM32CubeIDE
Visual Studio Code and a variety of plugins |
31-60 seconds |
Clean, concise and simple. |
the whole function should be seen an editor view that has a console at the bottom. ~40 lines or less |
At work they have been minimal I hope this course helps us establish better practices. |
20 |
40 |
40 |
I like the ability to program hardware to do real world data acquisition or actions. |
I don't like full ownership of large projects by a single dev. |
I only know that test cases should be written first then code is written to fit those cases. |
My team enrolled as a group learning project to help our company establish a standard. |
Show
|
| 1 |
30 |
Embedded C |
C++ |
none |
I don't have all the answers, but I can find them! |
Unit and integration |
Embedded PIC16,PIC32 and ESP32 |
Notepad++ |
1-5 minutes |
No business coding standard. Personally I use Michael Barr's Embedded Coding Standard |
When it has too many branches |
What code review? |
80 |
10 |
10 |
Able to find creative solutions to a problem/task. Control of robots. |
Never an expert |
Don't know yet, still learning |
Required |
Show
|
| 0 |
16 |
C |
Python, C++ |
CppUTest, GoogleTest |
I am learning all the best firmware practices by reading your book, following Elecia White's podcast and memfault interrupt blog. |
Manual testing |
STM32 |
STMCube IDE |
31-60 seconds |
K&R style |
When its doing too many things than the desired functionality. |
We dont have that process setup yet |
4 |
2 |
4 |
Solving problems at low level |
Working with tightly coupled code and code generated by the IDE. |
I have read your book in the past and have written some unit tests. |
To actually deliver high quality firmware. |
Show
|
| .6 |
5 |
embedded c |
c
c++
python
java
|
QTP |
WORKING ON MICROCONTROLLER FOR THE INDUSTRIAL APPLICATION. |
unit test |
Multiple peripheral system |
STM32 CUBE IDE |
Under 10 seconds |
MISRA |
TAKING TOO MUCH TIME FOR DEBUG |
2 CYCLE REVIEW |
30 |
30 |
40 |
CODE DEVELOPMENT AND TESTING |
DEBUG |
TDD IS A USEFUL TOOL CAN BE USED FOR IMPROVING THE FUNCTIONALITY OF FIRMWARE |
TO IMPROVE MYSELF AND TEAM |
Show
|
| 3 |
20 |
C |
python, C++, pic basic, vhdl, verilog |
none |
I like biking, running, and climbing, dnd, and Pokemon go |
I test edge cases and then come up with a test plan for a technician to run. |
embedded devices |
VScode, eclipse based IDEs |
1-5 minutes |
I have mostly written prototype/proof of concept code, but I have also done some production code |
Uh… I don’t think that is necessarily a thing, especially if you are trying to squeeze processing ti |
I have never done one |
3 |
3 |
4 |
bringing machines/code to life |
useless meetings |
nothing |
my boss said to |
Show
|
| >1 |
8 |
C |
C++
Python
TypeScript
Dart |
Ceedling |
n/a |
Manual functional / behavioral test suite
I started at Whisker as a FW QA Engineer in July, I have become familiar with Ceedling and am in process of adding unit test capabilities to FW team. |
Main MCU is PIC but is being phased out with STM32, all targets have companion ESP32 for Wi-Fi. |
VSCode
Espressif's ESP-IDF
STM32CubeIDE |
1-5 minutes |
Not established |
When it can become modular or easily separated into discrete steps. |
Have not participated in one, but have recently set forth a plan to make this a regular occurance. |
n/a |
n/a |
n/a |
Solving problems, Exercising creativity, |
Firmware can be frustrating because of non-intuitive SDKs, clunkiness of building, flashing/debug |
Unit tests are created during planning for new code, and unit tests guide development of code. |
Our firmware group at Whisker plans on adopting TDD to consistently deliver quality firmware. |
Show
|
| 2 |
45 |
C |
Python, C++, Rust, Bash, ... |
Python unittest, Catch, in-house |
Hi! |
varied: Unit, integration, E2E tests. Very few human-in-the loop manual tests. |
varied: FPGA, MCU, Embedded C, Linux |
git, gcc, CMake, CLion, JIRA, Jenkins, Docker, Artifactory |
Under 10 seconds |
Informal |
Judgement call |
Pair program instead |
10 |
10 |
20 |
Creative, challenging, crisp analysis. |
Complexity, bloat, inconsistency, too much code that should never have been written. |
Once did a 2-hour TDD course: inspirational, but I desire additional teaching. |
I want to develop the finest TDD skills I can, and be better able to coach colleagues to do so. |
Show
|
| 2 |
40 |
C++ |
Python, Go, C, Java, C# |
Various, mostly home grown |
I dislike open ended questions without discussion |
Varies |
Varies, but mostly Linux VMs (not embedded) |
Varies |
1-5 minutes |
Varies |
Getting harder to change |
Varies |
50 |
20 |
10 |
Flexibility, learning new stuff |
Deadlines set without a good estimation process |
Just the basic principle |
Learn more about embedded development process |
Show
|
| 2 |
20 |
C++ |
Python, C, Rust |
Catch2 |
thinking and doing this stuff is hard when you're tired |
Catch2 unit test, end to end test using python |
varies |
CLion, Git, Gitlab |
11-30 seconds |
not strictly enforced |
when it's larger than say 10-15 lines |
continuous pair programming |
33 |
33 |
34 |
thinking about creatively solving problems in the best way |
not knowing why something doesn't work, spending hours on it |
the main stuff: write failing test, make it pass in the simplest way, refactor |
what "level" to write the tests at? (e.g. external interface only etc) |
Show
|
| 2 |
5 |
C, Java |
C++ |
Cmock, Cpputest |
na |
unit and integration tests |
arm, x64 |
jetbrains suite, vs code, sublime text |
1-5 minutes |
Conforming to Java 17 |
When there's conditional or logical operation words in its name e.g. "and" "or" "when" |
3 reviewers on every change, 2 junior and 1 senior |
5 |
3 |
2 |
Building new things, figuring things out, and finding how systems work & interconnect w each other |
The lack of country/continent-wise recognised certifications ala medicine professionals |
Test-first emphasis to eliminate regressions & guarantee behaviour for a set of (specific) reqremnts |
To see if TDD is better understood, appreciated and internalised through a workshop instead of book |
Show
|
| 2 |
1 |
Java, C# |
Python, XML, HTML, JS, SQL |
0 |
I'd like to get less technical about QA and instead head towards leadership and Systems Engineering. |
BDD, Manual QA, Black Box, Automation Tests of functionality, Integration testing, System Testing, Regression testing. |
Any complex software application |
VSCode, Notepad++, SQL, Docker, Cucumber, |
11-30 seconds |
Not much to tell, I mostly just script and do QA. |
When the scope of the function tries to achieve more than 1-2 things at once by itself. |
I don't do any. |
1 |
7 |
2 |
I do not like developing, this is why I joined the Quality Engineering career path instead. |
Tedious debugging, unclear errors occurring from typos or small coding syntax errors |
It's a programmatic way of shifting testing to the left. White-box testing. |
To learn more about automation, left-shift and white-box testing. |
Show
|
| 2.6 |
16 |
Embedded C/C++ |
All sorts of programming languages e.g. java, python |
google unit test |
Passionate about software engineering, enjoy travelling, good food |
Catch2 with google mock |
Linux |
GCC |
31-60 seconds |
varies with project |
when it is doing more than one thing |
use gitlab |
40 |
40 |
20 |
designing |
debugging |
You write test first and then code later |
Want to understand tdd properly. |
Show
|
| 6 |
10 |
C++ |
C, Python, Rust |
Catch2, pytest, nosetest |
I spend some of my spare time cycling and baking. |
Unit tests with TDD
Host integration test
Target end to end tests |
Embedded systems, some running CentOS or Debian Linux, some bare metal. C and C++ applications |
CLion, CMake, Git, Jenkins, Docker |
5-30 minutes |
Per-language coding standard for ISO quality system. Bit out of date, I tend to use modern standards |
More than a few lines, hard to read, does too much, not single responsibility |
Not required very often as dev is done using pair programming. Reviewed by senior devs during dev. |
10 |
40 |
50 |
Making cool stuff. Working with fun people. |
hard to read/understand code, slow tests, not having enough time to do it properly |
Test driven development drives the writing of code through tests. Red, green, refactor. An art form |
learn the art of TDD; how to write tests to drive the code, how to do abstraction/interfacing |
Show
|
| 10 |
20 partial |
C |
C# |
None |
I do not develop software full time. My main activities consist in developing electronics boards, writing code for the embedded microcontroller (bare C) and often writing GUI (C#) that interacts with hardware. |
Debugger |
? |
Keil MDK ARM, Visual Studio |
Under 10 seconds |
? |
When I can't remember what happened at the beginning |
No review |
5 |
5 |
5 |
Flexibility. |
Never works first time |
Only got an introduction to it, but sounds interesting |
To learn new methodology. |
Show
|
| 3 |
10 |
C++ |
C
Python
Rust |
Catch2
cpputest
Pytest
Cargo test
Cucumber |
I spend a lot of my free time on the river rowing and coaching rowers. |
Unit and integration tests in Catch2
End to End tests running on hardware in Pytest |
STM32 microcontroller |
Clion
STprogrammer and STlink |
11-30 seconds |
We aim for TDD and pair programming whenever possible. |
To many functional blocks/regions which should then be refactored to separate functions. |
Minimal due to heavy use of pair programming. However diffs are reviewed between releases. |
20 |
30 |
50 |
Solving the logical problems |
Maintaining documentation |
functionality/interfaces are first defined in the tests, code is then written to pass tests |
Professional development, and whilst I have learnt TDD on the job, I've never had a formal course. |
Show
|
| 3 |
15 |
Python |
JS/TS
SQL
C#
|
Pytest
Unittest
Robot Framework
React Testing Library |
As well as programming I love hiking and the outdoors |
Write the code and if time permits write unit tests.
Then update integration tests to make sure code base works as a whole.
Run robot framework on the output to make sure the behaviour is correct.
QA manually sign off that everything is working. |
The target is docker containers which run the data pipeline |
VSCode with Python Extensions
Copilot |
Under 10 seconds |
ISO9001 |
When it doesn't fit on your screen |
Done through the PR interface. Usually offline but if it is complex, done on a call |
30 |
10 |
60 |
It is my hobby and people pay me for it!? Mainly the puzzle solving aspect. |
Being told what and how to build something. |
Write unit tests first, then code to satisfy those tests. |
Out current testing approach isn't working. I am interested in other approaches for testing. |
Show
|
| 18 |
18 |
C |
C++, C#, Ladder Logic, Structure Language, Motion Perfect, VB |
CMOK, CUNIT |
I am an active person, I love scuba diving, I am a go-kart racer |
depends on the project. Hardly even pure TDD, a bit of mixture of soft TDD and test created after coding. Both unit and integration tests on PC, the same on HW + System test. |
Embedded (ARM, etc.) |
All sort of Editors (depends on client) |
1-5 minutes |
MISRA, internal and external, |
>20\30 lines? |
used a number of tools |
40 |
30 |
30 |
I can see results immediately, I like logical thinking, the interaction SW\HW, Human Factors |
debugging, legacy code, spaghetti code, compiling dependencies, cryptic test frameworks |
I know the principles and apply some of them |
to learn how my life can be made simpler when coding, and producing good modular code |
Show
|
| <1 |
2 |
Python |
C++
Javascript |
unittest |
Mangoes are one of my favorite fruit |
By writing unit and integration tests |
Don't have one.
It can change at any point. |
IDEs and Code Editors.
Version Control.
Package and dependency managers.
Debuggers
|
31-60 seconds |
Normally PEP 8 |
When it does more than one thing or more than what can be easily described through the function name |
They go okay |
40 |
50 |
10 |
Having different solutions to one problem. |
Libraries that contain unpatched bugs |
It's difficult at first but rewarding at the end |
Because I want to get better at TDD |
Show
|
| 4 |
10 |
Python |
C++ |
Catch2
pytest |
Looking to go from working in mostly in Python to do more C++ and also embedded work so I'd like to do those things with TDD from the start rather than learn to code then figure out how to TDD it |
Using TDD - unit, integration, e2e. Automated CI to run tests on hardware |
Linux based systems, Raspberry Pis, cloud |
VScode, Jenkins, Docker |
Under 10 seconds |
Use TDD and clean code |
When it does more than one thing |
Usually pair program so the code review is done during development of a feature rather than after |
3 |
6 |
1 |
Continual challenges. Variation in projects. Satisfaction when a complicated things is simplified |
Often not enough time to go back and perfect the code |
Write the test first then the functioanlity. |
I want to get better at delivering high quality code and I see being an expert in TDD as the way |
Show
|
| 20 |
25 |
c |
c++ rust |
ceedling catch |
i tend to focus on embedded coding |
catch unit test
python integration and end to end tests |
microcontrollers embedded |
clion
gcc tool chain |
5-30 minutes |
c and c++ |
review
it becomes difficult to understand |
pair programming or formal document |
30 |
50 |
20 |
producing quality code
solving problems |
i'd like to do more of it |
write tests before changing code
change just enough to make the test pass |
i have received feedback that I need to improve my TDD skills |
Show
|
| 6 |
21 |
C# |
Python, Java, JavaScript, C++, C (although very rusty in C++ and C) |
MSTest, NUnit, JUnit, Selenium |
Father of 2 (10 and 7). Love my garden, keen badminton player and currently in the middle of doing loads of DIY on an extension project on the house which started in 2020. I've been working as tech lead for 7 months and want to get my hands dirty! |
On the current project we have a blend of Unit Tests, Integration tests, System Tests, performance tests and, unfortunately, a heavy contingent of manual tests still. |
Python Data Pipeline which pushes data into a Postgres Database fronted by a .NET / JS web app. |
VSCode, Visual Studio, Git, GitlabCI, Docker, Azure and associated tooling |
11-30 seconds |
All python is written to PEP8, C# is written to an internal standard |
We use in-built tooling in the IDE to flag this |
All code goes through peer review and gets signed off through a formal QA process on client data |
50 |
30 |
20 |
Problem solving and being able to take an idea and make it come to life |
Trying to explain to people who don't understand software, why building good software is important |
I know the principles but struggle with the application on a macro scale |
I want to understand how to 'think' properly about testing at the macro level |
Show
|
| 3 |
15 |
C++ |
C, Python, others |
googletest |
I've a fair amount of code for many systems in my life. But for the past 5 years I've been more architecting than coding, which has made me rusty. I try too hone my skills at home with personal projects, primarily coding games and robots. |
googletest |
embedded |
various |
31-60 seconds |
Using company coding standard |
when I have to scroll my screen |
pair programming, walkthroughs, formal reviews. |
30 |
40 |
30 |
The creative challenge |
management's misunderstanding of software |
start with writing tests that fail. then code till tests pass. |
to learn |
Show
|
| 2 |
40 |
C |
C++, Java, ... |
No much Unit testing Experience. Years ago I got some Junit during period working in Java |
I would like to become TDD fun after this training. |
My role is not currently development, as I am mainly on Support and with some devops. I write code occasionally for demostrations an recreating customers issues.
I normally write test cases. |
No target on this |
VS Code or JetBrains Tools. I have used others in the past. |
Under 10 seconds |
No comment |
It depends on the language, but based in the number of lines. |
No comment |
60 |
20 |
20 |
Continuous learning. |
Deadlines |
Very little, I think. I never had my brain set for the TDD. I normally focus on design. |
Learning the the TDD, and using it when I have to write code. I don't work on big projects though. |
Show
|
| 2 |
6 |
Python |
C++, Rust, Bash |
Pytest, Unittest, Catch, Cargo |
I studied aerospace engineering, I didn't study computer science. |
TDD, testing locally before pushing to CI.
Tests run in CI using Jenkins pipelines. |
Data diodes and their surrounding software for customer ease of use. |
Nvim, GitLab, Jenkins, Docker, Jira |
1-5 minutes |
2 years professional experience with 4 years in my degree. I try to actively improve my standard |
If things are not at or close to a single layer of abstraction. |
We use pair programming for the purposes of code reviews. |
10 |
10 |
80 |
The ability and opportunity to solve a wide variety of problems. |
Business challenges that slow down or stop you from developing. |
It should be used to guide the design of the code from the perspective of the user of the function. |
TDD is controversial, I want to grow a pragmatic understanding of when and how it should be used. |
Show
|
| 2 |
40 |
C++ |
C, Rust |
Boost.Test
Ceedling
Rust's inbuilt test harness (cargo test) |
Not on this form. |
Unit testing |
Armv7 SoC |
VS Code + language-specific extensions; git, Jira, valgrind |
1-5 minutes |
C, C++ coding standards located in company Quality Management system. TDD is not mentioned. |
When a reviewer suggests it might be. |
They depend on who is doing the reviewing. |
30 |
40 |
30 |
Problem solving |
Estimation |
Its use is controversial and subjective. Tends to polarise developers. |
Information declined. |
Show
|
| 0 |
11 |
C, C++, Python |
Flutter |
Unity, pytest, inhouse tools |
I like to play golf, and in my spare time I'm making an app for couples so that they can try new dates and be reminded to be romantic. It's fun because it's very different from embedded development. |
unit tests, function tests, system tests, manual tests |
IoT devices, embedded product with connection to cloud |
zephyr, git, cmake |
5-30 minutes |
Use tools like linters and static analysis to make sure everything at least looks the same |
When I need to scroll down a long way and it does way to many things |
Mine are usually pretty small and concise, |
20 |
40 |
40 |
Solving interesting problems and "make something out of nothing". I get to be really smart at times. |
Tight deadlines, and when the tech lead doesn't want to do anything too complex |
The basic structure, but I've never gotten it to stick. |
I want to become better, and make things go more smoothly. |
Show
|
| 0.1 |
30+ |
C++ |
C, Python, PHP, shell, assembly, Java, Javascript, Objective-C, ... |
CppUTest, XCTest, JUnit, Selenium, ... |
I don't like this planet. |
CppUTest |
custom embedded platform (Arm and x86) |
VSCode, Makefiles, git, Jenkins |
31-60 seconds |
We don't seem to have a formal coding standard here. :( |
I try to keep functions to within a page of lines, but this is arbitrary and subjective. |
PRs are reviewed before merging to main. Who reviews is chosen by the PR author. |
20% |
5% |
10% |
Problem solving |
Agile |
Step 1: Create tests to enforce spec requirements.
Step 2: Code to pass tests.
|
Assigned as a new hire, plus it's good to refresh my knowledge. |
Show
|
| 1 |
5 |
C/C++ |
Python, bash |
CppUTest, ZTest, BATS. |
As many software engineers are, I'm a technology enthusiast. I went to school to computer engineering and I also love the hardware-side of computing. |
I try to cover as much of my code as I can with unit tests, and run functional and integration tests too. |
I primarily write code for embedded ARM processors in avionics systems. |
git, vscode, docker, gdb, github. |
11-30 seconds |
we use our own standard developed over the years for formatting. |
If you start having 4, 5, or 6 parameters that's a tip-off. Also simply the number of lines. |
My goal when going through code reviews is to keep them as small in size and scope as possible. |
60% |
10% |
30% |
The speed with which you can build things. Iterative design. |
Managing dependencies between new and old code bases. |
Write the tests before your code and you'll catch a lot of mistakes that would have slipped by. |
My employer would like me to undertake this training. |
Show
|
| 0.3 |
9 |
C |
C++, Python, Javascript, Java |
Unity, Ceedling, GTest, Jest, JUnit |
I'm Icelandic |
Post-hoc with heavy mocking |
STM32 series microcontrollers |
CMake, GCC, CLion, cpplint, sonarqube, gitlab |
11-30 seconds |
There is none, only a cpplint config. |
When you've forgotten the start by the time you get to the end |
Two mandatory reviews per pull request, one dev, one QA |
5 |
3 |
2 |
Experiencing the simple joy of creation, fulfilling the fundamental human need to improve our world |
Working with people that don't care |
I've read Beck's book, but haven't applied it to anything beyond university assignments |
It was offered to me, and I'd like to write better tests |
Show
|
| 1 |
30+ |
C++ |
C, C++, Python, JavaScript, Java, Php, HTML, CSS, MySql, assembler, etc. |
roll my own |
:) |
manually |
game consoles, pcs, etc. |
all and any |
5-30 minutes |
depends on the language but write-test loop, re-evaluate, comment push to complete |
short and sweet is best |
solo developer so it's new terrain |
50 |
40 |
10 |
creative moments of system design |
micro-management and having to type |
necessary step |
employer assigned to me |
Show
|
| 9 months |
14 years |
C++ |
Rust, Python |
Google Test, CppUTest, Rust built in. |
I like to cook. |
CppUTest |
AMD X86 embedded, Arm V7 & V8, Alpine musl for static builds |
Make, CMake, VS Code, Sublime Text |
31-60 seconds |
I base my coding standards off the standard that the company uses. |
If it's possible to break the work up into smaller functions then it's too long. |
Unless I see a major reason for a change I generally only ask probing questions make recommendations |
7 |
1 |
2 |
Being creative and solving problems, which includes debugging. |
Commenting code |
The goal is develop tests first and then write the functions later to verify they do what you need |
Company requirement |
Show
|
| 3 |
5 |
VHDL |
Verilog, C, C++, C#, VB |
None |
I prefer writing HDL due to more in depth testing/simulation tools |
Test Benches, Prayer |
ARM processors on Xilinx MPSoCs |
Vivado, Vitis, Visual Studio, VS Code |
5-30 minutes |
Outdated and now followed by everyone |
If there is repeated Code |
None |
2 |
3 |
5 |
Fun to solve problems |
Vendor provided tools |
Nothing |
To learn new ways to develop more efficiently |
Show
|
| 1 |
8 |
C# |
C, C++, VB, HDLs |
Visual Studio Unit Test projects |
I find that there is nothing better than 80s hair metal. |
"Automated" testing by writing code to test code, not using a unit test framework such as the one provided by .NET. |
Windows machines, Xilinx devices |
Visual Studio, Vivado, SDK |
1-5 minutes |
Not much of a standard, some linting practices. |
Likely when it is doing many different functionalities rather than what the name implies. |
Using either a lead dev on a project or a group of people to review code prior to merging to main. |
15% |
35% |
50% |
Seeing my code function properly and return the correct output given a broad range of inputs. |
Fully testing functionality to catch every edge case at the end of writing the code. |
Using testing throughout the software life cycle to save time and sanity when developing. |
To gain better knowledge about TDD in the embedded space. |
Show
|
| 21 |
21 |
python |
IEC-61131 (ladder / structured text), Labview, TestStand, C, C++, C#, Matlab |
pytest, Unity |
I was born in Normal, Illinois |
For code touching hardware, most is done with custom code that allows hardware to be exercised to verify functionality |
Windows PC and/or embedded target |
Vendor provided (MPLAB / Keil)
Visual Studio Code
|
11-30 seconds |
no formal std try to follow best practices |
If it is doing too many things, or if the number of lines of code is long |
Internal use - informal or None depending on scope
External - Formal peer reviews |
30 |
40 |
30 |
Ability to bring hardware together with software to create a cohesive system. |
Working around bugs/issues in vendor provided development environments. |
I have been reading your book as well as done exercises from throwtheswitch.org |
I want to be more efficient at applying/championing TDD to future work |
Show
|
| 4 |
8 |
Python |
C/C++, HTML, JS, CSS, MATLAB |
Not a familiar concept to me |
I love to snow ski in Colorado! |
Limited independent peer review, personal stress testing for edge conditions and critical logical conditions |
Not sure what is meant here. I don't have any specific procedure. |
Stock IDE tools for code generation and basic debugging. |
Under 10 seconds |
Keep nesting under three, use descriptive names, composition over inheritance, few global variables. |
Greater than three levels of nesting, or exceeds what can be shown on a standard screen. |
Informal and without a written description. Reviews performed by developers of the code. |
25 |
25 |
50 |
Playing a game or solving a puzzle, the more complex the problem the more satisfying the solution. |
Scale and learning curve is daunting. Too many assertions of a 'right' and 'wrong' way to do things. |
Very little, I'll try to come in with as open a mind as possible! |
It was suggested by my manager. I'm not a software developer by trade, but would like to learn. |
Show
|
| 5 |
<1 |
C |
none |
don't know / n/a |
. |
see if it does what i want it to |
arm microcontroller |
code composer studio |
Under 10 seconds |
don't have one |
it does more than one thing |
haven't done any |
40 |
20 |
40 |
satisfaction from getting code to work |
taking forever to find bugs |
nothing |
someone signed me up, plus it'll be helpful for a project i'm working on |
Show
|
| 7 |
1ish |
C |
Python |
UNK |
I enjoy rock climbing |
As I generate code, I create test functions at the bottom of the same file. The tests are intended to catch edge cases and compare function output to known good output. The test functions are wrapped in #ifdef for easy removal. |
Embedded C on microcontrollers & some scripting with Python |
Vendor provided IDEs (Code Composer Studio, STM32CubeIDE, etc.) |
11-30 seconds |
Unsure, as I recently began dabbling in firmware development out or curiosity. |
When code is repeated within the function, or the function is difficult to understand. |
After verifying functionality, I look to senior programmers for feedback on style and implementation |
40 |
20 |
40 |
I love solving puzzles, and it feels like I'm solving endless puzzles. |
My current level of understanding in the C language can lead me astray at times. |
I create a test function with known output, if I can, that I can compare my program to. |
I find embedded C interesting and I want to do more of it. To make that happen, I must improve :) |
Show
|
| 5 |
10 |
C++ |
C
Java
Python
Bash
|
None |
Love to code |
Functional tests as I'm programming |
Linux |
VS Code
GCC
Docker
Git |
5-30 minutes |
Project dependent |
When it starts repeating itself or doing the same things as other functions. |
We don't have a lot of them, and don't have a process established yet. |
50 |
25 |
25 |
Making computers do neat things. Solving problems in creative ways. Creating an end-product. |
Frustrating problems that don't seem to have a good solution. |
Not much, but seems a bit backward and risks missing reqs for the sake of making it testable. |
Mandated by manager |
Show
|
| 2.8 |
8 |
C |
C++, Python, VHDL |
Homemade |
I like to ride bikes and program on a raspberry pi at home. |
On-target |
Embedded MCUs |
vscode, eclipse |
1-5 minutes |
Safety Critical most of the time. Power of 10 and JSSSEH. |
It takes over a page when printed. |
I get okay feedback but we don't have the software review culture I would have expected. |
50 |
20 |
30 |
Getting something cool/complex to work. |
When something small keeps something from working and is hard to find a patch out. |
Write tests before writing a function. |
I'm looking for ways to implement tests and mock drivers on my computer. |
Show
|
| 8 |
25 |
C, C# |
C++, Python, bash, Perl, VB |
Those in Visual Studio, but just a little bit. |
25 years embedded software |
Custom test harness. |
hetero multicore SoC |
Linux tool chains |
31-60 seconds |
Ad hoc |
More than 2 pages |
Ad hoc |
5 |
0 |
15 |
Solving puzzles |
Managerial anti-patterns. |
I have good theoretical understanding, but I have not used it much. |
I am familiar with software testing but I can't talk about concepts with peers. |
Show
|
| 16 |
0 |
n/a |
I'm a quality engineer wanting to gain better understanding of software testing. |
n/a |
I have four daughters. |
n/a |
n/a |
n/a |
Under 10 seconds |
n/a |
n/a |
n/a |
n/a |
n/a |
n/a |
Wanting to learn about how the business can better control its code and develop SOP |
n/a
|
nothing |
Wanting to gain some insight testing and re-verification |
Show
|
| 7 |
5 |
C |
C#
VB
LabVIEW
Python |
Catch2
gMock |
My college major was actually biomedical engineering so I learned software on the job and at home. |
breakpoints; set up constants in code |
windows |
GitLab, Jira |
1-5 minutes |
every project is different |
when I see part of code repeat or parts I want to easily skip when debugging |
very unofficial reviews between peers |
50 |
20 |
30 |
instant feedback on my changes |
troubleshooting non software issues related to hardware |
write tests first before writing code |
My manager set up the training so she encouraged us to attend plus it sounded relevant to my work. |
Show
|
| 2 |
9 |
C/C++ |
Python, SQL, Bash, C# |
None |
drawing a blank here |
individual developers define their own Ad hoc tests unless specifics requirements are defined by the customer |
Linux |
Visual Studio Code, Sublime, other IDEs. Gitlab/Github |
11-30 seconds |
nothing formal |
It's function cant be summed up in a sentence or code from it is being repeated elsewhere |
Over the shoulder/ virtual screen share code reviews. Usually limited to a few hundred lines. |
70% |
10% |
20% |
The puzzle solving aspect. Finding a solution to the given problem and iterating on it |
Overhead work. Documentation, source control, maintenance, etc. |
unfamiliar |
Hopefully to find better and easier ways to accomplish the "boring" parts of development |
Show
|
| 3 |
5 |
c++ |
c, python, matlab |
None |
In my free time I play disc golf. |
Manual |
Just here to learn a better way to code. No current projects with target system. |
visual studio code |
11-30 seconds |
I typically just do developmental so no real standard to follow |
When a function is completing multiple tasks that should be split out into their own function. |
currently limited in current job function |
50 |
20 |
30 |
It is satisfying to get hardware working as intended |
Debugging can be difficult and time consuming and/or I write myself into an architectural corner. |
No much - excited to learn! |
I am attending the course to in hopes to learn better code architecture strategies |
Show
|
| 8 |
20 |
C# |
C, C++, Python, VHDL |
None |
I enjoy mountain sports (skiing, climbing, kayaking) and coffee! |
Creating Test Cases using the same language and IDE |
Microcontrollers (C/C++) and desktops (C#) |
Visual Studio, Spyder, Arduino |
1-5 minutes |
Depends on the project. I usually try to adhere to the industry standard for the language I'm using. |
When it can't all be viewed at once, does more than one thing, or is hard to read |
I like to circulate code, then have an in-person review. |
30 |
30 |
40 |
Software is a tool I use to solve system-level problems. ex. "How do we make these two things talk?" |
Risk and Uncertainty associated with changes. The overwhelming number of edge-cases to test. |
I understand it in the abstract, but have never applied it. |
Desire to improve quality and efficiency of testing, in order to create higher quality products. |
Show
|
| 8 |
35 |
C |
Python |
Roll-your-own |
I'm an RF engineer that spends about 75% of my time writing code. |
Combination of various ad hoc |
Embedded C on AMR M4 |
Eclipse |
Under 10 seconds |
Use my own developed over decades |
Does more than one thing, or not clear what it's doing |
Doesn't exist |
70 |
10 |
20 |
Power to do cool things |
Clunky tools, anacronyms of C |
Nothing really |
Standardize how we do testing |
Show
|
| 5 |
3 |
Python |
C, VB.net, labview |
none |
I am an electrical engineer who enjoys dabbling in software. I have 2 daughters at home, a 6 year old and a 3 month old. |
Trial and error. |
windows and linux |
visual studio code |
1-5 minutes |
no real standards for me, i try to follow pep 8 when coding in python. |
when it is trying to do too much. |
review with other engineers on the project. |
50 |
25 |
25 |
problem solving aspect. |
running into syntax errors, having to dig too deep to solve a problem. |
Write tests before you ever write a line of code. Then you write code to pass those tests. |
To learn more about test driven development, become a better programmer. |
Show
|
| 2 |
5 |
python |
C |
Unittest |
I've mostly worked on hardware teams and I was usually the only person writing hacky python code for automation. I want to get into embedded systems design and write C/C++ code that can be trusted not to break
currently learning C++ |
unittest module in python |
embedded linux devices |
vim
vscode
pycharm |
31-60 seconds |
- |
when it does too many things |
we dont do them |
40 |
20 |
40 |
I like getting things done and being depended on |
Reading codebases with no tests or documentation |
red-green-refactor |
I want to write code that doesnt embarrass me when I share it. |
Show
|
| 3 |
3 |
C# |
C, C++ |
None. |
I'm looking forward to learning about TDD. |
Functional Testing. |
WPF Apps, and Embedded STM32 Devices. |
GitHub, Jira, Microsoft Visual Studio, STM32CubeIDE |
11-30 seconds |
Internal Standard, rather basic with little hard constraints outside of formatting and naming. |
When it becomes difficult to understand with a glance and requires scrolling. |
Short pull request reviews for minor changes, and a larger system review prior to first release. |
50 |
30 |
20 |
The design and problem solving aspects. |
Rushed timelines and large amounts of minor changes. |
Not much, just that it has a large focus on test development earlier on. |
To gain some experience in an aspect of software that I have not encountered before. |
Show
|
| 11 |
30 |
C++ |
C
C# |
CppUTest
GoogleTest |
I mostly manage people and technology these days. Spend less time coding. Am taking the course with my son in HS to learn new things. |
CppUTest |
STM32xx w/ on-target tests in IAR and GCC + on-host tests w/ 32-bit windows GCC build |
IAR, GCC |
1-5 minutes |
Clang-Tidy linting + Markdown to capture manual rules + automatic formatting via Clang-Format, w/ CI |
Gut feel |
Pull request + CI automation checks |
30 |
30 |
40 |
Solving hard problems that others find too challenging/impossible to solve + planning and organizing |
long meetings |
Write a test for new use case, compile w/ coded interface (fails). Then implement to pass test. |
James convinced me it would be great for me and my team :) |
Show
|
| 5 |
20 |
C |
C++, Python, VHDL, Verilog, System Verilog |
Cppunit |
I am also a course instructor and I also write technical blogs over at embeddedrelated.com :) |
For C++ code Cppunit and using mocks for hardware drivers. For FPGA I use System Verilog with assertions to implement TDD to verify behaviours to reduce the risk of regressions when making changes. |
Almost all my projects have an FPGA and chips around them that we interface to. |
VSCode with TerosHDL for FPGA work and VSCode with C/C++ extensions for linting/code completion etc. |
1-5 minutes |
I have formulated my own coding standards based on the DO aviation standard for FPGA's. For C MISRA. |
When it handles too many behaviours. |
Generally I like to use checklists and have reviewers read standards beforehand. |
2 |
4 |
4 |
It is always a joy to see new behaviours working on a live board. |
How much time is spent trying things until it works and how brittle it often is. |
Very little, just that it can help prevent regression issues using a design for test philosophy. |
I was recommended it by Steve Branam and most recently I'm finding it could be useful for FPGA's. |
Show
|
| 2 |
5 |
C |
python |
none |
I've had little professional development around coding (outside of university) |
Test to functional specifications and ensure the device functions as intended. Additionally some longer term testing is setup but its all quite unstructured. |
Battery powered small embedded systems. Usually containing a sensor and RF |
STM IDE |
11-30 seconds |
We have a firmware standards document. |
When it is hard to follow / review |
Every pull request to a develop branch or to release goes through a pull request and is reviewed. |
20 |
50 |
30 |
The complexity and problem solving |
The repetitiveness of testing |
Nothing |
I know there is better ways of writing and testing code, however it is not done yet at work |
Show
|
| 3.5 |
3 |
Java |
C++, Bash, Python, |
Java |
I have a lovely dog who doesn't mind sleeping next to me whilst I code. |
Java unit tests. Build C++ code for some testing |
Java in a Linux environment |
IntelliJ, Qt |
31-60 seconds |
I'm still learning. Relatively junior as a software engineer. |
When it goes beyond 100 lines of code. Static analysis confirms too much cyclomatic complexity. |
Essentially non-existent, we don't have the time. |
30 |
20 |
50 |
Building something and seeing it working. Particularly seeing it provide real utility for someone. |
Never enough time. Crazy deadlines created by others. |
I hadn't heard of it until I came across your course. |
Because I won it in a competition. |
Show
|
| 2 |
6 |
python |
java |
mypy |
Dogs are great |
TDD |
n/a |
pycharm |
2-4 hours |
In python, for data processing, fairly proficient. Normally work using OOP and working to PEP8 |
It depends, but typically when reusing a code extract multiple times, or returning multiple things. |
I do them |
50 |
10 |
40 |
Building new things, building models |
testing |
Building a test first, that fails, then writing code to fulfil the test |
Mostly to learn more about embedding programming (not so much TDD) |
Show
|
| 3 |
5 |
C |
Python |
Unsure |
I am an avid baker and book reader. |
Debugging on embedded hardware |
STM32 |
STM32CubeIDE, STM32CubeProgrammer, STM32CubePowerMonitor |
Under 10 seconds |
Internal firmware standard |
When it becomes difficult to follow or contains many bugs |
Peer reviews on pull request |
40 |
10 |
50 |
Solving problems, working with logic based system |
Writing for other people's hardware, working around existing issues |
Almost nothing |
To learn better methods of coding - even if I don't agree with them, I would like to understand them |
Show
|
| 1 |
1 |
python |
Java, Javascript, C++ |
none |
A recent graduate, I am ready to hone my skills. |
Simple running and debugging the code |
I can't say for a certain |
VS Code for coding |
1-2 hours |
keeping the code maintainable, organized, and readable as much as possible as well as error handling |
Multiple lines present |
Just reading the code and test it |
20 |
30 |
50 |
Comprehensive and thorough documentation.
The programming outcomes and results |
The debugging process |
The opposite of how I test my code |
seeking to enhance my skill and knowledge |
Show
|
| 1 |
6 |
Ruby |
C, Kotlin, Python |
Unity, CppUTest
Espresso
Rspec, Nose |
I love martial arts and have trained many styles over the last 17 years |
Try to use TDD where Possible |
CN0510
https://github.com/graial/ad5940-examples-adjust-output |
cross core embedded studio (eclipse based) |
Under 10 seconds |
nil, one man team |
around 10 lines, unless its a switch |
nil, one man team |
3 |
5 |
2 |
The logical challenges |
Fighting with the initial setup of a testing toolchain |
I'm all about it |
Hoping to raise the technical standard of BSU's hardware labs |
Show
|
| 14 |
14 |
C++ |
C#, python, matlab |
Did not understand the question |
I work also as a control specialist and don't always work on software |
1. Unit testing for individual or a small set of classes
2. Integration testing in a simulated environment
3. Integration testing in a real time environment
4. System testing in a simulated environment |
Many product specific targets for simulated and real time environment |
1. C++ editor, compiler and debugger
2. Matlab / Simulink |
11-30 seconds |
Code needs to build with a C++98 compiler |
Difficult to read or understand and cannot be easily unit tested |
All pull requests to master branch must be approved by one colleague |
20% |
60% |
20% |
Usually it is possible to find out quickly whether you did an OK job or not |
Usually it is not possible to find perfect solution and need to compromise |
Often it is best to start by implementing a test case rather than start by implementing the feature |
To get some new or old ideas for testing and developing software more efficiently |
Show
|
| 5 |
9 |
C++ |
Python, C and C# |
Google test, python unittest |
I feel that we don't write that much code. In many feature that we do, we modify some existing code. I don't feel very experienced with coding and software systems. |
Unit test, manual testing with hardware, automated tests (unit tests and hw tests) |
Embedded system with ultrascale soc and different peripherals. |
Git, ide, debugger sw, confluence, build tools |
5-30 minutes |
We have a style guide which is based on Google C++ style guide. I think we have C++17, not sure. |
Hard to describe what it does or you forget what it does while checking it. |
We have code reviews when pull requests are being done. |
20% |
30% |
50% |
Problem solving, engineering, learning new, math |
Working with poorly defined requirements/user stories. |
Concept? Creating tests before coding features. |
I'm attending because my manager asked, also I'm curious to learn more. |
Show
|
| 4 |
4 |
C++ |
Python |
none |
I'm very lazy, but try very hard to not let anyone notice :) This is why I hate doing things wrong as it usually forces me to do them twice. |
Functional testing of the product |
Arm based real time control system |
VS code |
5-30 minutes |
Style guide that is based on Googles C++ style guide |
When I can't see it on my screen all at once? |
We do peer reviews (min 2) in pull requests |
5 |
15 |
15 |
Not having to reed HW standards, the power of digital control, the satisfaction of success. |
Computers, windows, technical debt, slow building/loading/feedback loops |
In practice, not much. The idea is very intriguing. |
To learn something new, to get new ideas for solving old problems, |
Show
|
| 7 |
15 |
C/C++ |
Python |
gtest/gmock, pytest |
- |
unit test, system test |
embedded |
VS Code |
5-30 minutes |
C++98 to C++17, Google C++ Style Guide derivative |
When it doesn't fit to the screen |
- |
40 |
40 |
20 |
- |
- |
Start by defining the test body how something is expected to work |
To have better tools for refactoring code |
Show
|
| 12 |
20 |
C++ |
C, Python, Matlab |
Catch, MStest |
No I won't |
Unit, systemtests, tests with realHW |
electric drive |
Visual studio/code |
1-5 minutes |
company has it's own |
When it's too long :) |
Via pull requests |
30 |
40 |
30 |
Problem solving. |
Complexity and quality of some legacy stuff |
I know the principles quite well. |
I see value in TDD, but has/is difficult with legacy stuff |
Show
|
| 4 |
4 |
cpp |
python |
google test |
I like bicycling. |
System level test. Unit tests |
Each product have a different target to compile |
meson, scons, vs code |
1-5 minutes |
google style guide, Klocwork |
When it is over 100 lines |
In each pull request a review is done. |
4 |
4 |
2 |
You can use your imagination |
Examine/Debugging others code |
You should do it more. |
In order to get better at TDD. |
Show
|
| 5 |
8 |
C++ |
C |
google test |
if get one function, how to get the start point to test it, and what kinds of stuff need to be considered |
mostly in hardware tests |
single chip / embedded device |
code IDE |
30-60 minutes |
C++ 17 |
feeling |
pull request reviewed by team member |
2 |
2 |
2 |
it can make the feature work |
a lot of stuff needs to be learned |
nothing |
want to learn the fundamental knowledge of TDD, hope it will be used in daily work |
Show
|