Json Parser from Scratch in C# using TDD

preview_player
Показать описание
An example of writing a json parser from scratch in c# using test driven development.

#csharp #json #parser
Рекомендации по теме
Комментарии
Автор

I’d like to see you tackle performance optimisations and add some benchmarks, for the viewers benefit more then anything.

I had to implement one that was quite cut down feature wise that had zero heap allocations. It was for 100Hz message logging which is well beyond what the average developer would need.

It’s shocking how many allocations even the optimised Utf8JsonWriter does under the hood, let alone in the standard JsonSerializer.

jamesmussett
Автор

Love this kind of video. We can get a glimpse of how other devs think. It's very interesting to see where we think alike, where we don't. I learn a lot with it.

moke_codes
Автор

Loved the video, looking forward to seeing more

TheInkSpoots
Автор

Looking forward to seeing a formatted version, this gave me some ideas though. Nice sharing!

nove
Автор

What exactly you craete for this,
this is which one is console app and which one is class library can you please tell me how can i create json parser
where i pass my model for the json and i get back that values

DurgeshMarrathe
Автор

Hi there, I hope you see this comment because I do have a quick question: Do you consider this approach as fast as using something like IronPython and deserializing and flattening the files using Python scripts? I'm thinking of passing streams to the parser but was wondering how efficient it would be to go character by character for longer jsons. Thanks for the amazing insight and video! Also if you would like to get in touch I can also provide a CSV parser in exchange for some info, maybe you would like to make a video out of something similar

natha
Автор

What about talking about active directory logins

abuzeromohammed
Автор

At 7 minutes in I am thinking your bool test will pass if you pass "test", "tree", "trap", etc.. I'm curious to see if you fix that by the end of the video. I usually write unit tests for sad path first.

th_CAV_Trooper