4 ms·
Good enough is a struggle... but the one thing that should never be pushed down the pipe is ensuring the code is understandable. Once you get beyond the basic
by columbo 14y ago
Good enough is a struggle... but the one thing that should never be pushed down the pipe is ensuring the code is understandable.
Once you get beyond the basic crud-webapp-twitter-clone the ability for a new person to simply pick up and start working becomes increasingly more difficult. This is a cost that you will pay. You'll pay for it when one of the three people that understand the system decide to quit or when you have to put new hires through eight months of training before they can write a single line of code.
I've worked with systems that were written by people that have decades of industry knowledge. Every class, method and comment is using their lexicon and entire chunks of the system rely on assumed knowledge. Suddenly ranked_pct(std_dev_norm(userid,norm,v,arr,false,get_data(userid))) is returning 0.24 when it used to return 0.51 and the BA/PM would like to know what changed. That's when you'll realize that your growth has been severely limited.
- hanzq 14y agoThat code blip sends a shiver up my spine. My previous code shop maintained a fairly large rails base and we mitigated that risk by doing as many things "the rails way" as possible, even if it took more time than some ruby hack. When you consider how quickly new hires could pick up the project, it easily outweighed the extra effort designing code in a well-understood format.