How to apply coding methodologies and practices to non-coding work?
- by Dan
I can talk for hours about best-practice, source control, change management, feature tracking, development cycles and the lot, but most of what I've learnt or read seems to apply to nuts-and-bolts programming of compiled applications. You know, ASCII files that gets turned into 1s and 0s.
How does one apply the same discipline and wisdom to working in environments that are point-and-click, config-centric. I'm thinking of CMSs and specifically, my current 9 to 5, SharePoint.
Traditional practices of source control, dev-staging-production seem to break down since we're not working with code, and the live environment changes with user input.
So to sum up a rather lengthy question, what works in a no-code environment?
