[swift-evolution] Should we consider Swift improvements for indie solo programmers?

Marc Knaup marc at knaup.koeln
Sat Dec 12 08:04:20 CST 2015

Even when not working in teams developers should maintain a good code
structure & practices.

   - They may revisit the code after a long time has passed and then need
   to understand it again.
   - They may join a team some day and then carry over the the
   bad/"non-optimal" practices over.
   - Many developers start learning programming or a new language in solo
   projects. They should learn a language along with good practices.
   - They tend to underestimate that quick & dirty coding causes technical
   debt over time and will some day bite them.

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".

On Sat, Dec 12, 2015 at 2:54 PM, Amir Michail via swift-evolution <
swift-evolution at swift.org> wrote:

> Unlike those working in teams, indie solo programmers may be happy with
> some non-optimal coding practices (e.g., very long methods, etc.)
> Should we consider improvements to Swift that are of interest mostly to
> indie solo programmers (e.g., optional “} /for”, etc.)?
> _______________________________________________
> swift-evolution mailing list
> swift-evolution at swift.org
> https://lists.swift.org/mailman/listinfo/swift-evolution
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.swift.org/pipermail/swift-evolution/attachments/20151212/15bc7a33/attachment.html>

More information about the swift-evolution mailing list