Jump to content

  • Log In with Google      Sign In   
  • Create Account

Robot Ninja

Member Since 01 Jul 2011
Offline Last Active Jul 07 2014 04:54 PM

Posts I've Made

In Topic: OMS CS degree - viable option?

30 May 2013 - 12:23 PM

Looks like a coursework-only degree.  No research requirement, and no thesis.


The coursework-only aspect will make a difference to some people, and will make no difference to others.  


Ultimately it is still just a bit of education and certification.  It won't guarantee a job, and it won't guarantee any changes to your career.  You may be able to leverage the knowledge and other facets of what you gained, but it guarantees you nothing.



If you want to invest the time and the money, and if it fits your life goals, it might be worth it.


Thanks for the input. Honestly, my desire is to get my feet wet in industry before I go on to a MS CS program. So I am working on my own projects to build up a portfolio. Unfortunately I keep getting mixed answers to this question of getting a Master's degree (or even a Bachelor's in CS) first, which becomes frustrating and a bit of a distraction when I am working towards my primary goal. That said, grad school is more of a backup plan if finding work is seeming like a shot in the dark.

In Topic: OMS CS degree - viable option?

30 May 2013 - 02:42 AM

$7000 for an accredited MS degree is a killer deal man. You rather be in student debt for some help from some ivory tower?


$7000 is a killer deal, and that is the main appeal for me. I've never been the kind of person that thinks it's necessary to spend 50k+ a year because the school is well known. Plus, I've already done quite well learning on my own, so I'm not worried about understanding the material on my own. However the ability to have intelligent and enlightening discussions with experts in their field is something that can be of very high value to those that take advantage of the opportunity. A meaningful connection with a faculty member you admire can be really great, I think, but is of course not the be-all and end-all. I appreciate the input. I am still very interested in applying to this program, but would still like to get some additional insight.


*EDIT* In retrospect, I should have given this thread a better title than "viable option".

In Topic: OMS CS degree - viable option?

30 May 2013 - 02:04 AM

Those issues aside, I'm kind of worried that an online format won't allow enough access to the instructors.


A masters degree isn't about being taught by instructors it is about self learning.  The instructors are only there for guidence or to ask the odd question.  You should be able to watch the lecture material and then go away and research / do your project on your own with only minimal instructor interaction.


Right. Correct me if I'm wrong, but don't MS students still typically work under a faculty member related to their focus? So it would still be important to have that one-on-one interaction, right?

In Topic: OMS CS degree - viable option?

30 May 2013 - 01:14 AM

I don't think on-campus is any better tbqh. Who the heck wants to go through traffic jams, look hours for parking, be waitlisted ALL THE TIME for classes, getting bad proffs? Its very annoying, and made me not want to major in CS in the first place. For CS I don't need distractions like those, they just get in the way of actual learning. That's why im just a hobbyist game programmer now.


Those issues aside, I'm kind of worried that an online format won't allow enough access to the instructors.

In Topic: Best time to commit changes to repo...and branching?

27 April 2013 - 01:29 PM

Another item to consider is looking into GitFlow.  It is not a part of git itself and is just a way to work which survives in complex dev environments.  See: http://nvie.com/posts/a-successful-git-branching-model/ for more information.  It is pretty similar to how we ended up doing things on some insane large projects I've worked on but with the addition of some scripts: https://github.com/nvie/gitflow#readme, it makes things fairly easy compared to our adhock methods in Perforce.  An added benefit, if you happen to use Os X, SourceTree (my favorite git front end for OsX) integrates the scripts directly.  Point and click git flow is really sweet.


Wow, GitFlow makes working with development branches really nice. I've been using GitExtensions because it provides an easy interface for git and I like how it presents the repository graph. I noticed that there's a request to integrate GitFlow into GitExtensions, but it doesn't seem like anyone is trying to implement it. While GitFlow would be really nice to use, I'd rather stick to GitExtensions for now than go back to using the command line for Git. So far I'm really the only one working on this project, so I'm the only one modifying my repo. I will of course adopt the same branching model into my project though. Also I'm certainly open to recommendations for other Git GUI extensions, especially if they have has successfully integrated GitFlow.


It seems like SourceTree (http://sourcetreeapp.com/) has already integrated GitFlow into it's Mac version, and are working to get their Windows (beta) version up to speed. They're not quite there though, so I guess I'll just stick with GitExtensions for now. I also came across an article by Scott Chacon, where he talks about an alternative version control scheme to GitFlow. His team uses it at GitHub. Here's the link for anyone interested: http://scottchacon.com/2011/08/31/github-flow.html. I *think* the GitFlow model still seems more fitting for my project though...

Also although I'm writing an editor, I'm also building engine code in the same solution. I ended up having separate local repos for each project in the solution. Is it recommended to have one unifying repo instead? It would definitely make keeping track of changes much easier (since there would only be one repo to commit to), but I don't know if there's a big negative that I haven't thought of.