The Democrats passed the bill in the senate 60-39, with 2 independents voting for, and all Republicans voting against. Then that bill was passed in the house with a vote of 219–212 with 34 Democrats and all 178 Republicans voting against it. This wasn't partisan, this was Democrats passing a bill without any Republican votes. The band-aids were to get moderate Democrats on board.
The bill passed in the Senate by 60-39 with all republicans voting against except for Jim Bunning who did not vote. With 58 Democrat and 2 Independent votes the Republicans weren't able to filibuster. After the bill passed the senate a special election to replace Ted Kennedy in the senate was won by a Republican, so the Democrats no longer had a super majority in the Senate, and so the decision was made that the house should pass the Senates bill as they didn't think voting on a house bill would pass the senate now that the Republicans had 41 votes which was enough to filibuster.
> The existing policy is a compromise that liberals signed off on to improve the conditions of the worst off
The only compromises happened between members of the Democrat party, between moderates and progressives.
> I agree with you that blaming Obama for a failure of leadership in this situation is borderline absurd
I agree that there are likely a lot of compromises that happened behind the scenes that we didn't see, but there has to be some ownership of that bill by President Obama. It was his marquee bill at a time when some Democrats were urging him not to tackle it, he had a super majority in the senate and the house. He signed it into law, he set the agenda, I think it's fair to hold him accountable for the outcome, even if it's not exactly what he wanted, it's still what was passed and if he didn't like it they could have scrapped it to try again.
Joining a startup is a high risk/high reward decision, and the biggest question you should have for them is where is the money coming from, and how long does the startup have until it needs more money given the current plan.
In addition to the salary cut, what are their expectations of a first employee? Will you be the only engineer, what are their expectations for hiring more staff?
Raising money is very hard, do these founders have an amazing network that they can utilize to raise cash?
Have they successfully started companies in the past?
If you were an investor would you invest in them?
Also keep in mind that everything is negotiable. Finding first employees is very hard, and as such you have a lot of negotiating power, especially if you're already employed and aren't in a rush to move.
I agree with this. What will be interesting though is to see if the wages of those jobs will increase because people won't want to do them, or if wages will decrease because there will be so many more people that aren't employed, and there may be a certain prestige to being employed to do any work at all.
I like building things, not just code. I think it's a sense of personal satisfaction from creating something where there was nothing and sharing it with others. Most of the time nobody cares, so it's always nice when somebody else likes it.
Lately I've been mixing relaxation music that's really just royalty free recordings of nature and royalty free piano music.
What bothers me is that all the data collection is on by default. If I purchase something I expect it to have my best interests at heart, if I get something for free I expect it to have the providers best interests at heart. Since you buy your computer, all data collection should be opt in. If Microsoft wants to give me a free computer, then make it opt out.
I was curious about this and took a look at the repositories. If you look at the Java repository and the Scala repository there seem to be a lot of additional folders as compared to the Haskell problem set. I'm sure Haskell would still come out ahead, but it's not clear that you can get an accurate picture from just looking at the amount of code as reported by github.
We went through a similar migration process and it sounds like we had different experiences. We started with the devs taking some time just to study and learn Scala basics then added the frameworks on top of that. I think if you go that way and you're using Slick > 2.0 it really starts to look like idiomatic Scala and everything in Slick looks like List manipulations. The other bonus is that a lot of the SQL generated perfors well and is easy to read.
We're a pre-series A company (4th engineer just hired) based out of NYC building a B2B product for the Architecture and Construction industry. Our co-founders identified an interesting opportunity in this space that we're trying to solve with a great Web App, some Machine Learning, and lots of data.
We currently use Scala (Spray + Slick), Java (Spring + Hibernate), Python, PHP, JQuery and Angular JS. We're looking to slim down our stack to just Scala + Angular, and Python.
We make heavy use of AWS.
We're looking for a full stack developer who is interested in solving problems across lots of domains and who wants to learn and share knowledge across those domains.
https://en.wikipedia.org/wiki/Patient_Protection_and_Afforda...