Pair Programming with Microsoft's Damian Edwards - Retrieving and parsing JSON with .NET 6

Scott sits down with Damian Edwards to code C# 10 and .NET 6. They learn how to call a new Microsoft Docs API to retrieve data that was removed from a previous API. We'll see analysis of how to get Json, how to breakdown a problem, we'll talk about 'YAGNI' (You aren't gonna need it), analysis paralysis, and when something is done. We'll also see the importance of iteration, asking questions, and feeling empowered as an early in career developer!

[richardwhitfield]

Love this format! As someone transitioning from another industry into software I’m definitely ‘early in career’ in the sense that I’ve never been paired with anyone with experience to learn from. It’s great to see how you tackle problems so I hope other people are also enjoying this!

[thatcreole]

This…. And the shorter recap of this problem that you did later, are imo the best videos you’ve ever made. More of these please!

[ukWaqas]

This is amazing. Thank you Scott and Damian for such a great session - the commentary provided around the coding was invaluable. Like you guys kept alluding to, there are 1001 different ways to tackle the issue, and it is great the different perspectives you have provided. Please keep these pair programming sessions coming Scott! And thanks for doing it in .NET 6 :)

[kishore-ravi]

It is a great session, showing how seasoned developers think while writing code! There are lot of learnings to consider while we discuss in our teams.

[JanWestin]

Great format! Been coding for 20+ years and still enjoy the process of iterative problem solving

[awright]

Great show, I liked the emphasis on multiple ways of doing things, and showing off some apis that many of us probably weren't aware of! Would love to see more like this!

[ericdc]

It was fun to watch the thought process on this.

I'd copy the JSON, and use "paste special" > ""Paste JSON as classes". Deserialize the JSON into the root class which would have the count and List<Episode> to work with it as a typed list.

The easy button is to deserialize into <dynamic> and you could type item.episode.title.

[leonardpera]

This is great content, Scott! I'm looking forward to your next Pair Programming session - it is really interesting to hear the taught process when tackling a problem. Thanks!

[PinheiroJaime]

Really interesting to see pair programming with 2 super senior guys!

[--Eric--]

I'm looking forward to watching more episodes like this. It was great listening to you and Damian talking about different ways to do things. Thanks 👍🏼

[vackoo]

Absolute Gold, loved the session. One comment from Damian I could closely relate with was about the failure modes. Most of the tech knowledge that is burned into my long term memory is actually the pain points that I have experienced while trying to figure out a particular issue and actually helped me in the long run.

[goodjesse]

This format is a rarity, also really liked Damian Edwards pedantic nature. I feel like too many developers don't care about the fine details anymore...

"Paste as Json" makes modeling super easy, and honestly would save so much time, even if you then simplify the model to just what you need.

[dim-d]

Great format! I hope you do more of these! Love it!

[bogdanbanciu]

This is great, would like for this to turn into a series, i would show this to all students in CS

[Noceo]

This is so awesome. Thank you Scott and Damian! Please do more of this...

[ManderO]

yo, please episode 2, i loved this so much

[seldomseen_]

Scott, great stuff as always. Hope to see more of this format.

[petesral]

Great content, especially the highlighting some of the real world challenges facing developers.

[dhugalleverett]

Great to see a real discussion around iterations and why it's OK to get something working simply then iterating over it IF and when required. Async, caching etc may be better but they all introduce complexity and often you'll find yourself working against other constraints (deadlines etc.) and it's normal to make trade-offs and perhaps not initially develop the "perfect" solution for every facet. It's also OK to look at something developed in this kind of scenario and question why it didn't take advantage of things like async but don't be guilty of "Drive by Design" where you evaluate a given solution in a silo without an understanding of the constraints that were in place when it was developed.