Please log in to watch this conference skillscast.
You will explore how to combine a number of techniques which you have already encountered separately, plus at least one technique you have never heard of and can use immediately. Naming and abstraction are too hard to get right every single time, so you need to know when to add small doses of comments and documentation. More importantly, you need to know how to avoid wasting time on bad comments and unnecessary documentation without giving up entirely and not having any at all.
After the excitement of early adoption, and the joy of coding among experts comes the horror of your first Scala maintenance project. As Jean-Paul Sartre said*, ‘Hell is other people’s code’. Whether you are a new Scala developer or an experienced team lead, your future developer experience and happiness depends on maintainable code.
The Call for Papers is now open for Scala eXchange 2017! Submit your talk for the chance to join a stellar line-up of experts on stage. Find out more.
YOU MAY ALSO LIKE:
- How to Name Things: The Hardest Problem in Programming (SkillsCast recorded in December 2017)
- Modern Software Architecture Documentation Hands On — Half‑Day Workshop [SAG Digital 2021] (Online Course on 12th October 2021)
- Akka Streams for Scala | ScalaCon Workshop (Online Course on 25th - 27th October 2021)
- ScalaCon 2021: November Edition (Online Conference on 2nd - 5th November 2021)
- Team Identity and its Impact on an Organisation (Online Meetup on 3rd August 2021)
- Dynamic Reteaming (SkillsCast recorded in July 2021)
- Formal Verification of Subsets of the Rust Language (SkillsCast recorded in June 2021)
How to write maintainable Scala code - Beginner
Peter Hilton is a software developer, writer, speaker, trainer, and amateur musician. His professional interests are business process management, web application development, functional design, agile software development and documentation. Peter currently consults for Signavio in Berlin, remotely from Rotterdam where he has lived since January 2000. Peter regularly presents at developer conferences and provides the occasional training course.