dvcc

Apparently when I laugh I show disgust, no wonder I'm no longer invited to dinner parties! I partly joke, but it did do a good job at distinguishing different expressions but maybe not assigning them to the correct one.

How would we ever know that the autopilot acted correctly? Should companies be required to release logs after every crash when a car is in autopilot? Seems fair.

This was entirely defensive and self-serving on behalf of Tesla. It's a general PR release, companies do these all the time. What made this so special?

Unless I am missing something, this didn't really teach me anything? It's more of a magical emoji black box.

On a sidenote, Codemoji broke my back button (:() and seems way over-animated for a simple three box form.

This may not be the greatest idea, and may not even be realistic but are there not cash advances on a pending/future lawsuit? I imagine the terms are not friendly, but it may be more successful than a GoFundMe campaign if he becomes desperate enough.

I wasn't entirely convinced about why the coffee is better than the cold brew method. They both return different flavor sets, and taste at that point is completely subjective. A bad comparison would be like saying orange juice with pulp is scientifically better than orange juice without pulp.

I was just saying his idea of what differentiates a mock from a fake was right!

Oh god mocks/fakes/doubles. The best answer to that probably comes from The Art of Unit Testing as explained on SO: http://stackoverflow.com/a/33333064/2136440.

In short yea, you're right.

There is something other than Moq? I'm only partially joking... But I really haven't found a reason to switch from it. I find the syntax easy enough and if I ever come up on a problem the question was probably already asked.

There are a decent amount of yeoman generators that allow selections between the different layers. Plus I feel like beginners (certainly for me at least) generally struggle with this heavy boilerplate anyway.

I hate to sound negative, but what does it offer over yeoman and the individual generators out there? If I use a Mega Boilerplate setup, I lose scaffolding post-setup stage, so what do I gain?

A working vendor-compatible HL7 implementation is certainly magical.

It's still debt, it's not as if the money is not owed it's just debt that has no legal repercussions for not paying. From my understanding at least.

So really he saved them from harassing phone calls, not really the money itself.

Damn I like to complain not code, that's why I'm on HN right now.

Entirely aware they do, even watched the relevant part for the csroj piece today; however, not everyone has time to sit through the stand-ups. And when the discussion with the community blows up on Github things don't look as promising as they once did. Sorry I don't share your same sentiment, but I am seemingly not alone in how I feel.

I get that they have gave their reasoning (all those links were already grayed out), but its much more an announcement than it is a discussion. In the end though, it feels more like an executive decision than a collective push.

Hell, I don't care if its XML/JSON/XAML but I don't want to go back to MSBuild/CSPROJ.

The changes were announced ahead of time, but within the discussion there hasn't really been actual consideration around not switching back to MSBuild. They've been pretty set on the it within the Github issues (#1433) and haven't provided too much reasoning for it outside of tooling. Of course it's not that alone either there is just a bunch of confusion around it right now on the direction of .NET Core.

From one of the end comments:

> If you want to work out how it should be made and be in the design team that talks about it... please do. [Link to MS Career Page]

Somewhat off topic, but all the excitement and hoorah surrounding .NET Core is beginning to fade for me.

It seems that the product is beginning to turn into .NET 5 (Core) instead of the original intentions of leaving behind the legacy chains.

Between the switch back to MSBuild, RC# breaking changes and the promise of even more breaking changes post-release, I've become a little disheartened.

Change in itself isn't bad, but .NET Core was supposed to be about open communication, and the later changes were never discussed within the actual community, instead it was decided by MS alone.

Hell, in this article, it took multiple attempts to get it configured when its in the release-candidate stage. No idea where this was going it was more of a rant than anything apologies for anyone who actually read it.

I am not sure where you live but this is pretty common in the north east (ShopRite etc.). To me though, I feel like there are misaligned incentives when employees pick food vs. the customer picks the food. Why should the employee care if the bread is going bad tomorrow instead of a week? The added time-savings just don't offset that concern for me.

Although interesting, it read more like scattered excerpts from my undergrad set theory textbook except without symbols.

I think its evident by the NYTimes comments, this probably won't be the easiest article to understand for someone with little background on the topic. The great thing about the books on the subject are they essentially start from nothing.

You can basically do anything at all with it, including include it in a more restrictive licensing setup. The only constraint is that you must include the original license/copyright notices.

https://tldrlegal.com/license/mit-license

We all knew where the story was going after that!

I am going to preface this with the a small piece of information, I work in corporate America.

From my perspective, I don't quite get a lot of the points. No unit-tests? Most code bases don't have them. Cucumber tests? You're already ten giant leaps ahead of most products out there.

Code in disarray? Used to it for every single project I have to come into. Factories/viewers at least there is some semblance of structure!

False corporate goals? It's a company, I expect nothing else from them.

Weird North Korea chants? That's just weird as hell.

Again, I don't work in SF or NY so it's hard to know what exists within startup culture, but to me all of this just sounds like the norm. There is much less importance placed on decent code then there is on just getting something out.

How can visas possibly be granted to employers who employ over half of their workforce on H1Bs? How does a provision not already exist to combat this?

Did the update today and gave it a try but it looks like it still complains on the imports, but JSX parsing did still improve at least!

Free during public beta... and then what? Rather just know the pricing model outright.

I think that is just for the NTVS plugin but VS itself still does not: https://visualstudio.uservoice.com/forums/121579-visual-stud...

So it looks like they still won't be supporting ES6 module imports, which just screws everything up when trying to do anything with js. Sad to see.

Do you not hold that more on your team though and less on the communication style? To me, if I know that someone else might have some information that would contribute to the discussion I'll include them.

That feels like it would be more on the individual team members not knowing when to reach out, more so than the in-person meetings causing a remote/local gap.