Reading “The Unix Philosophy”

At the part where the author talks about the benefits of portability. Helping me to re-think many of my past projects (both personal and work) by thinking about how much longetivity they’ve had and how easy it was to move them to new environments as upgrades and systems changes happened.

Unfortunately, I realize I haven’t done as great in this area as I would have liked!

Gettin’ C# together with PowerShell?

Doing a lot of work with PowerShell lately at the office. Doing a lot of reading about Unixy type stuff to deepen my understanding of my new MacBook Air. Reading about pipes and “doing one small job well” and all that. PowerShell really embraces those Unix values.

The big thinking point for me is – how can I embrace that in my C# development work? i.e., How can I write C# applications which consume and emit .NET objects which can live gracefully on the PowerShell pipeline?

Workin’ on it…

Merging the Unix philosophy into my work and life

I’ve been thinking a lot about the “Unix philosophy” and how it applies to projects and other things I do in my work and personal life.

I know “the philosophy” comes in some different forms depending on where you read about it. My first exposure came from reading “The Art of Unix Programming” a few years ago. Recently I got my first Mac laptop. I’ve used Linux a good bit over the years (and Cygwin) and I have a decent understanding of how things work and are built in the Unix Way. But I’m seeing many ways that I can start taking those ideas and breaking down the conventions of my Microsoft-centric software development job, and other big and small things I do in my personal life.

For example, the “keep it small” principle is something I often forget about at work, sometimes leading me into an application development that gets big enough that it is more difficult to maintain than it needs to be. There are reasons for it, at my work – mostly having to do with the tools we use and the administrative overhead involved in each new application we build. So there is a motivation to stuff as much as possible into fewer applications to cut down on the administrative overhead. But that means the complexity and difficulty of maintenance goes up.

More to come – gotta go get out of a walk on this beautiful sunny day!