Tuesday, March 10, 2015

Awesome Blog Post Goes Here.

This post is not really awesome.

I had a great idea last night at work, and thought, "I should write this down, because it's got the start of something great! This is awesome!" and then these jobs started, and I had to monitor them and well, it's complicated. My cosmic train of thought totally derailed, went into hyperspace, and is currently involved in a life or death struggle against the Shadows.
Stinkin' Shadows and their shenanigans. 

So pretend that this post tells you all about the wonders of learning something profound from the color of flowers, because that's all I can remember.

Saturday, February 14, 2015

Encapsulation, Abstraction, Inheritance and Polymorphism

These are the things that make objects in computer programming languages.
Encapsulation: The object's internal properties are kept hidden from outside the object.
Abstraction: The object possesses a way to handle its internal data.
Inheritance: The process by which a specific class is created using an already existing class.
Polymorphism: the capability of one type of data to be used like it's another.
I've been studying this so I can learn C#. Right now, I'm studying virtual members, and learning about how C# uses them to specify how a specific action may be different for a child class as opposed to the parent class.
It's been a long time since I've devoted this much concentration to one subject. There's a heavy temptation to branch out on something else, but knowing this stuff will make me more valuable to the company where I work. The book I'm studying is divided into 24 chapters, and carries the convenient title "Teach yourself Visual C# 2010 in 24 Hours". This title mocks me. It takes me about three hours to go through a chapter. I'm learning a lot. There is a certain amount of beauty in the way C# is written, and also some frustration. the syntax for instantiating a new member of a class is hilarious to me. As is the requirement for non-necessary parenthesis. I don't mind the curly braces. There's a certain snap to the appearance of code that has curly braces. I've always liked seeing them.

I need a way to make what I'm learning real to me. Working on the book projects are one thing, I need a project to do something useful.
I'll need to do some thinking on that. Iterators are still a couple of chapters out.

Thursday, February 12, 2015

Longing for Westernesse

I need to shave, get ready for work, pick something else up, but something running loose in my head right now and I have to get this out there.

There's a fine line between loving and accepting, and how you understand that could very well affect your your soul.

No more time to expound. Can't elaborate. Just don't want to loose that thread.
Do you understand the difference between loving something and accepting it? Do you know when to apply each.

furthermore (this is related in one of those random clear to me, not so clear to others ways), what if the telos for the whole English language and grammar was to ensure that for the perpetuity of this existence that sun would sound like Son? Do you see the lessons there?


EDIT***
I did it, got shaved, to work on time, and picked something else up. I even dumped out the compost onto the compost pile.
I need to think some more on the difference between love and acceptance. There's something about holiness there that can't be grasped by the non-Christian mind. There's also something deep about loving someone without accepting their behaviors. I love a lot about myself, but there's a lot of things I don't accept, I guess I need to start by defining acceptance.
To Be Continued.... I got some insomnihacking to do.

Saturday, February 7, 2015

Learning to Code in C#

Sorry I might have a boring post or two over the next little while,
I'm learning to write programs in C#.
yeah, I'm going there, I have to, it's what the development teams use, so it's important to know it if I ever hope to do something besides press the L button.
I have to concede the following:
1. So far, learning C# has been painless. As a language it makes sense. So far. That could be because I'm using a good book for learning C# ("Sams Teach Yourself: Visual C# 2010 in 24 Hours"), or because I know it's so important to learn it, but I don't care. I can write code and enjoy it using a Microsoft language.
2. I'm really enjoying Visual Studio. Yeah, I said it. It's useful, keeps me focused more on the logic of what I'm doing and less on the syntax. True, I'm still writing a lot of semi colons and curly braces, but other times, I start writing stuff, and intellisense really helps me write it quicker.
So yep,
I'm not giving up on Linux, or UNIX, but I have found use for Windows too.

Friday, January 30, 2015

Keeping the QSO Rate Up

My twin ham radio resolutions for this year have been:
1. to average 1 QSO a day
2. to operate twice a week.
So far, I'm doing decent, I'm down 3 QSOs right now, but that's because I had a couple of days when I only had time to make one QSO.
Goal 2 has been pretty easy to keep
Other things I'm exploring in the world of Radio:
Microwave transmissions.
CW.
So far, I've only made CW QSOs. Use the code or loose it!

Tuesday, January 20, 2015

I Can Feel it Deep Down, Waaaaaay Down.

Gonna be up late, I can feel it.
Writing features out for a rails webapp that will help me track my blood pressure.
I'm using a spreadsheet now.
It's taunting me. I bet my father-in-law would like something like this. Login, record some metrics, send to Dr.
Will be that simple.
It's 5 columns of data, a user, a date/time, 2 columns for the blood pressure, one for the heartrate.
It's coming together.
now to follow through.
I bet I don't sleep much.

Watch my twitter feed and this post for commits.

Tuesday, January 6, 2015

Ham Radio New Year's Resolution

I made one new years resolution about ham radio. My operating habits during December greatly influenced the wording

I, KG4GVL, do resolve to do my best to operate a minimum of twice a week, with the goal of averaging one QSO per day for 2015, or may the Wouff Hong find me as I sleep.

I've tried the whole "QSO once a day" thing, and that quickly became work. I managed to go somewhere around two months with a QSO every day, and many days it felt like I made the contact because of the commitment, not because I enjoyed the QSO. Time is a precious commodity in our house, and I don't have a lot of it to operate radio. In December, I managed to operate a handful of days, spending about an hour of time at a time (sometimes less), and had a blast running stations that were calling CQ. I even managed to call CQ a few times my own self and snagged a few new countries. Part of that I realize was propagation, but I've learned through the years that it don't matter how well propagation is if you don't get on the air. Plus, the maxim "RF gotta go somplace" is a reality. When you QRV, the signal goes somewhere, and the RBN network is a testament to how well some bands do under what would normally be considered marginal conditions. I really enjoy operating when I can get several QSOs at once.

Other people have made their resolutions too, one of the coolest is to build a project from your birth month/year issue of QST. I didn't see much in that would really work for me in the October 1977, but if anyone has an extra issue that they'd let me peruse, I wouldn't mind. :) I do have an October 1953 issue of QST that looks pretty interesting, and I think it has part of a 222 MHz project that would be pretty neat to construct, if I could find the parts to construct it.

Also doing some investigating into ham radio with microwaves. If the kids ever get their license, I think they'd get a kick out of building stuff they can use to bounce a signal off a satellite, or even the moon. The local library has a copy of The ARRL UHF/Microwave Experimenter's Manual and while some of the math inside seems complicated, the projects/ideas inside seem pretty straight forward.