Got the invite - thanks!

Late to the party here, but if anyone has a spare, I'd love an inv. cecille.freeman at gmail

I can't read past page 2 of the actual paper, and the article is a little bit vague, but are they saying that 50% of people who PLAY games are women, or that 50% of the time played is played by women? Because if it's the latter, then you're totally correct, if it's the former, then they may have a point about untapped markets.

For example - I'm a female, and I would say I am a gamer, although I play one game primarily - three guesses what that might be (not the sims) - and sometimes I play little puzzle/flash games, but it's rare that I would go out and pick up a new game 'cause I just don't care about most of them. I'm not opposed to the IDEA of buying games, so it's not a social barrier that needs to be overcome. If there is a signficant population like that then that might be considered as an untapped market.

It seems strange to assume that every person ("code monkey") who still writes code late into their career is doing so because he/she "simply never understood the practical or business side of things". There are plenty of developers who understand the business side of things, but just don't want to go into the business side of management. In our company, and I think probably in a lot of others as well, there are two different paths up the food chain. You can either code for a while and then try to get into management with the goal of being a project/product manager and up, dealing with issues like customers and business strategy, or you can work your way up the other side try to become an architect, where you're working on more technical issues. Either way, you end up basically managing people, but as an architect you're still writing code well into your career.

I'm with Rogers and I've seen this a lot. For me, it's not about high latency, it's an auto-disconnect. If a torrent download starts while the game is on, you get disconnected, full stop. Very annoying, especially since we've asked about it before and they basically said that we were idiots who didn't know how to set router priorities.

I'm not sure I agree. They are adding some significant new functionality, it's just not necessarily used by everyone, and it's not really that mature. But the new citation functionality, for example, is aiming much more towards an academic audience. Combine that with proper use of styles and referencing (also much improved as far as I can see), and you can see that they're now moving away from the fancy notepad model towards something that can be used more like Latex. You supply the content, mark up the heading, and it handles referencing, citation and style.

It's not perfect by any stretch of the imagination, and you'd be hard pressed to get an old-school academic to switch from Latex, but the development in this area is certainly not stagnant.

I'm currently at the University of Waterloo doing a PhD in the Electrical and Computer Engineering department. It's in Canada, so it's not a big 10 school, but it has a solid reputation as a pretty decent school, especially in engineering. For our program, it's expected that a grad student maintains at least a 78% average with 75% being a pass. This means that if you're running a grad course, and you think that a student should pass the course, you basically have to give them at least a 75%. The end result is that if you graduate from the program, you're almost guaranteed an A average.

The requirements are listed here: http://ece.uwaterloo.ca/Graduate/PhD/

Waterloo in general is a good place to look for engineering jobs. There's RIM, but there's also a bunch of other tech companies around there. My old company was hiring when I left, and the company that backed my master's work was also looking for VLSI people.

If we were all paid just for time, then everybody would be in at 8:30 and out the door promptly at 5 with exactly 30 minutes for a lunch break and no more. Nobody would have a blackberry and they could lock down the internet to their heart's content And that's one way to do it. Of course, locking down the internet also means employees don't necessarily have access to nice things that make their job easier, like the ability to quickly look up commands etc., but since we're just paying for time, efficiency doesn't matter one way or the other.

On the other hand, it's also possible to create a workplace where it's OK to check slashdot if you're running tests or compiling code or something, and sending an email to a friend isn't a fireable offense. Those sort of workplaces also tend to be the types of workplaces where people don't mind staying a little late to get extra work done or help out a client. They're also the type of workplaces where people don't wake up every morning loathing their existance and hating their jobs. Call me crazy, but I think that counts for something too.