Strategy is more about planning, architecture, knowing about the real pros and cons of different solutions eg. libs, tools or languages.
Strategy is more about planning, architecture, knowing about the real pros and cons of different solutions eg. libs, tools or languages.
So debugging, no, definitely not. I can spot root-causes of bugs now even easier than I used to be able to.
And one of the big new skills is that I'm much more able to 'guess' where a bug is in someone else's totally new code-base than I previously was able to.
In fact, I also write code faster as I get the general gist of it done much faster first time.
For instance, I used to be able to perftune UNIX and DB (mostly Oracle on Solaris) pretty well, knowing various kernel parameters by heart and all the tools of the day (tkprof, Cockroft and co). Now I guess I could still get by after some brush-up, but I'm not anywhere near as efficient as I used to be on that specific task. And I still write code, but I don't know every single method of every API anymore. But now, I can design full solutions, from choosing the hardware to setting up platform, languages, monitoring, high-availability, backups, security etc. Not because I'm smarter, but because I've been exposed to all that along the years.