|
| Another three monthsWoot I am just posting here because I feel bad for xanga, everyone's using facebook now.
| | |
| Three monthsThree months since I started working at North49.
One thing nice about working in a small company (when the office is full we have 7 people) is that you get more responsibility. You get to do more. I didn't want to be stuck testing software for a year before I could move on to something else. So far so good, I've been doing lots of programming, testing and even interacting with clients.
In fact that's why I wanted to blog today (even though no one will read it)
I got my first call for me. I got called directly by someone I never heard of before about software I wrote. Luckily it wasn't a big thing, he just didn't know where to run the software and that was it. Nice first though.
Now back to work
| | |
| Second DayWow what weather huh? Pissing rain and howling wind...awesome.
That's how I was greeted when I went to work. Luckily my co-workers were more friendly!
I split the work day into chapters/parts
.Net Framework Fraccas Pt 1.
I was going to make something C# that would detect if the .Net Framework was installed because our software requires 1.1 or 2.0 (probably 2.0). If it was detected then great, if not it would prompt to install it. Woo I got the detection part working...but then an epiphany. More like a let down. How would we use the thing I wrote to detect whether the framework is installed, if it uses the framework itself!!! We decided to let it go for now, thought about using C++. To be continued...
Network Neutered Pt 1.
Next we tried to hook my laptop up to the wireless. (remember I didn't have a computer yet) and we couldn't get it set up so we dragged a network cable all the way from the router to my laptop. This was basically from one corner of the office to the other...one long blue cable. The guy who knew how to set the wireless wasn't working today and eventually someone got hold of him on the phone. I put the password blahblah in and waited for it to connect. It didn't. I stared at it with the other guy and we wondered. Then I decided to reboot my laptop. Just as it was rebooting...it connected to the wireless. Luckily I was doing something else and didn't save so it interrupted the wireless. I gave him back the cable and went back to work. Done with that...for now
Weather Wonderful
Remember the weather? The pissing rain and howling wind? Boss decided to be cool again and ordered pizza for everyone! Woohoo! 2 large pizzas and 2 2L bottles of pop. That was a load of fun. BTW they used my "desk" as the lunch table. Or more I used the lunch table as my desk... While eating we discussed game shows of all things. We also mentioned this...
.Net Framework Finale Pt 2.
It was mentioned that we were having problems about the .Net Framework detection. Someone mentioned that the .Net Framework has to be installed already. Well that's a fun hour or two wasted...
Network Neutered Pt2.
Well I had to install some programs that were stored on our server so I sat around and did that after lunch. However the installation crashed when the wireless hiccuped so I decided to be smart and plug in a network cable to my laptop that was closer than the one across the room. Surely it must be more stable At first I didn't pay attention. But then I realized the installation was REALLY REALLY SLOW. I showed the other guy and he blamed the network being on the fritz (the phones weren't working properly and they're VOIP phones). So I sat there and waited and waited. I got some MSN time with Jun and Clive though (who incidently were at work and don't know each other). I checked the network connection and ti was at a measly 10Mbps. I think it was slower than that though. I talked/complained about that with the guys and then after a couple hours the guy in the room at the other corner suggested to try the long network cable again. Lo and Behold it worked. Everything went great after that... Yay for a few hours of doing nothing much. At least we learned that the network cable or jack I tried to use was bad....
I basically spent the rest of my time installing the programs from the network, honestly not much work done. However the guy who did the least work (I think...I'm not sure what the boss was doing) was the consultant again! Not his fault though, the phones weren't working so no one could call and ask for his...consulting!!!
It must be wonderful to be a consultant.
Anyways that was my second work day. Hopefully my third will be more productive.
| | |
| First dayWell I had my first day at work... Learned several things too.
It started off well, one of the guys (there's only 7 people including me) showed me their current projects and plans and about what the company does. I had to use someone else's computer though because the boss forgot to buy a new one. I also tried to log in to the computer but they forgot to get me a network login as well. However that didn't take long. No real lessons here other than stuff about the company.
The place is a nice place to work, small office everyone talks to each other and goofs off a lot. Not to say they aren't doing work though. The consultant goofs off the most, I think its because he had no consulting to do  . Lesson: Be a consultant
For lunch the boss bought us Sushi! It was all you can eat and honestly I can say I've had better...still it was cool to have the boss buy everyone lunch on your first day. Lesson: Having a nice boss is cool
When we got back I went to work on some C# thing with one of the guys again. We tried to add a component to the toolbox but instead we added a reference instead. So removed the references from the project and added the components instead. Then we discovered that the component we added wasn't handling events anymore. We spent 1 + hours trying to figure it out until we gave up and started again. This time we added the component first and remembered not to add it as a reference. Lo and behold it worked... Lesson: Even professionals make stupid mistakes
Luckily we were just testing around with it and it wasn't an important thing.
The next problem we had was that we were developing off the network, we didn't save anything on the local machine, and Windows didn't like that. When we would compile and run in the IDE it would work perfectly. However when we tried to run the executable in the bin/Debug folder it would crash and throw some security error. Seems you need to "Publish" it for Windows to allow you to run the executable when its not on the local machine. Had to use google to figure it out. How do you like that? Google helping us to use Microsoft's software. Lesson: Microsoft IDE isn't as helpful as you'd hope.
Then came the end of the day and I got to go home finishing most of what we were doing (it was nothing big anyways). I'll be bringing my laptop tomorrow as my computer.
So in summary what did I learn?
- Be a consultant - Spend half the day chatting
- Having a nice boss is cool - I had one at Sushi House too...and then this one buys sushi..hmm
- Professionals make stupid mistakes - Makes me feel better about myself when I was at school being dumb
- Microsoft IDE isn't as helpful as you'd hope - Thank god for Google!
Something I didn't learn at work but already know...I'm falling behind in Rappelz!!!! damn you guys taking advantage of my employment.
PS Kaegirra is playing Rappelz so check out the forums if you want to play with us again. F2P sorta like L2.
| | |
| Kaegirra Update!!Hey guys and gals!
Were you ever in Kaegirra? We've got a new setup now, a whole website dedicated to the guild.
Home: http://kaegirra.net
Forums: http://forum.kaegirra.net
Photo Gallery: http://gallery.kaegirra.net (Registration + Authorization required)
Wiki: http://wiki.kaegirra.net
Even if its been a while come and say hi maybe some of them will remember you!
 | | |
|
