Jon Skeet

This session will look at specific aspects of the (C#) code - particularly mutability and efficiency - but more importantly, we'll reflect together on the nature of personal projects and how we can use them to become more effective in our professional coding lives.

Some developers write date/time-sensitive code without worrying about it — but also without thinking about it. Some developers write date/time-sensitive code and worry about it a lot because it's hard. In this talk, Jon will provide some guidance to help you write date/time-sensitive code with a reasonable degree of confidence, and test it. We'll look at the speaker's Noda Time project as one tool to make your life easier, but Jon will also explain how you can improve your System.DateTime code too.

Stack Overflow #1 ranked contributor

Noda Time is an alternative date and time API for .NET. It helps you to think about your data more clearly, and express operations on that data more precisely.

In this episode of The .NET Core podcast we talked to Jon Skeet about NodaTime, API design, Time Zones, and the ECMA Standard for C#.

The biggest feature of C# 8.0 is undoubtedly nullable reference types. Rather than trying to rush through all the new features, in this talk I'll just talk about this one. What's the point? What's the syntax? What's should you expect? What might be unexpected? I'll go into all of this and more!

DotNext Moscow

C# 8 New Features by Jon Skeet

Jon Skeet talks about C# 8

C# 8.0 is coming up! Not just nullable reference types and asynchronous streams, which will get much coverage elsewhere in the conference, but also recursive patterns, switch expressions, ranges, default interface member implementations and more. We’ll look at all of those, and also at some of the things being worked on for future versions of the language.

This is the primary repository I work on within Google... but there are plenty of others too, almost all .NET.

Versioning remains one of the trickiest and under-discussed aspects of software development. Shipping 1.0 of a library or framework can be easy compared with shipping 1.1 and worrying about your existing users. "But semantic versioning!" you respond... yeah, not so much. It's easy to say "No breaking changes within a major version" - but what does that mean, exactly? And what does shipping 1.1 or 2.0 mean for anyone who depends on your package? How can we avoid an impending versioning apocalypse? This talk will use C# and .NET for concrete examples, but the questions raised are applicable - with potentially different answers - to all platforms and languages.