3 ms·
Yeah, it could just be me, but I prefer to make two false starts, toss them, and then get it right on the third attempt rather than attempting to whiteboard the
by JKCalhoun 5y ago
Yeah, it could just be me, but I prefer to make two false starts, toss them, and then get it right on the third attempt rather than attempting to whiteboard the problem for two weeks.
Not only is it more interesting to me to try three different ways to tackle a problem, but I have been burned when the two weeks of whiteboarding missed something and I'm back to having to iterate anyway.
To be sure, I do a little whiteboarding, but generally it might be about 2 hours or so of sketching out ideas, major structures, code flow ideas.
I generally was nodding along to most of the author's points though.
I definitely have grown to divorce myself from my ego and always try to not only try to shine the spotlight on my younger coworkers (new engineers) but try to give them "ownership" of key pieces to allow them not only some sense of autonomy/ownership but a sense of pride as well.
That does go slightly against some of the author's points about collaboratively working on a project. Engineers need a part of the code (let's say an image cache manager, as an example) that they can "own" though in order to grow. You don't want an engineer to always have "training wheels" on. (And frankly, I think this is one of the things I dislike about code reviews, I think it dis-incentivises autonomy.)
The team though, let me be clear, is the most important part of any project, not the individual luminaries. The "team" though, to a degree, needs to have engineers who feel an ownership stake in pieces of the product.
(FWIW, I have probably 35 years of programming experience, ha ha.)
- Palomides 5y agoI forget where I read this, but something like: first time to understand the problem second time to understand the solution third time to do it right
- spikej 5y agoI take the original text as "don't just jump into coding right away" which I've seen so many people do. As you said, take a little bit to process and think through it, then start out your pseudocode, etc.
- pklausler 5y agoYou shouldn't try to code a complete top-down solution without fully understanding the problem. (And how often do you fully understand the problem, or think that you do but don't?) But you can code up a bottom-up partial solution of the parts of the problem that you do fully understand, and in the process learn enough to make progress on the total solution, so long as the components you develop in the bottom-up process are composable and robust.
- polishdude20 5y agoThere was recently a thing I worked on where there were multiple similar things that needed to be done. Rather than finishing the beginning of A and then the beginning of B and then C, I opted to finish ALL of A then all of B then all of C. This way, what I learned when working on all of A, I could use to make better decisions about the beginning of B. Then what I learn from doing all of B would be used to help make the beginning of C even better. If I did all the beginnings first, I'd then go back to doing the middle of A and realize I did the beginning wrong and have to go back to fix the beginnings of B and C.
- mandevil 5y agoFred Brooks' other famous bit (besides the "mythical man month"): "You should plan to throw one away. You will anyway."