That seems wrong to me. I personally use visualization frequently during development and not having that ability seems to me a massive hinderance.
I don't even understand how you can begin to plan a user interface without the power of visualisation. I suppose you just have to produce drafts? I can just lie there in bed and iterate for hours, imaging how the user will move through processes, etc. It seems a huge disadvantage to only be able to develop such an idea while actually having the interface in front of you. Maybe this is the real reason some developers never want to leave the back end :)
I feel like even planning architectural code is somewhat visual for me, like I have a mental model of the folder structures and how different components of the system relate to each other.
Comments
That seems wrong to me. I personally use visualization frequently during development and not having that ability seems to me a massive hinderance.
I don't even understand how you can begin to plan a user interface without the power of visualisation. I suppose you just have to produce drafts? I can just lie there in bed and iterate for hours, imaging how the user will move through processes, etc. It seems a huge disadvantage to only be able to develop such an idea while actually having the interface in front of you. Maybe this is the real reason some developers never want to leave the back end :)
I feel like even planning architectural code is somewhat visual for me, like I have a mental model of the folder structures and how different components of the system relate to each other.