Ni is more about the concept as opposed to the detail. So expanding on the concept will be much different then expanding on the detail. I work with an ENTP and he really likes to dig into the detail, while I enjoy digging into the concept. He made a comment one time about me basically rewriting a framework because I dissected it, figured out the concept and shifted that concept over to what we were doing. He would find the details of the framework and bring it into our project as a whole. For him our project is designed of patterns and frameworks, to me I build the framework off of understanding the concepts of other frameworks. We work completely different. I will understand what we are doing and create the concept and piece together the details as I work in a very sloppy approach that I streamline and rewrite as I go. Alot of rewriting, debugging, logging, etc. Kinda like you sloppily painting the details and restructuring on the fly. I lose pretty much everyone if they watch me work as I bounce around. My code ends up with alot of fail overs where I seperate paths at key points and I kinda create switches to move between the paths, eventually killing off the old path and using the new improved path. Is this what NFPs do with NeFiTe? Like an internal rewiring, that affects things externally as well.
This is different then what I was thinking of when I said lazy Te. I was referring to just accepting "groupings" as truth. More like a static framework as justification. Maybe this is just a part of sloppy. I dont know.
Completely lost yet?