Well, boot camp is over and I have mixed feelings about it. On one hand I'm glad to be home, on the other I'll miss Don and class in general. What did I learn? Well, there isn't really enough time for me to sit here and expound on that subject so I'll just say that I learned more than I bargained for. After this training I see that being a programmer is more than just sitting down and hacking out lines of code. Programming is about offering a service. And anytime you offer any kind of service you have to do the following: working with people (communication is probably more important than being a senior programmer), planning (no more of this: "Okay, I've got my problem so let's see what code I can throw out there to figure it out."), and much more.
What does it take to be a good programmer and not just a programmer? Well, in school I was completely naive in this area. Given an assignment I would spend hours just staring at a blank screen hoping that the code would miracuolously type itself. Now, I think that to be a good programmer you just have to have the proper resourses (and not to mention being able to work with people). Google has become a good friend of mine recently. If I face a problem I'm not sure of how to approach then off to the WWW I go. Some students think this could border on cheating, but don't be mistaken. I'm not suggesting copying code fromt he web (cheating), I'm saying find a place you trust to give valid information about your particular subject and use it. In the real world you aren't going to know every key word or syntax, you'll have reference materials on hand for when you need them. The internet should be one of those resources.
Well, that about does it for now. I close with this:
-Forrest won the best blog award (computer Whiz to him).
-Team Ninja won last weeks programming project by the skin of our teeth, Freebirds did an awesome job on their project, we just got lucky.
-Thursday is the official first day at The Company, looking forward to that, but glad we got a break because I have got to get things organized at home before getting busy.
Until Next Time.
Les
August 29, 2005
August 23, 2005
The Freebirds ~vs~ Team Ninja
Well this week we've been split into two unique groups. We have to face off in a battle of developer wit and stamina (or maybe just development skills) and see which team can finish this weeks project first.
The Freebirds:
Kyle
Mario
Erik
Forrest
Sandeep
Team Ninja:
Ramy
John
Amanda
Nathan
me (...Les...)
Not a bad match, this should be an interesting week. We are splitting the work amongst team mates in order to work in different layers at the same time, we'll see how that goes.
Until next time.
Les
The Freebirds:
Kyle
Mario
Erik
Forrest
Sandeep
Team Ninja:
Ramy
John
Amanda
Nathan
me (...Les...)
Not a bad match, this should be an interesting week. We are splitting the work amongst team mates in order to work in different layers at the same time, we'll see how that goes.
Until next time.
Les
August 15, 2005
What a Difference a Week Makes
This past week was another week-long group project. The last time we were split into groups, we had the then daunting task of adding a few extra fields to the Create screen of our basic CRUD application. The excercise was a thoroughly challenging one, and involved adding pieces of functionality to already existing classes in the reference implementation. It was challenging enough that most of the groups (mine included) barely got the project done by deadline. Little did we know that this week's project would be twice the difficulty with the same time restrictions.
Our assignment this time around was to implement the Retrieve and Update functionalities (betcha can't guess what our next project will be...). This time, however, we didn't have the nice classes to add to, we had to create our own classes in almost every level of the architecture. Super tough. The good news is, after many, many hours of work and some gruesome battles with bogons, my partner, Ramy, and I were much more comfortable with The Company's architecture. Since we're going to be expected to extend it on a daily basis, it's good that we've been thrown into it in a training situation rather than having to mess up a real-world application that our employer relies on for its daily revenues. Our crashing through the layers came at the expense of the consultants' personal time though, because they also had to stay up here with us far later each day than they probably should have. The end result is hopefully worth it, because I think we all understand a great deal more about what goes on in the system.
This week, we're going to be learning about Enterprise Java Beans. That should be an interesting task for my part, because I have zero experience with them. I guess that's pretty much been the story about every aspect of the training for me so far, so nothing different there. Of the new things I've learned, the award for most awesome thing easily goes to taglibs and Expression Language in JSPs. I love the concept of code that reads like plain-English and accomplishes a lot in a small snippet.
Oh, and one side note about group projects. In college they seemed to be little more than excercises in futility, because you would invariably get teamed up with people who either wouldn't do any work at all, or wouldn't even show up for group meetings. In training, it's been the exact opposite. I've already had two incredibly awesome teammates that have worked very hard and that I have also learned a lot from. If this is what it's like at The Company, then I'm going to have an awesome time working there for sure.
Well, anyway, just two more weeks and we'll finally be able to head to The Company every morning instead of The Consulting Firm. That's right folks, we'll actually get a work phone number and email address, woot, woot! It's going to be really strange when we return, having been employed for almost two months and still being "the noobs." It's okay though, I can't imagine how much harder it would have been to have just been planted on a project without all of this training. Hopefully, we'll be prepared enough to step right in and contribute when we get back.
Forrest Humphrey
Our assignment this time around was to implement the Retrieve and Update functionalities (betcha can't guess what our next project will be...). This time, however, we didn't have the nice classes to add to, we had to create our own classes in almost every level of the architecture. Super tough. The good news is, after many, many hours of work and some gruesome battles with bogons, my partner, Ramy, and I were much more comfortable with The Company's architecture. Since we're going to be expected to extend it on a daily basis, it's good that we've been thrown into it in a training situation rather than having to mess up a real-world application that our employer relies on for its daily revenues. Our crashing through the layers came at the expense of the consultants' personal time though, because they also had to stay up here with us far later each day than they probably should have. The end result is hopefully worth it, because I think we all understand a great deal more about what goes on in the system.
This week, we're going to be learning about Enterprise Java Beans. That should be an interesting task for my part, because I have zero experience with them. I guess that's pretty much been the story about every aspect of the training for me so far, so nothing different there. Of the new things I've learned, the award for most awesome thing easily goes to taglibs and Expression Language in JSPs. I love the concept of code that reads like plain-English and accomplishes a lot in a small snippet.
Oh, and one side note about group projects. In college they seemed to be little more than excercises in futility, because you would invariably get teamed up with people who either wouldn't do any work at all, or wouldn't even show up for group meetings. In training, it's been the exact opposite. I've already had two incredibly awesome teammates that have worked very hard and that I have also learned a lot from. If this is what it's like at The Company, then I'm going to have an awesome time working there for sure.
Well, anyway, just two more weeks and we'll finally be able to head to The Company every morning instead of The Consulting Firm. That's right folks, we'll actually get a work phone number and email address, woot, woot! It's going to be really strange when we return, having been employed for almost two months and still being "the noobs." It's okay though, I can't imagine how much harder it would have been to have just been planted on a project without all of this training. Hopefully, we'll be prepared enough to step right in and contribute when we get back.
Forrest Humphrey
Subscribe to:
Posts (Atom)
