[rkangel]

I split activities at work into "Engineering" and "Talking about Engineering". We're a consultancy so there's a certain amount of "Talking about Engineering" that is required and good, but I try not to lose sight of what is actually engineering and what isn't.

What I am still on the fence about is when "design" or "architecture" type work counts as Engineering. There's a certain amount of design work that is valuable to do before coding and is part of the thinking process. But sometimes you get into a lot of abstract talking that is "not doing the thing".