Data binding solves this generically. It allows you to build state machine trivially Stuff like angular and ember do this amazingly well though it would be nice to have a nice standalone library. (no idea if one exists)
We just switched from backbone to angular. The thing that sold me was data-binding. You could write your own with backbone but it's done so why bother. Also the code reduction was about 1/3.
Jiggy I honestly think I remember you especially if you played under this exact name. Anyways I was on the other side as a core myg0t member for a while. It was fun, and why I started programming.
No, but it certainly looks interesting. According to the collective intelligence that is the internets current tDCS products cost upwards of $600, so this might be an interesting alternative.
Yes I am aware. I also noted that I am paid decently, maybe I should have made it clearer that I am paid decently for FL which is most certainly not the same in NY.
This. I'm 26 and I had a decent paying software job in Florida. But I wanted to move up to New York so I convinced my job to let me work remotely. I made the move 2 months after they allowed me to work remotely. I sold a bunch of my possessions, made sure everything could fit into my car, gave away my furniture to my mom, and did the entire move for around $800 of my own money. (I had a place to stay when I got up here)
So I agree. These people sound foolish. It is entirely possible to move but that means getting rid of shit and people do not want to get rid of their shit. It's a bit sad really.
Yes, I must second this. The quality of conversation on HN is simply put... amazing. It boils down to the people that you choose to associate with.
Think of your Facebook friends. I seldom talk to my "friends" there so it would make sense that the content they produce is usually of very little value. Most times Facebook makes me aware of internet memes and that is about it.
With all of these companies shutting their doors, I think it would be fun to make some sort of data graveyard. A place where you can visualize your dead interactions.
I love testing I just find using it in the right way can be very tricky sometimes. Especially in a team setting where there are weaker members than others.
When you work with a team of people that didn't understand what to test you end up with really bad tests that add very little value. Do you delete those test? Write sane ones?
When you end up with a legacy code base where doing something like functional UI testing is easy but doing unit testing on the actual code is almost impossible, do you even attempt to unit test it?
If you see a piece of code with that must be rewritten, but unit testing it costs too much time, do you simply start writing tests what you think the assumptions were and then just go about with the rewrite?
In the end I see a huge value in testing what you write, and being automated is preferred. My problem becomes picking up something else that was clearly done in a misguided fashion and reliably rewriting or refactoring it. I know there are probably some guides/books out there that demonstrate it so any suggestions are welcome.
For a hobby project, it is awesome and impressive. Things like this light a fire under my ass, and remind me I need to get cracking and start something awesome like this.