Our corporate WebSite runs on Clojure and Google App Engine | Hacker News Reader

Our corporate WebSite runs on Clojure and Google App Engine

hackers-with-attitude.com

12 pointsfogus17 comments

That headline didn't kick me much (well, so you can build a website on clojure, duh!) but while clicking through that site I was fascinated by their writing about the company philosophy.

http://www.freiheit.com/tag/Jobs#ag9mZGN3ZWJzaXRldGVzdDFyDQs...

The english translation is horrible but here some highlights from the Jobs-page:

* The day begins at 9:00AM, not later, preferably earlier.

* Release dates are never(!) shifted.

* We believe in the "Broken Window"-theory. Companies degenerate, too. That begins with a paperclip laying around. Consequently every employee must empty their desk before they leave.

Along these lines there's this cultish subtone in all of their writing which is hard to translate. Reading their blurbs gave me the chills like no other company description I've ever read. Definitely has a "zombie B-movie" taste to it.

Yuck!

I don't really have a problem with that. I'm self-employed most of the times, but during the occasional "sortof hired" periods I like to take work ethics seriously. And I definitely don't mind a nice quiet clean office - again, not at all something I'd do on my own, but I definitely wouldn't mind such a policy. There is a bit of zen in 5 minutes of cleaning up at the end of the day.

Does anybody actually like tag clouds? I've always wondered.

No, though I think there may be a good concept in them somewhere.

I've never even clicked a tag cloud.

I clicked a tag cloud once. It wasn't that great.

The only time I've ever liked them was for finding trends when working with analytics.

No, but marketing requires them in order to be buzzword-compliant.

I assume they have a cron job running to keep the site alive - Google App Engine for Java has a nasty habit of putting your app to sleep and then it takes 20 or 30 seconds to wake it up (at least that's what happens with JRuby - I don't know about Clojure).

Is it me or is it really slow?

I'm curoius why everyone resizes images when they're uploaded.

I think the better way is not in any way changing the uploaded file, instead resizing it when it's actually requested by a client. This way, your pages can ask server for whatever actual size they need in the moment instead of setting image size once in stone. Like, if you've uploaded kitty.jpg, you can then ask for kitty_120x50.jpg or kitty_300x.jpg or kitty_x200.jpg (with missing dimension being calculated to preserve ratio).

If course, resized files are stored along with the original to avoid costly resizing process each time. If there's already a copy with required sizes, it's served really, really fast.

The upload process is already time consuming. Doesn't hurt it much to include the resize processing with the upload. People want the images to appear quickly every time. Disk space is cheap and you want requests to images to go to the regular file serving (.jpg or .html) rather than through dynamic serving (.php or .aspx) to reduce load on the server.

It's not about the time it takes to resize a new image, it's about the time it takes to change _all_ of your images when design changes happen.

a preprocess-only system means that you need to have a migration system in place, and it means that your designers have just a little more overhead to make tweaks. It's manageable, but producing the images on demand makes for a more easily changed system with fewer moving parts.

I think amazon.com does something like this. I read an article that dissected their product image urls to explain how their image service worked but I can't find it now. If I remember correctly the service could resize/rotate, add sale "stickers," and a bunch of other stuff.

EDIT found the article: http://aaugh.com/imageabuse.html

Yeah, adding stickers on the fly is also the way to go.

This is one of those issues where I have an opinion but I honestly don't care that much either way. If the place I worked had one method in place I'd probably do that.

The nice thing about doing it on upload is It allows you to offload the processing to a job queue so you don't take a huge performance hit. (This is what I've done in the past). If you're resizing to sizes not relative to the original it also gives you the ability to maybe do some editing/cropping to make sure the resized images still make sense. Digg has a tool like this for avatar images.

Reply on news.ycombinator.com