| You were coding for 15 years when I started coding. Still excited, but oh, didn't think that I can get bored. Anyways, I keep myself excited between 2 fronts. Officially I'm sysadmin, but programming is just a coincidental skill that I apply starting from automation to the point where stuff gets built from ground up. Probably excited because within sysadmin+programming world there is so much to learn. Only now getting the skills to debug .net 3rd party sofware, uh, that's so interesting. Lots of internals to learn. Getting to know embedded world is also something interesting which I'm now only barely touching. I have no knowledge but would find it interesting if I could know electrical engineering. Understand, fix and build stuff at that level seems exciting. Maybe someday. I have had to build knowledge from high-level stuff to low level stuff. For you perhaps it was other way around? I think that high-level stuff was probably easyer/complementary to low-pevel knowledge, which gets you further much faster. I don't mean by developing a solution, but understanding systems, problem space and solution. Ofcourse I'v thought about which I like more: sysadmin or programming tasks. Both get me excited. And then I thought if I'd be doing only one of them, probably I would be less excited. Perhaps apply your knowledge to some different problem domain? I have this dream maybe someday I can build stuff for agriculture (whatever helps grow something). Be out on the field to see what I have to do and then test, improve it. Well, the other half says me the reality probably is a bit different - sit in the office 95% of time, and maybe the rest eith some real stuff. Dunno. Ohwell, that's just some wild dream. |