Comment by verall
2 months ago
Yes in all the environments I've been in this is nearly the entire job. But I work in embedded...
Need to verify feature X - okay, let me just -
- Find the list of CPs needed
- Get a recent source tree
- Acquire a board
- Flash board
- Get CPs
- Manually assign IP and bring up SSHD to the device so I'm not working over serial
- Build and SCP the rebuilt thing to the device
- Find whatever byzantine command you need to run it to verify it
- Of course it doesn't work, ask your coworker
- Oh did you remember to flub the flabnabber? echo "1" > /dev/i2c5 then restart the flabnabber-daemon
- Run the fking thing and it works
- 3 hours has passed
Wow is working in embedded great. But I think that this is basically everything. The time isn't building the shelf, it's figuring out exactly which hinges are right for what I want it to do, it's measuring and measuring and sanding, it's multiple runs to home depot.
ALL of this _is_ "doing the thing". They are all prerequisites and as such are part of the task.
> - Oh did you remember to flub the flabnabber? echo "1" > /dev/i2c5 then restart the flabnabber-daemon
Ah dammit I always forget the flabnabber.
10/10 authentic embedded development experience.
> $ echo "1" > /dev/i2c5
Permission denied.
> $ sudo bash -c 'echo "1" > /dev/i2c5'
I forget every time