You make a good point about dealing with idiot-users and Windows. What route did you take to get to where you are today? Doing something in development greatly interests me.
Edit: Not trying to steal the thread from the OP, just curious about AE7's path to where he is today.
You make a good point about dealing with idiot-users and Windows. What route did you take to get to where you are today? Doing something in development greatly interests me.
Edit: Not trying to steal the thread from the OP, just curious about AE7's path to where he is today.
I'll try to give you a timeline. I started out in high school just like everyone else, building my own PCs, messing around with hardware, helping people out with problems, etc. I took a computer science class in high school during my senior year; it was all Java, nothing more. It was okay, I didn't much care for Java, probably because I was too immature at the time and I didn't really have a strong background.
The more I look back on it, Java is a bad language to start with-it makes for lazy programmers, because of the Java Class Library. Beginner programmers have all these shiny, new Java toys, and don't know how any of them work, when knowing how they work is the name of the game. It's best to start with C++. Sorry, that's me rambling about...
Later in my senior year, I took another course that was based around the A+ and Cisco Networking Academy. This was a breeze, I was asked to compete for the school. I got a little bit of recognition, and the school offered to pay for my A+ certification and two other guys' if I made it to the state competition. I got second in the state competition, got my A+ for free, and had my name in newspapers for a little while.
A family friend from the past had been reading the newspapers, and had heard my name. This family friend had scored a six-figure job, and was looking for another IT staff member in the department. She found me, sent a business card my way, asking that I call her. I made the call a few weeks before I graduated high school, and arranged an interview. I got the job before I graduated, and started working.
The job was mainly a support role, which was fun for ~4 months. Then our network needed an upgrade, and we needed server infrastructure bad. So I changed things around to start working on that. That got annoying fast, the 50 year old network engineers and security people don't like to let somebody less than half their age tell them that a server needs a public IP and needs to be put in the DMZ. I got frustrated, luckily we have two Internet connections, I took the unused connection and made it my own. Network engineers are also stingy with SSL certificates, I later found out.
After that mess, I started getting questions about building business intelligence systems, just to see how many visitors came through our place. So I put some stuff together, event management systems and such. I made everything to be a web application, because it could be accessible from anywhere without a VPN. It could be just as secure using a relatively low amount of code and SSL.
I still support users, but I have a supervisor who likes doing that sort of thing. It makes life easier on me, but the supervisor can't code or use anything outside of Windows.
I started college at some point in there, I am a Computer Engineering major going into my 3rd year. It has been fun and as my department grows, there's always a need for a new system. I think the department enjoys having a developer, too. Rather than paying out $10,000 for a system, they can have me custom build something for cheaper, and cut out the extra fluff that we won't use. Plus, a new custom system can tie in with other custom systems. Depending on the project scope, it takes me around a week to turn a prototype using Python or PHP.