Great Developer Habits

Posted by Daniel Vela on June 23, 2020

Great Developer Habits

Great Developer Habits - WWDC 2019

Successful app development requires mastering a lot of different things. Discover practices you can incorporate into your development workflow to enhance your productivity, and improve your app’s performance and stability. Learn how to improve the quality of code you write with Xcode. Gain a practical understanding of some valuable development techniques.


  • Organize
    • Use groups in Xcode to organize everything: functionally
    • Match groups with file system.
    • Storyboards: use several using links.
    • Keep up-to-date project configuration.
    • Remove scrap code.
    • Remove warnings.
  • Track
    • Use source control.
    • Commits small, localize and self-contained.
    • Write usefull comments messages.
    • Use branches for bugs and feature work.
  • Document
    • It’s important to describe the why the code is written. Document it. Comments are criticial for future understanding.
    • A good comment explains the why. Good comments provide background and reasoning.
    • Use Command+option+/ to add a funtion or class commentary. Use descriptive variable and constant names.
    • Include documentation.
  • Test
    • Write unit tests.
    • Run unit tests before commiting code.
    • Build a foundation for continuous integration.
  • Analyze
    • Simulate poor networks with Network Link Conditioner.
    • Use sanitizers and checkers.
    • Measure performance and efficiency with Debug Gauges.
    • Investigate issues with Intruments.
  • Evaluate
    • Include code review as part of your practice.
    • Understand each line.
    • Build it.
    • Run tests.
  • Decouple
    • Determine functional segments and break them out.
    • Scale your work across multiple apps.
    • Improve efficiency with extensions.
    • Share your efforts with the broader community.
  • Manage
    • Use community and open source projects responsability.
    • Understand dependencies thoroughly.
    • Ensure that privacy is respected.
    • Have a plan if a dependency goes away or is no longer maintained.