When I make something, I want all and just the relevant pieces of what I am doing in my face, and then I want them gone when I do the next task. So if I were t

When I make something, I want all and just the relevant pieces of what I am doing in my face, and then I want them gone when I do the next task. So if I were to every try to design a page, I want all the relevant design items there when I am figuring it out, and then when I am done, I don't want to see them again. So if you spend a lot of time designing the html/css then this approach makes sense. I don't want to jump into the css file and then back in the html file. However, if I want a particular look and feel for a site, and then knock out the css, then I want the css in a different file and then I want to focus on the layout and the logic. So my guess is that the original author builds lots of new sites and moves on. My guess is that the original author does not build one large site for a large company that has a consistent look and feel for years (till the rebrand).