3 ms·
> I’ve also learned to write code in a way that reduces cognitive load so that interruptions aren’t so disruptive to my productivity. Have you figured out how
by hinkley 5y ago
> I’ve also learned to write code in a way that reduces cognitive load so that interruptions aren’t so disruptive to my productivity.
Have you figured out how to explain this to others? Some people don’t seem to get why their amazing code is more of a dumpster fire.
- BurningFrog 5y agoNot OP, but much of it boils down to partition the work into smaller, simpler chunks. So if you do lose all your context when QA has a nerf war, you haven't lost much.
- twodave 5y agoI’m in the process of designing talks outlining the general architecture of the platform my team has spent the last few years building. Minimizing cognitive load is a guiding principle of ours (and for our platform—payroll processing—it’s a necessity).
- d0mine 5y agoIt is BS -- you can't split some work into smaller parts. If you interrupt pregnancy at 3 months, you likely won't get a baby in 6. Deep work may take time.
- hinkley 5y agoI don't believe it. Most of the most complex code I have found, when I needle the author about it, it turns out they don't really understand it either. It genuinely seems to me that the Feynman Hypothesis holds true: If you can't explain it simply, then we don't really understand it. And for certain if you can't explain the code simply, there's no way to make the code simple.
- d0mine 5y agoDeep work is not about producing complex code. The result is most likely the opposite: it is a hard work, to make something look simple. The term "deep work" is from here https://www.calnewport.com/blog/2012/11/21/knowledge-workers-are-bad-at-working-and-heres-what-to-do-about-it/ https://www.calnewport.com/blog/2012/11/21/knowledge-workers...