CajunArson writes "I recently dug up an old P4 that is in fine working order and did what any self-respecting Slashdotter would do: I slapped Linux on it to experiment with making an NFSv4 server. One other thing I did was to remove the old AGP video card to save on power, since this is a headless machine. Now, I removed the video card after the installation, and I'm doing just fine as long as the machine will boot to a state where networking works and I can SSH to it. My question: Is there a good solution to allow me to log into this box if it cannot get on the network? I'm looking for solutions other than slapping a video card back in. In my case, I will have physical access to the machine. A few caveats to make it interesting: This question is for plain old desktop/laptop systems, not network servers designed to run headless. Also, I am aware of the serial console, but even 'old' machines may only have USB, and I have not seen any good documentation on how and whether USB works as a substitute. Finally, if there is any way to access the BIOS settings without needing a video card, that would be an extra bonus, but I'm satisfied with just local OS access starting from the GRUB prompt."

wikid_one writes "I recently went back to college to finish my CS degree, however this time I moved to a new school. My previous school taught only C++, except for a few higher level electives (OpenGL). The school I am now attending teaches what seems like every language in the book. The first two semesters are Java, and then you move to Python, C, Bash, Oracle, and Assembly. While I feel that it would be nice to get a well-rounded introduction to the programming world, I also feel that I am going to come out of school not having the expertise required in a single language to land a good job. After reading the syllabi, all the higher level classes appear to teach concepts rather than work to develop advanced techniques in a specific language. Which method of teaching is going to better provide me with the experience I need, as well as the experience an employer wants to see in a college graduate?"

relliker writes "So here I am at age 39 with two contractual possibilities, for practically the same pay. With one, I continue being a techie for the foreseeable future — always having to keep myself up-to-date on everything tech and re-inventing myself with each Web.x release to stay on top. With the other, I'm being offered a chance to get into management, something I also enjoy doing and am seriously considering for the rest of my working life. The issue here is the age of my grey matter. Will I still be employable in tech at this age and beyond? Or should I relinquish the struggle to keep up with progress and take the comfy 'old man' management route so that I can stay employable even in my twilight years? What would Slashdot veterans advise at this age?"

A story at Wired delves into the ongoing struggle between Google and Facebook to establish their competing visions for the future of the internet. "For the last decade or so, the Web has been defined by Google's algorithms — rigorous and efficient equations that parse practically every byte of online activity to build a dispassionate atlas of the online world. Facebook CEO Mark Zuckerberg envisions a more personalized, humanized Web, where our network of friends, colleagues, peers, and family is our primary source of information, just as it is offline. In Zuckerberg's vision, users will query this 'social graph' to find a doctor, the best camera, or someone to hire — rather than tapping the cold mathematics of a Google search. It is a complete rethinking of how we navigate the online world, one that places Facebook right at the center. In other words, right where Google is now." A related article at ReadWriteWeb suggests that while Facebook's member base is enormous, the company hasn't taken advantage of its influence as well as it should have, though the capability for it to do so still exists.