micah rich
working
this is where the magic happens.
i was fairly productive today. researched branding ideas, made some mockups, and sought out new clients.
after my thoughts last night, i made a few gifts for a few people. just to let them know how i feel.
today i had a rousing twitter conversation with my new friend eric. it was pretty funny, and normally i wouldn't really think to mention it, but two good things came out. first, it got me to fix a few things that were broken on my blog. nothing important, really, just stuff like log in and log out capability, and new user signups. but second, he told me about this post he made in his own blog. he had nothing but flattering things to say, and even the fact that he wrote it speaks a lot about the kinda dude he is. and eric, since i'm pretty sure you're reading this now, i just have to say: thanks, man. to get such high praise from somebody whose name i knew before i met him feels pretty darn good. i hope we can return the favor someday, help him out somehow, too.
last thing. i signed up for a pro flickr account today. it's cheap and gives me unlimited, high res photo storage with unlimited bandwidth for _half_ the price of my limited, medium bandwidth hosting. i figure that way, i can not only display the image low-res, but always have a high-res archive stored.
now that i've payed for it, i naturally want to _use_ it. and i was thinking. so far, i've got three exports for every photo i want to post. a low-res one for the blog, a high-res one for the book, and a different high-res one for flickr. this seems silly. i have a better idea.
particularly after going thru all the crazy, old, duct-taped code for my blog this afternoon, i started thinking that i could use flickr as both my archive and my backend. all i'd need to do is make a blog that could fetch the information from flickr, and i'd have merged 2/3s of my steps into one. and since i can go directly from lightroom (my photo program of choice) to flickr, that'd be super simple to update.
what's that mean for you? hopefully nothing. i'm gonna work on it in my spare time, and once it's ready, i'll switch over. i'm gonna try really hard to make sure commenting, RSS feeds, and generally viewability aren't at all compromised. i'm probably gonna get rid of the whole user system, that was sort of a failed experiment anyway. but it'll be a fun side project, to see how easy i can make it for myself and how quickly i can do it. that's all. goodnight.
working
this is where the magic happens.
i was fairly productive today. researched branding ideas, made some mockups, and sought out new clients.
after my thoughts last night, i made a few gifts for a few people. just to let them know how i feel.
today i had a rousing twitter conversation with my new friend eric. it was pretty funny, and normally i wouldn't really think to mention it, but two good things came out. first, it got me to fix a few things that were broken on my blog. nothing important, really, just stuff like log in and log out capability, and new user signups. but second, he told me about this post he made in his own blog. he had nothing but flattering things to say, and even the fact that he wrote it speaks a lot about the kinda dude he is. and eric, since i'm pretty sure you're reading this now, i just have to say: thanks, man. to get such high praise from somebody whose name i knew before i met him feels pretty darn good. i hope we can return the favor someday, help him out somehow, too.
last thing. i signed up for a pro flickr account today. it's cheap and gives me unlimited, high res photo storage with unlimited bandwidth for _half_ the price of my limited, medium bandwidth hosting. i figure that way, i can not only display the image low-res, but always have a high-res archive stored.
now that i've payed for it, i naturally want to _use_ it. and i was thinking. so far, i've got three exports for every photo i want to post. a low-res one for the blog, a high-res one for the book, and a different high-res one for flickr. this seems silly. i have a better idea.
particularly after going thru all the crazy, old, duct-taped code for my blog this afternoon, i started thinking that i could use flickr as both my archive and my backend. all i'd need to do is make a blog that could fetch the information from flickr, and i'd have merged 2/3s of my steps into one. and since i can go directly from lightroom (my photo program of choice) to flickr, that'd be super simple to update.
what's that mean for you? hopefully nothing. i'm gonna work on it in my spare time, and once it's ready, i'll switch over. i'm gonna try really hard to make sure commenting, RSS feeds, and generally viewability aren't at all compromised. i'm probably gonna get rid of the whole user system, that was sort of a failed experiment anyway. but it'll be a fun side project, to see how easy i can make it for myself and how quickly i can do it. that's all. goodnight.