> When I try to build something new, I find myself instantly criticizing my technique, to the point of paralysis. This function is hard to test; this object's dependencies need to be injected rather than initialized internally; that module needs an integration test; and so on and so forth. Even when writing spike or proof of concept code, I find myself revisiting the same lines over and over again, looking for the be…
No. It has to be clean, correct, and come with full unit test coverage the first time. You have until the next sprint to implement it. Your workspace is a Macintosh at a long desk where you'll be working shoulder to shoulder with other devs working on other projects. If you can't manage even that, you're just not a good fit for our company; we expected more of an engineer of your experience level. Based on a true sto…
I'm a good engineer but I suck at building stuff
71–80 of 128 posts
Re: I'm a good engineer but I suck at building stuff
#72> When I try to build something new, I find myself instantly criticizing my technique, to the point of paralysis. This function is hard to test; this object's dependencies need to be injected rather than initialized internally; that module needs an integration test; and so on and so forth. Even when writing spike or proof of concept code, I find myself revisiting the same lines over and over again, looking for the be…
No. It has to be clean, correct, and come with full unit test coverage the first time. You have until the next sprint to implement it. Your workspace is a Macintosh at a long desk where you'll be working shoulder to shoulder with other devs working on other projects. If you can't manage even that, you're just not a good fit for our company; we expected more of an engineer of your experience level. Based on a true sto…
Re: I'm a good engineer but I suck at building stuff
#73Here's a priority list that you should typically follow for making anything. 1. Make it work. 2. Make it not break. 3. Make it fast. That's it really. Until the performance of something is blocking what you need to do somewhere else leave it the hell alone.
Per (as far as I can tell) the original: http://c2.com/cgi/wiki?MakeItWorkMakeItRightMakeItFast 1. Make it work. 2. Make it right. 3. Make it fast.
Re: I'm a good engineer but I suck at building stuff
#74Earlier quoted context omitted.
4. Make it manageable.
I'd probably swap them: 1. Make it work. 2. Make it not break. 3. Make it manageable. 4. Make it fast. Otherwise I find that trying to make something fast before making it manageable usually ends up in crazy hacks that are hard to undo later.
Re: I'm a good engineer but I suck at building stuff
#75I'm good at building stuff, but I'm not a great engineer (I'm ok, but others on my team are way better).
Not to say I don't have my strengths. I'm good at figuring out what to build and the general architecture of how to get it done quickly and working well.
But when it really comes time to scale and scale big, you don't want me coding. You want me looking at the next features etc. etc.
If you love getting into the nitty-gritty of high quality beautifully considered easy to work with code, why do you feel you should focus on 'building stuff'?
Personally, I think focusing on your strength (not to completely ignore building stuff) can be a huge benefit.
Re: I'm a good engineer but I suck at building stuff
#76> When I try to build something new, I find myself instantly criticizing my technique, to the point of paralysis. This function is hard to test; this object's dependencies need to be injected rather than initialized internally; that module needs an integration test; and so on and so forth. Even when writing spike or proof of concept code, I find myself revisiting the same lines over and over again, looking for the be…
No. It has to be clean, correct, and come with full unit test coverage the first time. You have until the next sprint to implement it. Your workspace is a Macintosh at a long desk where you'll be working shoulder to shoulder with other devs working on other projects. If you can't manage even that, you're just not a good fit for our company; we expected more of an engineer of your experience level. Based on a true sto…
Re: I'm a good engineer but I suck at building stuff
#77Here's a priority list that you should typically follow for making anything. 1. Make it work. 2. Make it not break. 3. Make it fast. That's it really. Until the performance of something is blocking what you need to do somewhere else leave it the hell alone.
1) Make it work
2) Make it work better
3) Make it work cheap
Re: I'm a good engineer but I suck at building stuff
#78"He who rests while other people work with their heads, hands, and hearts is a capitalist".
Makes people mad, but it's true. People who rest and reap profits orders of magnitude above those who work, due only to the fact that they hold capital, are leeches on society.
The societies that have gotten rid of the capitalists haven't made life better for the rest.
Re: I'm a good engineer but I suck at building stuff
#79"He who rests while other people work with their heads, hands, and hearts is a capitalist".