I work on a team with the same size as yours. Although we do not all sit in the same room, we still do code reviews. Since we are small we are not the most critical on style.
I am a big believer in code reviews especially starting early with a small team. This would set the culture from the beginning because it is harder to bring that in later.
However, if you have good test coverage then you can test for that stuff and get a similar experience. For example, if a test break then you know your variable is not a number anymore when you need it to be.
This is pretty cool but sucks living in DC because we do not have equal representation. We just have a shadow representative who only has a vote in committee when democrats have the majority.
The worst part about all of this to me is that most people in the country do not know / do not care that 650,000 people that live in DC do not have fair and equal representation like everyone else. Wyoming has about 70,000 less people for the whole state and they have 2 reps and 1 senator. A little infuriating.
Heard about this and seems like everyone and their mother are signing on. This is one of the reasons why I asked the main question is because I want to fully understand what the business case is for using Docker.
>>No one is obliged to give you money. Finding a business model that works is your problem, not your customers.<<
This struck a chord with me and is exactly the reason why Hollywood and the Music Industry are flailing. They are trying to continue their business model that worked for so long into this new day and age. Adapt or die essentially.
Agreed. We don't and shouldn't follow. We should continue with developing currently existing and new technologies to loosen the worlds dependency on oil.
"The JavaScript Problem is two fold: JavaScript sucks, but we need JavaScript."
Can we just got over this JavaScript sucks issue. We get it. There are a lot of people who hate JavaScript but we know the issues so start using JS the proper way.
Yeah that slide is a little confusing because they messed up the second step. JS Facade is supposed to be where Dart Facade is and vice versa.
Also, Angular 2.0 is going to be written in TypeScript (which will be compiled to plain JS) but you can use ES5, ES6, TypeScript or Dart depending on what you want to use for your application.
I think that the Angular team has not decided on two-way data binding yet. They maybe keeping it and I just asked this question on the reddit ama that they are going to do over at the /r/ngconf subreddit.
At ng-conf in the opening remarks they talked about how they plan to have people migrate from 1.X to 2.0. From what I understand if you start using the new router in Angular 1.4 then that will be the router for 2.0 which will allow you to use Angular 2.0 with 1.X components as you slowly migrate each 1.X component to 2.0. I think this is pretty reasonable.