View Single Post
Old 01-07-2010, 11:32 AM   #23
MickMcGeough
First Line Centre
 
MickMcGeough's Avatar
 
Join Date: Oct 2002
Location: Calgary
Exp:
Default

Quote:
Originally Posted by FanIn80 View Post
How close to C is C#? Objective-C is really just pure C with an OO layer on top (my understanding at least). Is C# the same way, or is it just a modified C? Mind you, I can look that up on my own I guess.

Like I mentioned earlier, I don't mind the .Net IDE. I'm used to it from my days of doing VBA coding. Sure it's a resource hog (like pretty much all MS products), but it's laid out in a way that makes sense to me.

I guess I really need to think about how I want to ply my trade afterward. I don't really want to do the code monkey thing, and I'm kinda hoping that my resume (+ a degree) will help me avoid that stuff. There's also the option of doing my own stuff, which is where learning a decent language and framework is important.

Either way, maybe C# is something to consider. Java, PHP or C#...

Edit: There's also Perl as well, though I'm not sure how it fits into everything these days. I remeber starting to teach myself Perl back in '97, when I thought I had to write some CGI stuff for a project I was doing for the Lethbridge Public Library. We figured out a different way to do it though, so I stopped reading up on it.
Syntactically, C and C# are pretty similar so the learning curve shouldn't be too rough (but then, Java is very similar syntactically as well). Technically, they're quite different. I don't know enough about pure C to really get into the details though.

Your resume and degree will not, on its own, keep you free from ending up as a code monkey. You'll almost certainly spend some time in that capacity as part of paying dues; not unlike any profession, really. Actually, it's a good way to get used to working in a professional environment and getting familiar with how a software development team works from start to finish. Just don't get complacent. Push for opportunities to take part in design and don't screw it up when you get the chance.

Another thing worth noting: the smaller the team, the better chance you've got of taking on a bigger role earlier, and having an opinion worth something in determining the direction of the project. There are obvious caveats to working in smaller companies but it can pay big dividends experience-wise early on.
__________________

MickMcGeough is offline   Reply With Quote