theWold

I like large obtuse processes. I making a living using Java, and helping make a process. I 'enjoy' when business wants to take the world me and my coworkers have made and 'change all the rules' (Sometimes this doesn't need to happen other times I do agree that change does need to happen). I'm on my second year post college and still love it as much as my first internship between my freshman and sophomore year.

My weakest area is SQL and I am getting help through a more senior engineer and a DBA (who I occasionally bribe with a Coke for his help). I am continuing my interest in Java, Drools/Fico Blaze (Rules Engines), and I am also learning about Apache2 and Splunk right now and other more enterprise-y technologies. I am continuing being part of conversations with senior engineers and starting to help with driving intent with business and other engineers.

What do y'all think would be some good advice for someone in the early stages in their software life?