beoba

Having a good Saturday?

FYI Cody's is closed: https://secure.wikimedia.org/wikipedia/en/wiki/Codys_Books

It is also easy to love your work even if you aren't terribly interested in the industry. For example, urinal cake distribution sounds pretty awful until you think about the individual or team whose task it is to make it work as efficiently as possible.

If negative feedback is what drove you into wanting to be an entrepreneur, you may want to reconsider.

Given the style of the document itself, the language used in the header introduction ("Web apps that people actually want to use"), and the fact that every one of the "Previous Work" items has a gray "HTML/CSS" circle, I think/hope that she's trying to convey herself as primarily interested in front-end design work.

If I were going to pick out a particular thing that stood out to me, the use of Advanced "Apple Terminal" in a resume of any format would throw me off. It could just mean that the candidate was trying to convey eg "Terminal"/"UNIX Shell", or it could mean that they don't understand what the CLI really represents.

A bit nitpicky; it wouldn't be an instant drop, but I'd still look at the rest a bit more cautiously. Oddly enough I only notice a resume's "tools" section when there's something weird in it.

Not quite, the chart says they aren't quite pro at web browsers, but that they're used all day.

But, the chart says there is! THE CHART!

Eh, it works for them. If you don't have a desire for much stuff then it works fine.

I'm in a relatively spacious ~550sqft 1BR and I don't really know what I'd do with more space than that. However, unlike some of the people interviewed, I do get lots of light and it's in a nice area.

It's for controlling search results; blocking overzealous crawlers is a convenient side-effect.

robots.txt also blocks indexing of non-html files.

I think they just have an extremely slow server.

You might be interested in: http://taskwarrior.org/

I just use Yippy, since over 70% of websights should never be visited by anyone.

http://bitcast-a.v1.o1.sjc1.bitgravity.com/seehomenow/yippy-...

A fun pasttime is testing their awful filtering. It seems like they just have a list of blocked words. You can sometimes get the "clouds" box on the left to come up with some racy results. For example, "big booty" returns a link for "Round Asses".

http://search.yippy.com/censorship

answer: nope

The huge "MADE BY X" in the header is a bit overkill

My mother got this phone with this plan, it's not the best thing in the world (the screen is a bit too low-res) but for $25 I think it's a fantastic deal for a device/service which really isn't that noticeably different than what the 'high end' android phones offer.

I currently have a Droid Incredible with a $70 plan on Verizon ($75 after bullshit fees) and I felt like a schmuck for paying so much when I saw her phone.

I previously had a prepaid phone on Virgin and it worked fine. Ended up switching carriers just to get a data plan. I think I'll be switching back once my contract is up.

Would you have bought that book just to get that one answer? Would you have known the book even had the information you needed without Google's help?

What part is wrong?

(an ad for an html-based ebook app, with little explanation of how it works or what the tradeoffs are)

I'll gladly attach a tripod to a roomba if you're willing to pay me $15k to do it.

But for you, special price! $10k!

What does this thing do that makes it worth as much as a mid-range Ford Fiesta?

Neat, everybody loses. Now that's thinking different.

My own random thoughts/opinions on various things touched on in the article:

When working on any API, it's often useful to show it to someone who will likely be using it. Getting a second opinion will help you quickly determine where it needs improvement. It's best to do this early on, lest you need to start over.

If you're doing a lot of disk access and you have control over it, try to make your reads/writes as large and sequential as possible. This can make a huge difference if you're disk-bound.

For choosing a worker count in a threaded queue, the number of hardware threads[1] on the system would be reasonable. However, if the workers are doing frequent disk reads/writes it may actually end up being better to reduce the number of workers to reduce thrashing, though in a perfect world the disk firmware would help negate this (is that the case these days?).

I generally just worry about documenting outward facing APIs and any parts of the code that are inherently dense or otherwise require background information. More docs can't hurt, but I've found that things change quickly enough that immaculate docs are often out of date shortly after their completion. On that note, I also like to keep docs as close to the code as possible, so that it's easier to keep them up to date when the code is being changed.

Something I picked up recently that I yet don't do as often as I should is to design each module as though it were an independent library with its own API, to the point that a working application could be written against that API. At the time this mode of thinking sounded extreme, but I've recently been trying it and it's turned out to be quite useful for enforcing module boundaries and allowing easy testing.

[1] boost::thread::hardware_concurrency()

At this point, their "one trick" is advertising, but that's everything as far as the internet is concerned, and everybody wants to buy some.

Sure, someone might switch search engines (I have), but now they've got a huge market of third party sites running their ads for them, too.

Oh, forgot to mention: Savings accounts have a 6 transaction per month maximum (as mandated by the Fed). If you exceed that, you'll be paying fees. So if you're going to be doing a lot of frequent deposits/withdrawals, you'd want to use a checking account.

Just feeding off of drama. Over what, exactly? This is equivalent to posting about a Wikipedia edit war.

I'd have figured closet marriages would be less common now, especially in the bay area, excepting senators/televangelists I suppose. Or are you referring to adoption? Ugh kids.

Or go gay. You know. Either/or.

Serious point though: It's relatively easy to take risks on your income when you're half of a DINK family.

In my case, I recently just put a repo on my own site. I access it over ssh, and it's visible over http using gitweb. Works fine for my hobby projects, and it's under my own control.

There've been approximately 50 million of these over the years; it's a commodity.

Really, if you're looking at open source, I'd recommend joining an existing project that you find interesting. Nothing prevents you from making a site based on such a project, and they might even like the exposure it gets them.