darthdeus

I've been using Ember Data in all of my applications so far, two of them are in production, another one will be very soon.

Yes there are some rough corners and the documentation is really not that great, but that's something you have to expect from a pre 1.0 release, especially in the case of Data where it's clearly stated that it's unfinished.

The "problem" with Ember is that it's nothing like Backbone, and Ember Data is nothing like $.ajax. It is no surprise that Ember makes you do things a certain way, which is different than most people are used to.

This sometimes leads to thinking that "Ember is broken", but in reality most of the times you're just doing it wrong. I'm not saying that everything is rainbows and unicorns. I'm not even saying that Ember is easy, there's a pretty steep learning curve.

What I'm saying is that once you get past a certain point, most of the issues will just disappear, because you'll know why things "appear to be wrong" and how to fix them :)

I really don't think there's any good alternative to Ember right now, and if you're not satisfied with Ember Data, go ahead and use $.ajax. Discourse does it and it works great for them.

SEEKING WORK - Remote

We are a small group of Ruby and JavaScript developers available for hire. Tell us about your product idea and we can design, build and deploy it for you. Find out more at http://sensible.io

Ember is awesome, you are dumb if you're not using it.

trololol?

This sounds like something from Star Wars ...

The best thing is of course learn by actually doing it. Your tests don't have to be anything complicated, basically what you're doing is writing down your own assumptions about the code.

Those can be something like "when someone upvotes on a comment, then the comment should have +1 score" ...

Another thing that might help you is watching someone actually do TDD, for which I can recommend Destroy All Software screencasts https://www.destroyallsoftware.com/

If you're into TDD and Ruby, then they're probably the best ones you can find. But if you don't like testing, then I would suggest saying away :) There's a free one that you can check out here https://www.destroyallsoftware.com/screencasts on the bottom of the page ... and see if you like it.

People talk about what's important to them. For some it might be proving that SVN is stupid (Torvalds?) and for others it might be proving that one editor is superior to others (SublimeText 2 obviously </sarcasm>).

The good thing about janus is that it also provides a simple framework for customizing your plugins, even if you change all of the original settings.

I've made my own fork (https://github.com/darthdeus/janus) and basically removed 90% of the default plugins and settings and repalced them with my own, but I still use it for the Rake task and nice directory structure.

This Developer's Life is probably the best podcast I've ever came across. I've been listening to it while running for the past 2 months, and yes I listen to it over and over again, because it is just that awesome.

I used to be really addicted to hardcore code completition and refactorings for Java in IntelliJ, it just felt like there is no other way. I had the same feeling when I was considering Sublime while using VIM, I thought there's no other way to edit text than the way VIM does it. And both time it paid off that I gave another editor a try :)

That is true only to some extent. Information can be valid or invalid independently from it's source.

If you have an idea in your dream, does that mean it won't apply in the real world? Even though the dream is nothing like reality, it doesn't inherently mean that the idea is wrong, it just means that it's not 100% right.

So you're judging and idea not based on the idea itself, but based on who said it?

There's big difference between integration and unit tests. If you're having trouble writing unit tests, it's probably because your code is too tightly coupled, making it hard to separate one part from another.

When you try to write a project with tests, not necessarily test first, it will enforce certain design. This is almost always a good thing, since you're forced to write modular code.