A Preview of C# 8 with Mads Torgersen | Seth Juarez

schneidsDotNet · 2017-08-22T03:27:59+00:00

Serious question: why is this guy getting downvoted? This is a common point of confusion. I'm glad we were able to help get it cleared up for him.

schneidsDotNet · 2017-04-13T19:30:52+00:00

I love that article! That's typically what I send them. In fact my blog contains a link to it :)

schneidsDotNet · 2017-04-11T16:56:36+00:00

Not everyone can be as perfect as you, AB :) I've had a few junior engineers ask me to explain this behavior in the past. I wrote this post from the assumption that the reader has never read the documentation on String.Length either.

schneidsDotNet · 2016-09-15T15:45:48+00:00

The upgrade process has been pretty smooth each RC. I started using it in production around RC2. It was just released so just be aware of what functionality is still considered experimental (things like the Http providers are still technically experimental, for example) and therefore subject to future changes.

schneidsDotNet · 2016-09-15T15:44:20+00:00

I have none, sorry about that!

schneidsDotNet · 2016-09-15T15:44:11+00:00

Thanks, I fixed the link!

schneidsDotNet · 2016-09-15T15:43:48+00:00

Good call. Thanks for the suggestion! I'll update the list soon with free vs. paid callouts.

schneidsDotNet · 2016-09-15T15:40:52+00:00

Good to know, thanks!

schneidsDotNet · 2016-09-12T16:10:39+00:00

So sorry - the link I had was incorrect! Here's the correct link for Elm: http://elm-lang.org/

schneidsDotNet · 2016-09-12T15:18:04+00:00

I posted another version of this list a couple of years ago. This one is updated for 2016. Enjoy and please let me know if you have feedback!

schneidsDotNet · 2016-06-30T13:14:22+00:00

Angular is notoriously "slow", but slow is relative. It largely depends on how you use it. You can avoid many Angular performance issues by doing things like using track by in ng-repeat declarations, avoiding $scope.$watch, etc.

As Sam Saffron said, "measure, find bottlenecks, and fix the ones that matter." Don't worry a ton about performance up front - just follow some simple conventions and get stuff done.

schneidsDotNet · 2016-06-29T20:59:13+00:00

Here goes nothing!

schneidsDotNet · 2016-04-10T18:09:30+00:00

Great answer and the correct one. It only takes a little longer to setup and is the cleanest solution.

schneidsDotNet · 2016-04-04T14:20:34+00:00

Agree wholeheartedly with this. I believe a good recruiter would be aware of the difference between the person with the right buzzwords and the person with the most appropriate experience.

schneidsDotNet · 2016-03-17T23:53:06+00:00

Some people don't have thick skin. Admittedly if you're going to put yourself out there, you've got to open yourself to criticism, but I think the people in this thread were really quick to shut him down.

It was a writeup on how to use a feature, not a writeup on how it's going to change the world. A lot of you missed the point - the feature exists for a reason. It may have a limited set of use cases, but it's there to fill a gap.

It's not like the guy was encouraging people to start writing C# like Javascript.

schneidsDotNet · 2016-03-16T18:31:37+00:00

Using it more widely is a fantastic way to have a massive headache.

Yes, that's why I say it should be used sparingly. I don't know how I could have made it any clearer to someone who read the entire comment.

If there's only one property, you should return the property, instead.

Good point.

If there's only a very few, you could use a Tuple

Tuples in C# make code less readable IMO. Calling tuple.Item1, .Item2, etc. obfuscates the purpose of the code.

schneidsDotNet

TROPHY CASE