When I'm building out new HTML UI elements, I often add {{data}} to a page to get a rendering of the data I'm working with (using Selmer for HTML templates), so it's nice to see it crop up here and be given a name.
Although I agree with your indication of the synthetic approach being more akin to the Cynefin's Complicated domain, I would be very careful to place the activity of building software somewhere other than the Complex domain, because even when we apply more formal methods to design and understand the domain (if I understood correctly your explanation of the synthetic approach), building software will always be a creative process where we don't necessarily know how we'll get there before actually doing it, and in many cases we learn new things after collecting feedback on our implementation. Thus "Best Practices" has no place in the "probe, sense and respond" approach of the Complex realm.
When I'm building out new HTML UI elements, I often add {{data}} to a page to get a rendering of the data I'm working with (using Selmer for HTML templates), so it's nice to see it crop up here and be given a name.
Although I agree with your indication of the synthetic approach being more akin to the Cynefin's Complicated domain, I would be very careful to place the activity of building software somewhere other than the Complex domain, because even when we apply more formal methods to design and understand the domain (if I understood correctly your explanation of the synthetic approach), building software will always be a creative process where we don't necessarily know how we'll get there before actually doing it, and in many cases we learn new things after collecting feedback on our implementation. Thus "Best Practices" has no place in the "probe, sense and respond" approach of the Complex realm.