Path 2 Developer

So, I don't have much, but I do have some. Behold my genius code for my hours calculation:     Private Sub btnCalculate_Click(sender As Object, e As EventArgs) Handles btnCalculate.Click         Dim s1 As Integer         Dim s2 As Integer         Dim s3 As Integer         Dim s4 As Integer         s1 = Val(txtTimeInSunday.Text)         s2 = Val(txtTimeOutLunchSunday.Text)         s3 = Val(txtTimeInLunchSunday.Text)         s4 = Val(txtTimeOutSunday.Text)         lblSundayHoursTotal.Text = s4 - s1 - (s3 - s2)         Dim m1 As Integer         Dim m2 As Integer         Dim m3 As Integer         Dim m4 As Integer         s1 = Val(txtTimeInMonday.Text)         s2 = Val(txtTimeOutLunchMonday.Text)         s3 = Val(txtTimeInLunchMonday.Text)         s4 = Val(txtTimeOutMonday.Text)         lblMondayHoursTotal.Text = m4 - m1 - (m3 - m2)         Dim t1 As Integer         Dim t2 As Integer         Dim t3 As Integer         Dim t4 As Integer         s1 = Val(txtTime

I've learned a big part of development since I've been a part of this team. We have meetings. Some seem long-winded, some seem unnecessary at times, but I've gotten something from all of them in every case. There's a lot of communication involved in this role. I focused on a lot of technical, but there are many soft skills involved to make it successful. Below is a summary of some of the things I've learned in just a few quick months. 1. Know When You Don't Know There's nothing wrong with not knowing. There are developers on this team that I've heard everyday say, "I"m not sure how to do that, I need to ask 'so and so'." I feel I'm part of a great team, and maybe this type of honesty isn't the norm. In any case, it's refreshing to see that type of behavior. It's also encouraging to see someone who has been here for many years not afraid to admit when he/she doesn't know something. No one is going to kn

So What Have We Learned Today, Class? Okay, I haven't progressed nearly as far as I had hoped in the textbook. Actually, I still haven't gotten past the GUI development in the 2nd chapter. This doesn't mean that I haven't been picking up what I can. Codefights has still been a great resource. Not knowing a lot of the functions has really been a hindrance. Not knowing many of the commonly known practices of developers has also slowed me down considerably. So, what have I learned? Visual Studio When I first started as a software tester in March this year, I was using TFS (Team Foundation Server) web portal. For those who don't know what this is, it's a web-based portal to let you see what your team is working on. Above is a generic screenshot of what's going on right now and things we're fixing. You can click on each task and see more specific details. This view is much easier to navigate to me, but I needed to learn how to integrate with Vi

Codefighting Progress Okay, first, if you're not following my other blogs, it's worth noting that I'm simultaneously studying to become a pilot. I had no idea the time it's going to take to study everything for the flight school. The amount of information covered is insane and demanding. I'm going to keep both up, but not nearly at the pace I had initially hoped. The actual ground school lasts 12 weeks, and then I take a written test. I'll have to get actual flight time in and eventually take the flight test within 2 years to be a full blown pilot. That being said to iterate how much my focus will be divided briefly, but I will come back more focused to this task at hand. I'm in the 2nd week of the 12 week close so only 2 1/2 months left, then my flying time is only on the weekends. I'll figure out how to do that. As far as the what I've been doing lately, well, I haven't progressed further than the 2nd chapter in the book. In my spare

Well, I've started my pet project, and I've got a GUI laid out. It's a little slow going, but it should work well in the end, I think. I'm sure there's going to be lots of feedback and many different ways I could do things. Right now, however, I'm limited to what I am learning in the text. As promised, here's the screenshot of my first program. Help? I'm trying not to ask too many people how to write any of the code yet for a couple of reasons. First, I haven't learned any code yet, and I likely won't understand a word of what's being told to me. Second, I'm afraid that what I'll be told I'll understand at that moment, but since I didn't have to work  for it, it won't get burned into my memory like the knowledge I have to seek out. Those long hours searching usually scar you to the point you never want to forget those lessons again. Function Since I don't have too much to show, I'll just explain what th