Kyle Ellman

Last week, I had the pleasure of doing a photoshoot for room 201. For some reason, in this house of 40 college guys, a room will sometimes want a special photoshoot. Well, they had been asking me to do it all last semester, and we never had a time when everyone could. So, when we figured out that this past Saturday worked, I had to oblige.

So, here they are.

Owen

Danny

Trent

Charlie

I need to write more, I’ve realized. I need to make things. So much of what I’ve been doing lately involves processing things. Math, code, numbers, problems with one solution. I’m not too bad at it, and I’m really good at some of it. Sometimes I don’t want it, though. Sometimes it feels that what I’m learning to do has no soul. And as a computer science student, when I’m working hard and focusing on it, it’s not too hard to feel like I don’t have one either.

So, I have to thank God for words, people, photographs, food, drink, movies, plots, happiness, faith, pain, struggle, successes, and failures. Without these things, I’m left without a soul.

I think that’s all for now.

Ellen asked me to put these up today, so they’re not fully edited. But here is a breif preview of some of the shots from the Miller Wedding. (click on the thumbnails to see a bigger version)

So, I was on my thinking chair (read: toilet) this morning and had a though enter my head: “What will reading recipes be like ten years from now? Will it be on a phone, a small computer made for the kitchen? Something else?”

I have a feeling that, to some extent, we will be reading recipes from a screen of some kind. If this comes true, wouldn’t it be nice to have some standard format in which a recipe is stored? I’m thinking a standard XML (extensible markup language) format I’d like to call RML (recipe markup language) that could be created, modified, and viewed on any sort of device, sort of like how there’s a thousand different ways to use twitter, but it’s still standard, except it’s a file rather than an online service. These recipe files could either stored on someone’s iPhone or other device, internet enabled or not, or simply downloaded onto a device whenever needed. Each device or application would be able to display each recipe consistently, independent of the source of the recipe file, whether it be from some online service or right on the device being used.

Any ideas out there?

This weekend, I shot a wedding, and gave out a few of my business cards. I realized that if those with the cards visited my site, they would be redirected to this blog, which would not be too helpful to someone seeking a photographer. So, I’ve replaced the redirection with a simple page that resembles my cards including a links to this blog, my flickr page, and a way to directly contact me. Hopefully it’s helpful.

I hope to put something better up sometime to replace everything on kyleellman.com once I have a a period of time when I don’t have too much to edit and not too much school work.