# Do's and Don'ts when developing First Project with Ignition? **URL:** \ **Category:** General Discussion\ **Created:** [July 23, 2024, 8:55am UTC](https://forum.inductiveautomation.com/t/dos-and-donts-when-developing-first-project-with-ignition/93592 "2024-07-23T08:55:09Z")\ **Posts on this page:** 1\ **Showing post:** 5
**Author:** ![Ryan\_Deardorff](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/ryan_deardorff/32/63815_2.png) [@Ryan\_Deardorff](https://forum.inductiveautomation.com/u/Ryan_Deardorff)\ **Post date:** [July 23, 2024, 6:13pm UTC](https://forum.inductiveautomation.com/t/dos-and-donts-when-developing-first-project-with-ignition/93592/5 "2024-07-23T18:13:21Z")
1. Bind UI input values to custom properties of the view, and reference those instead of the input value itself. It not only makes for cleaner code without a bunch of `getChild/getSibling` nonsense with hardwired component names, but ensures that you can reorganize and rename components without breaking those references. 2. Name your UI components/containers. It may seem like unnecessary effort in the short term, but in the long term it will save lots of hassle when trying to navigate your way down to a specific component. 3. Browse this forum regularly. I have learned many valuable tips just from reading responses to other people's questions. --- _[View the full topic](https://forum.inductiveautomation.com/t/dos-and-donts-when-developing-first-project-with-ignition/93592)._