4 ms·
How much to optimize for the reader versus writer depends on context. In my daily work on a mature system I completely agree I should optimize for readers: the
by jefftk 5y ago
How much to optimize for the reader versus writer depends on context. In my daily work on a mature system I completely agree I should optimize for readers: the things I'm writing will likely last a long time, during which many people will work on them.
On the other hand, there are other contexts such as research or prototyping where it's much more important to get things out quickly; turn your ideas into code so you can see how they work.
- silisili 5y agoIt's a common excuse in any place...we just need an MVP. I guess my wish is that the language du jour was one that made things harder for the writer and easy to read. The only reason people seek shortcuts is because they exist.
- Zababa 5y ago> I guess my wish is that the language du jour was one that made things harder for the writer and easy to read. This has been the trend for a few years with static typing being added to every language.
- unionpivo 5y ago> It's a common excuse in any place...we just need an MVP. Software projects are more than just code. Getting MVP out in 2 Months instead of 3 or 4 that it would take to do it properly, could doom the project. And I am not just talking about startups. I am talking about project at big slow moving enterprises. Getting somethin that the client can see, is one of the most important milestones. Sometimes that means that you will need to do a lot of cleanup, after first mvp, and sometimes yes it stays in sad state. But the alternative often is not better project, but project that got canceled/failed before first release. There are times that you want to go fast, and times that you want to take your time and do it properly.