201–210 of 220 posts
[0] Please just let this slide.
I get the thrust of this; it's to help Virgos[0] stop procrastinating by over-preparing. But you do need some minimal level of preparation. So declaring that preparing to do a thing isn't doing the thing becomes almost a tautology, or a meaningless question of what the words mean in the dictionary. [0] Please just let this slide.
Earlier quoted context omitted.
Certainly, but don't get confused: You are not doing the thing, until you do the thing. There are many ways to do the thing. There are many more ways to not do the thing.
That's right, you're not producing paperclips unless one minute you have metal wire and the next minute you have a paperclip.
I'm inspired by this and want to extend it, perhaps telescopically, by discussing what the thing is. Sometimes we see our task as being, "do C," and we forget the "B" and "A" that come before. Maybe you can't do "C" without discussing it ("B") or researching how others did it ("A"). In these cases, we shouldn't simply think the thing is "C"—the thing must first be "A," then "B," and then, "C." If we forget this, we'r…
It's easy to underestimate that groundwork because it's less flashy or quantifiable. But skipping it usually just means C turns out half-baked, or takes even longer in the end
Just yesterday I was helping a family member install roofing. The roof was done up to slats, the roofing was big metal sheets, should be done in an hour. Except we spent good five hours on various little details before the first sheet was going up. And you cant exactly not do those, at least if you want the roof to stay there, and the weather to stay outside.
Wow this article is an amazing rorschach test! Each defensive comment here is a person defending what he thinks this article is personally attacking him on!
Earlier quoted context omitted.
Certainly, but don't get confused: You are not doing the thing, until you do the thing. There are many ways to do the thing. There are many more ways to not do the thing.
Au contraire! Almost all the time you spend doing the thing is actually doing the things required before the final completion of the thing. I've taken to calling this "the work before the work" and it's at least 90% of the work. Example: I get asked at the start of a project to provide ModbusTCP comms mapping for a new control panel, so that the client can start integrating it into their SCADA system. It's just a spr…
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.
Wow this article is an amazing rorschach test! Each defensive comment here is a person defending what he thinks this article is personally attacking him on!
What you see as defensiveness, I see as reasonable replies to a very silly faux-inspirational post.
Exaggeration is a common technique employed in human language for emphasis.
Earlier quoted context omitted.
What you see as defensiveness, I see as reasonable replies to a very silly faux-inspirational post.
Have you considered the idea that it is just exaggerating to make a point and isn’t meant to be taken literally? Exaggeration is a common technique employed in human language for emphasis.
Wow this article is an amazing rorschach test! Each defensive comment here is a person defending what he thinks this article is personally attacking him on!
Earlier quoted context omitted.
Au contraire! Almost all the time you spend doing the thing is actually doing the things required before the final completion of the thing. I've taken to calling this "the work before the work" and it's at least 90% of the work. Example: I get asked at the start of a project to provide ModbusTCP comms mapping for a new control panel, so that the client can start integrating it into their SCADA system. It's just a spr…
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 t…
Ah dammit I always forget the flabnabber.
10/10 authentic embedded development experience.