3 ms·
Just because you're smart and in the front lines, that doesn't mean you _need_ to take the complex route every time. It takes skill to do things the simple way,
by theshrike79 5y ago
Just because you're smart and in the front lines, that doesn't mean you _need_ to take the complex route every time. It takes skill to do things the simple way, to know when you just need to get shit done and when you can/need to be fancy.
Let's say I want a fence for my yard.
The newbie carpenter wants to show off their skills and makes the most beautiful delicate lattice work with intricate fibonacci patterns.
An experienced carpenter sees that I have 4 huge dogs and determines that I need a sturdy fence, not a fancy one.
This is the way I do things at work:
1) Make it work
2) Make it fast
3) Make it pretty
It doesn't matter if you've got the fastest code and the most elegant one-line lambda functions and the most expressive code if it doesn't work first.
First you make the simple and boring solution, the one that works. Then you see if it needs to be faster, most times it doesn't. After that, if you have time, you can spend time making the simple code prettier, more elegant and expressive.
In 99% of the cases I don't need to go past step 1, the simple solution works just fine.
- TeMPOraL 5y agoOf course. But I disagree with the general sentiment that "clever = fancy", or "a junior may have not seen this technique before" = "fancy" = "bad". A lot of "advanced" techniques and features of tooling exists because they enable simpler code. Simpler, in the sense of better expressing intent, more readable, less bug-prone. For example, a map-reduce on a sequence will typically be simpler than an explicit loop - because it expresses only the things that matter, whereas an explicit for loop also emphasizes irrelevant details and provide opportunities to introduce bugs. And yet, a random junior is going to consider the latter to be "simpler" - but that's only because they're unfamiliar with more advanced programming concepts. The solution to that isn't to abandon advanced concepts - it's to teach the junior to work with them. > The newbie carpenter wants to show off their skills and makes the most beautiful delicate lattice work with intricate fibonacci patterns. Maybe. Regardless, the newbie carpenter will be identified by doing more work than necessary, using less sophisticated tools and techniques. The experienced carpenter will show up with a richer set of tools, and perhaps apply some non-standard technique to put it up and secure against your dogs. He'll be done faster, and tire themselves less. > Make it work / Make it fast / Make it pretty Yes, this is a good approach, and I'd say programming experience manifests itself in the following ways: - A richer set of tools allows an experienced programmer to get the thing to work faster. - Their experience allows them to simultaneously also make the code somewhat fast and somewhat pretty, because quite often, making things fast and pretty requires the same amount of effort as slow and ugly, if you have some experience to help you make the right choices. - An experienced professional will not habitually stop after the "make it work" phase, unless made so by high deadline pressure.