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.
I'm not sure why this was posted but I will wager a guess it's the high ratio of women to men. So... good for them! You don't see this a lot and it's a bold statement. Rock on.
I don't get the "Beautiful Stories" section. All of the articles look pretty much the same. Same full-width image peekaboo parallax banner thingy at the top, same font, same look.
This article (https://medium.com/beautiful-stories/66e87553d22c) is a hodge-podge of design decisions. The way images are displayed is a mess: some images float next to text, some float next to text with a caption next to them, some images are centered, some images have quotations in them. To divide sections of text, sometimes there are hr's, sometimes there's a single line with a little loopy thing, sometimes there are parallaxy headers.
Medium may be easy to use but if people think they can click a few buttons and pop out a "beautiful story" they are mistaken.
Call me an old-timer but I would rather just read text without a bunch of stuff in my way.
If you're looking for something more photo-driven, I'm working on a thing called Exposure: https://exposure.so/invite/hn (opening this week but we'll invite folks from that link ASAP)
MIDI was never intended to be playable by people. It's just a protocol, you can do whatever you want with it. So saying that this is "impossible" doesn't make any sense.
That said, this music sounds atrocious when you run it through a computer, it'd sound better if it were spread out across multiple instruments, but whatever.
Whilst clicking through the related youtube links, I found a 3D representation / rendering of one of these tracks (instead of the 2D one shown on most videos), with the notes cascading downwards onto ten rows of keys - gives a bit more perspective to how they made it.
This isn't very useful, unfortunately. There aren't any requirements for this. All it says is "come up with a design!" This is about as useful as saying "Write something about any subject!"
Has there been any pre-discussion on this? Where did this come from?
