<div dir="ltr">Even when not working in teams developers should maintain a good code structure & practices.<div><ul><li>They may revisit the code after a long time has passed and then need to understand it again.<br></li><li>They may join a team some day and then carry over the the bad/"non-optimal" practices over.<br></li><li>Many developers start learning programming or a new language in solo projects. They should learn a language along with good practices.</li><li>They tend to underestimate that quick & dirty coding causes technical debt over time and will some day bite them.</li></ul><div>Also if they really do not want to follow good practices then there's no need for something like "} /for". They could just use "} // for".</div></div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Sat, Dec 12, 2015 at 2:54 PM, Amir Michail via swift-evolution <span dir="ltr"><<a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Unlike those working in teams, indie solo programmers may be happy with some non-optimal coding practices (e.g., very long methods, etc.)<br>
<br>
Should we consider improvements to Swift that are of interest mostly to indie solo programmers (e.g., optional “} /for”, etc.)?<br>
<br>
_______________________________________________<br>
swift-evolution mailing list<br>
<a href="mailto:swift-evolution@swift.org">swift-evolution@swift.org</a><br>
<a href="https://lists.swift.org/mailman/listinfo/swift-evolution" rel="noreferrer" target="_blank">https://lists.swift.org/mailman/listinfo/swift-evolution</a><br>
</blockquote></div><br></div>