Tuesday, April 27, 2010
Sorry
Just read through some old posts, and I've decided that I'm more of a BLAH-ger than I am a blogger. Sorry about that.
Sunday, April 25, 2010
Just how I feel!
So I was looking through a book for a quote or story that related to my lesson about Christ today, and I ran across the author's preface. He talks about his wife, and it is just how I feel about mine (I've substituted Rhoda's name in there when applicable):
"...if we must compare individual statures, I think the following sketch represents the approximately correct proportions.
"When [Rhoda] approaches the pearly gates, the Lord may say to the angels something like this, 'Why, look everybody -- here comes [Rhoda Crabb]! [Rhoda's] finally here! Let's all go out to welcome her and bring her in.' But as he greets her on the steps, he will probably stop and add, '[Rhoda], what on earth is that sorry thing you're dragging behind you?' To which she will respond, 'Oh, that? That's my husband. Can I bring him in too?' Without her I haven't got a chance..."
Love you Rhoda!!!
"...if we must compare individual statures, I think the following sketch represents the approximately correct proportions.
"When [Rhoda] approaches the pearly gates, the Lord may say to the angels something like this, 'Why, look everybody -- here comes [Rhoda Crabb]! [Rhoda's] finally here! Let's all go out to welcome her and bring her in.' But as he greets her on the steps, he will probably stop and add, '[Rhoda], what on earth is that sorry thing you're dragging behind you?' To which she will respond, 'Oh, that? That's my husband. Can I bring him in too?' Without her I haven't got a chance..."
Love you Rhoda!!!
Saturday, April 24, 2010
Short-Changing My Kids...One Piece of Pinewood at a Time
I just got to wondering. This is a purely hypothetical situation, so I'm just curious. Let's just say that like 5 weeks ago, my cub scout comes home from pack meeting with a Pinewood Derby car kit. I think (hypothetically, of course) "Man, 5 weeks is a long time!" and do nothing about the car. About a week ago, we decide (again, it's all hypothetical) it's time to get working on it. Part of me wants to do it "right" (you know, let my son design the car, we cut it out of the wooden block, and then he does the rest: sanding, painting, adding decorations, etc), and yet the part of me that was raised the way I was says, "they have pre-cut cars at the store".
So I have a question. And remember, I'm still speaking hypothetically. If I were to, say, run my son to the store so he can pick out the pre-cut car, then show him quickly how to sand it (and then finish sanding it after he gives up two minutes later instead of insisting he continues to work on it) and then show him how to spray paint it (and then take over and finish most of the painting after he tries for a second, because I'm too worried that he'll get clumps or spray something (or even someone) that shouldn't be spray painted). I then add the purchased accessories (decals, spoiler, engine, and some other weights), after getting some input from him. Then I have him hammer one of the wheels in place, but the nail goes in a little crooked, so I pull it back out and fix it and then hammer in the rest of the nails. Keep in mind, all of this is finished at 10:30 pm the night before the race, and we were supposed to weigh the car in by 9 pm that night. So we take the "late weigh-in" option on the day of the race, just a couple of hours before it's supposed to start, and we still only get there with 2 minutes to spare. I'm not saying all this happened. Like I said, I'm just imagining this whole thing. I promise.
So, let's just say that hypothetical situation actually occurred (not that it did, of course. I'm just playing the "what-if" game). Do you think that I'm robbing my 8-year-old of the valuable cub scout experiences he deserves?
Like I said, it's all hypothetical. I know, I have a crazy (and somewhat detailed) imagination, right? But that's not how it went down. Really.
By the way, on a COMPLETELY unrelated note, have you ever noticed how the word hyPOTHETICal almost has the word PATHETIC in it? Just an observation.
So I have a question. And remember, I'm still speaking hypothetically. If I were to, say, run my son to the store so he can pick out the pre-cut car, then show him quickly how to sand it (and then finish sanding it after he gives up two minutes later instead of insisting he continues to work on it) and then show him how to spray paint it (and then take over and finish most of the painting after he tries for a second, because I'm too worried that he'll get clumps or spray something (or even someone) that shouldn't be spray painted). I then add the purchased accessories (decals, spoiler, engine, and some other weights), after getting some input from him. Then I have him hammer one of the wheels in place, but the nail goes in a little crooked, so I pull it back out and fix it and then hammer in the rest of the nails. Keep in mind, all of this is finished at 10:30 pm the night before the race, and we were supposed to weigh the car in by 9 pm that night. So we take the "late weigh-in" option on the day of the race, just a couple of hours before it's supposed to start, and we still only get there with 2 minutes to spare. I'm not saying all this happened. Like I said, I'm just imagining this whole thing. I promise.
So, let's just say that hypothetical situation actually occurred (not that it did, of course. I'm just playing the "what-if" game). Do you think that I'm robbing my 8-year-old of the valuable cub scout experiences he deserves?
Like I said, it's all hypothetical. I know, I have a crazy (and somewhat detailed) imagination, right? But that's not how it went down. Really.
By the way, on a COMPLETELY unrelated note, have you ever noticed how the word hyPOTHETICal almost has the word PATHETIC in it? Just an observation.
Monday, April 12, 2010
Light at the End of a Looooong Tunnel...
So at my work, I've been working on a bunch of projects. Looking back on the last 18 months or so, I can honestly say that I'm really proud of a lot of things I've accomplished. There have been some major changes and updates that I have made, and some of the things I'm doing have had a positive effect on the whole company.
The reason I bring it up, is because about 18 months or so ago, I got asked to start working on a HUGE project. Now, when I say huge, I mean it is extremely involved and there have been tons of changes and revisions. At one point they said, "Oh, there's actually going to have to work two completely different ways, depending on what kind of user it is." Then they said, "Oh, both of those different processes are going to have to work completely differently depending on how they got there". (yeah, if you're counting, that means I have FOUR similar-but-not-the-same versions) Then they added extra stuff to it. Then they tried out a prototype and it worked great, according to what they originally told me, but it just wasn't going to do everything they needed it to do. So while I've been working on all those great things I mentioned earlier, this project has been "on my plate" as one of the higher priorities (obviously not the HIGHEST priority, but it is one of those things that we talk a lot about). If I had a dime for every time I heard the question "So, how's that project coming", asking about this particular project, man, I'd have a lot of dimes.
Anyway, so hopefully I've set up the situation for you well enough to understand why this thing has been on my mind a lot. Well, tomorrow, I am not just releasing it to our internal employees (who will probably yawn when I show them because they have seen it many times, used it, and added on to it), I'm releasing it to the world of users of our website. It's been a VVVEEEERRRRYYY LLLLOOOONNNNGGGG time coming.
Of course, with that being said, there is still a wish list about a mile long relating to add-ons or enhancements to this project (people can think of a lot of those in 18 months!), so I'm sure this is not the last I'll see of it, but the basic project is for all intents and purposes....DONE.
Sheesh.
The reason I bring it up, is because about 18 months or so ago, I got asked to start working on a HUGE project. Now, when I say huge, I mean it is extremely involved and there have been tons of changes and revisions. At one point they said, "Oh, there's actually going to have to work two completely different ways, depending on what kind of user it is." Then they said, "Oh, both of those different processes are going to have to work completely differently depending on how they got there". (yeah, if you're counting, that means I have FOUR similar-but-not-the-same versions) Then they added extra stuff to it. Then they tried out a prototype and it worked great, according to what they originally told me, but it just wasn't going to do everything they needed it to do. So while I've been working on all those great things I mentioned earlier, this project has been "on my plate" as one of the higher priorities (obviously not the HIGHEST priority, but it is one of those things that we talk a lot about). If I had a dime for every time I heard the question "So, how's that project coming", asking about this particular project, man, I'd have a lot of dimes.
Anyway, so hopefully I've set up the situation for you well enough to understand why this thing has been on my mind a lot. Well, tomorrow, I am not just releasing it to our internal employees (who will probably yawn when I show them because they have seen it many times, used it, and added on to it), I'm releasing it to the world of users of our website. It's been a VVVEEEERRRRYYY LLLLOOOONNNNGGGG time coming.
Of course, with that being said, there is still a wish list about a mile long relating to add-ons or enhancements to this project (people can think of a lot of those in 18 months!), so I'm sure this is not the last I'll see of it, but the basic project is for all intents and purposes....DONE.
Sheesh.
Saturday, April 10, 2010
One Man's Junk...
We've all heard the saying "One man's junk is another man's treasure". I think it's all about perspective. Perspective is something I've been thinking about lately.
I am a web programmer, and I get people asking me at work to do "small" tasks for them all the time. "It's just a small request", or "Just something really simple", they say. I think the funniest (and yet sometimes the most frustrating) part is that something that seems so simple on the surface can actually get quite complicated (and that's even before the "feature-creep" - the inevitable requests for add-ons that weren't in the original project description). On the other hand, sometimes things that seem really difficult or complicated are actually very easy. There have been loads of times that I find out that someone has been doing something the hard way because they assume that for me to create something to help them will be a huge task, when it's really a pretty simple thing.
It gets tough, though when people assume that something is simple, especially when that person knows a little about technology and programming. My boss is one of those. He will ask me to drop everything and throw together some "quick and easy" project for him, because he doesn't think it will take too much time. I remember one time he came to me just before lunch and explained a new project, which seemed kind of simple on the surface, but I knew was more complicated "under the hood". Not to mention the fact that it was something I'd never even tinkered with before, so I knew there would be a bit of a learning curve anyway. After talking about the specifics of the project a bit, he said, "So, do you think you could have a working version by this afternoon?" At first, I just looked at him, trying to figure out if he was joking. After a couple of seconds, I realized he wasn't. Because he thought it was a simple thing.
So after some experiences like that, I have learned that when someone comes to me with a "simple" task, it is best to be forthcoming with them about the difficulty of the task. They may not need a lesson in programming to understand all the detailed mechanics of it, but it's helpful to them to know what they are really asking for. When I first became a programmer, I didn't really know how to handle this kind of thing. I would just say "sure, I can do that" (while I'm thinking "and you want this done by...when?) and then do the best I could to get things done. Even though I'm not perfect at it, I'm learning to let people know up front some of the simpler and more challenging aspects of the project that I can see (because I think like a programmer).
Now, with all that being said, I realize that this translates to just about every aspect of life. To really make things work, you may not need to HAVE someone else's perspective, but you need to be able to try to SEE someone else's perspective to understand better where they are coming from. Simple assumptions often cause the biggest problems in relationships with others. So many misunderstandings and conflicts could be avoided if we just understood each other's perspective a little better. And guess what, that requires COMMUNICATION - something I'm working on.
One note, while I'm on the subject of communication. I'm pretty sure that the quote at the beginning of this post really describes my blog. My thoughts are my treasure (one of them, at least). To the rest of you, probably junk. And you know what? I'm ok with that.
I am a web programmer, and I get people asking me at work to do "small" tasks for them all the time. "It's just a small request", or "Just something really simple", they say. I think the funniest (and yet sometimes the most frustrating) part is that something that seems so simple on the surface can actually get quite complicated (and that's even before the "feature-creep" - the inevitable requests for add-ons that weren't in the original project description). On the other hand, sometimes things that seem really difficult or complicated are actually very easy. There have been loads of times that I find out that someone has been doing something the hard way because they assume that for me to create something to help them will be a huge task, when it's really a pretty simple thing.
It gets tough, though when people assume that something is simple, especially when that person knows a little about technology and programming. My boss is one of those. He will ask me to drop everything and throw together some "quick and easy" project for him, because he doesn't think it will take too much time. I remember one time he came to me just before lunch and explained a new project, which seemed kind of simple on the surface, but I knew was more complicated "under the hood". Not to mention the fact that it was something I'd never even tinkered with before, so I knew there would be a bit of a learning curve anyway. After talking about the specifics of the project a bit, he said, "So, do you think you could have a working version by this afternoon?" At first, I just looked at him, trying to figure out if he was joking. After a couple of seconds, I realized he wasn't. Because he thought it was a simple thing.
So after some experiences like that, I have learned that when someone comes to me with a "simple" task, it is best to be forthcoming with them about the difficulty of the task. They may not need a lesson in programming to understand all the detailed mechanics of it, but it's helpful to them to know what they are really asking for. When I first became a programmer, I didn't really know how to handle this kind of thing. I would just say "sure, I can do that" (while I'm thinking "and you want this done by...when?) and then do the best I could to get things done. Even though I'm not perfect at it, I'm learning to let people know up front some of the simpler and more challenging aspects of the project that I can see (because I think like a programmer).
Now, with all that being said, I realize that this translates to just about every aspect of life. To really make things work, you may not need to HAVE someone else's perspective, but you need to be able to try to SEE someone else's perspective to understand better where they are coming from. Simple assumptions often cause the biggest problems in relationships with others. So many misunderstandings and conflicts could be avoided if we just understood each other's perspective a little better. And guess what, that requires COMMUNICATION - something I'm working on.
One note, while I'm on the subject of communication. I'm pretty sure that the quote at the beginning of this post really describes my blog. My thoughts are my treasure (one of them, at least). To the rest of you, probably junk. And you know what? I'm ok with that.
Friday, April 9, 2010
Lucky
The main intent of this blog is to share the things that have weighed heavily on my mind. One of the reasons it's been a while since I posted anything is because I've been spending so much time working on some big work projects for both my jobs. Yep, that's right. It always hits at the same time. I figured most of you wouldn't be interested in the intricacies of writing queries or web programs, or even creating or consuming web services. (To those of you who would be interested in those things, I say "Get a life, you sicko!" Just kidding. I love that kind of stuff.) Anyway, that's been monopolizing a lot of my brain power over the last month or more.
However, among all of that, there has been an underlying thought that has stayed present in my mind much of the time. It's how lucky I am. I am so blessed. I have a beautiful, understanding wife. She has been very supportive of me and my endeavors. Not only that, but she manages our household very well. In fact, because of her, nobody has skipped a meal, had to wear dirty clothes out of the laundry hamper, or even had to pay late fees because the bills always get paid on time. She is the best thing that has ever happened to me, and I'll be honest, that's saying something, because I've had a pretty good life so far. I love my sweetheart, and I think she deserves every compliment she gets, even if she doesn't feel that way.
Then there's my kids. Sure, they're kids, so they act like kids, but they are good kids. They make me proud. Last night, we were reading the scripture story of the sick woman who just touched the hem of Jesus' robe and was healed. Mily asked "How did Jesus know that woman was sick?". "Because He's awesome!", Josh replied. Man, it was funny, but it really made me happy inside to know that my kids feel that way. Cause Jesus IS awesome!
Speaking of the Savior, another blessing I am SO lucky to have is that I have my faith. Faith in Christ. Faith in His atonement. Faith in the plan that God has for all of us. I know He wants us to be happy, not just forever, but now. Right now. I am so lucky to know the Savior and His love for me.
Another way I'm lucky is that I have not one, but TWO jobs. One full time, and then some consulting on the side. I know people who have been out of a job for a while, or who have been really struggling to make ends meet because they couldn't find a job that would meet their needs. And I have two. It gets a little hard to balance everything sometimes, but in this economy, I'm not complaining about having enough for what my family needs.
I'm also lucky to have been raised by great parents. My mom and dad are people who are kind and talented. People you just want to be like. Not mean in any way to anyone. I learned a lot from my dad. He was a great example of sacrifice to me. Sometimes he worked two jobs. He worked a very physically demanding job, and I never once heard him complain about how hard it was to go to work. My mom has a great work ethic. If she tells someone she'll do something, she does it and she does it right.
I am lucky to live in the time we live in. I love having a computer and a cell phone. Things I would not have had if I didn't live in the time that I live in. So many modern conveniences. It's amazing. I am also lucky to live in the place that I live in. The US is really a great place to live. Sure, it has its ups and downs, but we are sure blessed in this country. And to be more local, I am lucky to live in Utah. It's a great place to live.
I could go on and on (trust me, I could), but I think you catch my drift. My life has been hectic, trying to juggle it all has been kind of a challenge, but through all this, it is easy to see that MY LIFE IS GREAT. I am SO lucky!
Oh, and I'm also lucky because I have a SUPER POWER!
However, among all of that, there has been an underlying thought that has stayed present in my mind much of the time. It's how lucky I am. I am so blessed. I have a beautiful, understanding wife. She has been very supportive of me and my endeavors. Not only that, but she manages our household very well. In fact, because of her, nobody has skipped a meal, had to wear dirty clothes out of the laundry hamper, or even had to pay late fees because the bills always get paid on time. She is the best thing that has ever happened to me, and I'll be honest, that's saying something, because I've had a pretty good life so far. I love my sweetheart, and I think she deserves every compliment she gets, even if she doesn't feel that way.
Then there's my kids. Sure, they're kids, so they act like kids, but they are good kids. They make me proud. Last night, we were reading the scripture story of the sick woman who just touched the hem of Jesus' robe and was healed. Mily asked "How did Jesus know that woman was sick?". "Because He's awesome!", Josh replied. Man, it was funny, but it really made me happy inside to know that my kids feel that way. Cause Jesus IS awesome!
Speaking of the Savior, another blessing I am SO lucky to have is that I have my faith. Faith in Christ. Faith in His atonement. Faith in the plan that God has for all of us. I know He wants us to be happy, not just forever, but now. Right now. I am so lucky to know the Savior and His love for me.
Another way I'm lucky is that I have not one, but TWO jobs. One full time, and then some consulting on the side. I know people who have been out of a job for a while, or who have been really struggling to make ends meet because they couldn't find a job that would meet their needs. And I have two. It gets a little hard to balance everything sometimes, but in this economy, I'm not complaining about having enough for what my family needs.
I'm also lucky to have been raised by great parents. My mom and dad are people who are kind and talented. People you just want to be like. Not mean in any way to anyone. I learned a lot from my dad. He was a great example of sacrifice to me. Sometimes he worked two jobs. He worked a very physically demanding job, and I never once heard him complain about how hard it was to go to work. My mom has a great work ethic. If she tells someone she'll do something, she does it and she does it right.
I am lucky to live in the time we live in. I love having a computer and a cell phone. Things I would not have had if I didn't live in the time that I live in. So many modern conveniences. It's amazing. I am also lucky to live in the place that I live in. The US is really a great place to live. Sure, it has its ups and downs, but we are sure blessed in this country. And to be more local, I am lucky to live in Utah. It's a great place to live.
I could go on and on (trust me, I could), but I think you catch my drift. My life has been hectic, trying to juggle it all has been kind of a challenge, but through all this, it is easy to see that MY LIFE IS GREAT. I am SO lucky!
Oh, and I'm also lucky because I have a SUPER POWER!
Subscribe to:
Posts (Atom)
