Life Laid Bare

[elfs]

I had a face-to-face interview today. That was interesting. It's one of those super-secret startups, and unlike the last one, it seems to be in a quest for a monetization strategy. The amount of detail the interviewer had searched for on me was quiet extensive, almost alarmingly so; I suppose I shouldn't be surprised, but I was. It's one of those "your life laid bare" moments, and although my life now is sedate and ordinary, once upon a time it was not so, and extensive searching will show up all kinds of bad habits once upon a time. And I've had longer than most of y'all to accrete a record of bad habits. I might be interested in them, they seem to have a cool product, but I'm not sure, with the girls at the age they're at now, if I'm ready to be putting in 12 hours days once more. I did that at Spry, and for a brief while at Isilon, but Kouryou-chan and Yamaraashi-chan are not quite self-maintaining yet. Besides, I like hanging out with my family.

One of the two I had earlier this week was very weird. The recruiter had a lot of questions about HTTP headers, especially those concerned with caching. To my thinking, that's not something you know, that's something you know where to look up, and then you segment your application server appropriately so that dynamic material is not cached, and static material is (a) cached and (b) served out a lightweight media server like NGINX or THTTPD. If you need your developers thinking about caching as they develop, it's either something you need right now (in which case, as a "long-established internet service" you're way behind) or something is exceptionally wrong about your architecture and you need help.

Still, that's the third interview this week. I got a callback on one of them; they want to do a face-to-face next Thursday, so that's good news. Also, tomorrow I have a phone conference with an ad agency, one of those places that has a lot of brilliant graphic designers and flash developers, but now needs more back-end work for their social-media aware clients. I think that would be a great fit for me: different clients every once in awhile, high pressure but with a financial backstop to alleviate the fear of collapse, and a variety of projects I can put my mind toward.

Also found one more resume' to send out today. That makes five resumes and four interviews. Well, good. I qualify for Unemployment Insurance for another week.

And curse Omaha for finishing Plants Vs. Zombies. Now that she's done, I've installed it on my desktop and that's got to be one of the most addictive little games I've ever seen. "Casual" gaming my left bollock.

Comments

[http://users.livejournal.com/_candide_/]

… or incredibly stupid and think that your software doesn't need to cache anything.

[duskwuff.livejournal.com]

And, hence, will never grow. At least, not for long.

[elfs.livejournal.com]

All of this is true, but it wasn't my original point. If your application programmers need to worry about what headers the application is sending out in its response object, your application is poorly segmented and your information architecture isn't worth the money you've spent on it. Your application should be designed in such a way that a programmer's awareness of caching is embodied in the framework, not in ad-hoc HTTP Cache headers he needs to look up for each segment and its potential cache status.

When someone says, "Tell me about HTTP Cache headers that help the browser cache things correctly," my response is that that's a configure-and-forget feature of your application architecture, and if you're forcing programmers to worry about it, you're throwing money down the drain.

[http://users.livejournal.com/_candide_/]

Oh, don't get me wrong, I totally agree with your original point!


^_^