mcmire

I deactivated my account. It's still around, of course, and I can log in again when I want. But I didn't want the distraction anymore. I found that checking the feed on my phone became an automatic habit for no observable benefit. I don't mind so much the whole privacy thing, because I don't think Facebook is that evil. Your information is public somewhere, and you're being tracked by someone, whether you like it or not. And this happens outside of the internet -- it's how business works. So it's not a big deal to me.

The usefulness of Facebook is a big deal though. And it's just not useful anymore. My friend group tends to be pretty selective, and is mostly made up of people I know and interact with in real life. So I do that instead.

Thanks for this, I needed a laugh today.

I think that was a reference to MacVim, maybe?

Did not realize it used math to simulate paint hitting the canvas like that! I like the research that went into this. Pretty neat stuff.

Omigosh I remember this. This is ooolddd but so cool. I used to mess with the creatures by dragging around the joints and such and then get freaked out when their movements changed from being lovely and life-like to being grotesque and unnerving.

Only runs on Firefox, it seems.

Anyone else get a JavaScript error when they attempt to load the demo?

"Who thought you could have fun with the Germans?" Really, Kara?

Anyway, obviously there were a couple of mistakes by the speech recognition, and they were taking care to speak very clearly, but still, I'm impressed. The future looks bright.

This makes sense. I don't write a lot, but when I do, I actually use Evernote on my phone or TextEdit on my computer. I find the smaller the space to write in, or the shittier the tool, the better. Basically limitations are actually a good thing. You're not compelled to write anything beautiful, and so there's no pressure, and you just write anything that comes to mind. You can always edit later...

Why are they doing this? It's too late. No one is going to want to make Bitcoin transactions through a US-based company now because you know the Fed is going to start creating all sorts of lawsuits unless people follow the rules. I have zero Bitcoins but if I had any I'd play it safe and put it somewhere overseas (or if I did put it in a US-based company I'd want to make damn sure they were backed by an overseas bank).

Wonder if they manually curate these lists or if they initially populated them with some sort of machine learning?

The problem with dependency injection in this manner is that your test code is using a fake class that's injected while your production code is using a real class.

This is fine if all you want to do is unit test your classes. That's beside the point though -- I would posit if you're bolting dependency injection onto your interfaces just to make your tests faster, you're not doing it right. Instead, bring that dependency injection into the forefront: to the constructor. Yes, this means to make an object, you'll have to make another object first, both in your production and test code. But now your interface acts the same way in both places. If this sounds very Java-like, well... maybe Java got it right. (There was an article on the Twitter blog in the early days about this but I can't remember where it is now...)

Of course, this is going to introduce complexity and now you have to decide whether that complexity is worth it.

The problem I have with these tools is that the diagram it produces is really not that great. I guess it tells you what models you have, the columns they have, and whether a model is tied to another one... but not much else.

Here's the thing: I already know how many models I have (I just look in app/models) and which columns back them (I just look in db/schema).

The thing I often want that 1) ActiveRecord doesn't give me and 2) I haven't seen in any tool yet is a diagram of the relationships. So I have two models, A and B, and A has many B. How do you diagram that? Typically I've seen arrows: B points to A, with the words "has many" written next to it. The thing is, if I have 30 models in my app, I'm not going to be able to read this at a glance. Words are too small. Diagrams are meant to be rough pictures.

The way I visualize this in my head and consequently diagram this on a whiteboard is, multiple instances of B point back to A. It's easy. If you have a has_one instead, then only one B points back to A. Makes sense right? No one does this. I often wonder why.

Is this the same guy who wrote head.js?