How do I Architect Solutions Better
How do I start Architecting Solutions from the outside in, instead from the code out?
I feel that my biggest weakness currently is that I have to get in the code to understand a problem, and then figure out the solution as I go. Luckily, I'm fast and can churn out code. However, I feel like that my whole approach is fail fast, and pivot. It mitigates analysis paralysis but creates a lot of repetitive work as I work through the problem.
My current logic system for creating solutions is OK, but it wastes cycles as I uncover consequences as my solution shapes up. It appears to me that I should be able to look from the outside, think about a solution and its implications, and then write the code to implement after some careful deliberation.
Of course, things will come up, I won't be able to think about everything. I do wish I could Architect better though. One of the problems is I have never met a good Architect to absorb their thought process so I'm winging it.
Any personal philosophies, books, anecdotes would be appreciated.