Posts

Showing posts with the label productivity

Why Programming Environments Matter, Gaming Edition

As I do some posting on another site, I've been running the   BGR live stream of the Sony Playstation 4 launch   on my second monitor and I've got something to say. I'm not a "gamer". I stopped playing games back in 1999 when I found that I had lost yet another weekend to Quake and Tomb Raider. I spent innumerable hours playing Quake, TR, Doom (and many others -- the late 1990s were kind of slow for me, socially speaking) on my Micron Pentium II. Before that, Falcon 3.0 (and Commander Keen and Wolfenstein 3D) on my Northgate 386/33. In medieval times, Ultima on my Mac Plus and Adventure on my Atari 2600 occupied my time. I was never all that good, but the games absorbed my brain in a way that TV never did. I had to stop playing games because I didn't do much else in 1999, besides go to work.   Since then, I have watched developments in game hardware and software from the sidelines. I do have some observations about the situation with the forthcoming PS...

How I Migrated My Source Code from Subversion to Git

While at University in the eighties, I didn't learn much in the way of useful software development tactics or strategies. It was just a question of fulfilling the homework requirements and getting past the exams. I was an EE student and not a ComSci major, after all. When I started my first job out of college, which was as much about programming as it was engineering, I was introduced to version control in the form of the PolyTron Version Control System, or PVCS. At that time, I worked in a two-person coding group. PVCS kept us from stepping on each other's work and allowed us to track our changes, using nothing more than the legendary MS-DOS command line.   When I moved on to my second job, the coding environment was more complex and chaotic. I was surprised that the version control strategy consisted of occasionally pkzipping the source files. The product itself was somewhat confused. I've worked on many projects since then, and it always seems that the better-run p...

My Experience with OneNote on Smart Phones

OneNote is my favorite Microsoft productivity program. I would like to say that I have had a lot of experience with Microsoft's OneNote on mobile devices, particularly on smart phones. Unfortunately, I have just about no experience with OneNote on smart phones. I have been using OneNote on Windows desktops and laptops for well over four years. I've used both OneNote 2007 and OneNote 2010. OneNote was the program that convinced me to move from taking notes from simple text files. I had been taking notes that way since around 1989. Generally speaking, I'd rather have access to OneNote than Word, Outlook, or even Access (the database program). I think that OneNote is the worst-marketted product in Microsoft's stable. People just don't know about it. Two years ago, I was  using a Nokia E71 smart phone and awaiting the first modern Windows Phone devices. My expectation was that I could run OneNote on my smart phone and seamlessly edit my notes on my phone, the Micr...