Видео

typeof(string)

True to the core. BDD can acts as source of truth

What if I need to navigate between pages non sequentially? Aka: Page 1 -> Page 6

So @9:30 you mention you might want to hash to continuation token so as not to expose internal id's. But I can't go back from the hash to the actual id unless I keep a list on the server. Also in the example you use an order integer Id, but what when I want to page through a filtered set of results that messed with this integer or any orderer key values. The way back is even harder. Let's assume SQL. Continuation could be just Id > continuationToken, but going back you would need to do Id< continuationToken and add an order by on the Id column with of course a limit/top restriction. This also ties what you can select to the Id order field. The less efficient Skip/Take query can easily manage forward and backward paging, and still works when you have filtering involved, or even ordering on a specific value. That generic solution might be less efficient but it makes working with pagination a lot easier.

These are amazing tips. I really liked your motivation when explaining them. Well done!

amazing class thankyou brother

Thank you very much for this informative video. This all is new for me.

Cursor have it..pls check beta in settings

that's an excellent explanation and use case that all of us have faced at some point... thanks Gui!

this may be useful when you're building some feed (e.g: instagram), but definitely, when building some adult content website, where people need some more precise navigation

Pagination sucks when, during someone or some process paging your data, the data is modified. Let's say you're paging employees and you've just gone from page one to page two. Meanwhile, while you were looking at page one, an employee was added on the first page. Now you've "missed" the first employee and on page two you're seeing the last employee of page one as first entry. These 'continuation tokens' don't solve that either. Also, for every API request you're sorting the entire thing only to determine which records go on which page and to then only return a fraction of the data. And then the user / process asks for the next/prvious/other page and it all needs to be done all over again. It's horrendously inefficient. Whenever you can, try to avoid paging.

Nah. 👎. Too complicated.

It would be great if you could explain the underlying mechanism of this approach. What sets this apart from traditional pagination I have never worked with NoSQL. I assume that it's kind of index organized table. In the traditional method, - we start reading from the beginning - count to the offset - and then fetch records until we reach the page size With this new approach, we can use the index to directly jump to the starting point, improving performance. However, how does this work when we need to apply a filter and then skip and take records? Please explain clearly. Else, this video is not useful at all. We don't want to follow something just because an expert says to do it. We need to know the reason to think if it is worth implementing for our use case

Surely you'll still need to do a second query to get the total?

You Should Know This Before Using Page Numbers on Your API (with non-relational databases)

Is this similar or equals to cursor pagination?

Today I learned: test containers. Thanks for the lead to the concept and the modifications!

Is this technique a forward only process? Otherwise, you would have to keep track of the continuation tokens as you go along.

A great video! In fact all the videos I've seen from you are high quality 🤌. I have a question though: if the green arrows represent the flow of control, what do the purple arrows represent?

So the application became harder to maintain, harder to understand and with more code lines.

thx for the video didnt know any of them

Hey Gui, What is the tool that you used for drawing rectangles in screen?

2:40 The choice of words here makes a confusing subject harder to understand

You say you will answer the question “which IDE” but you never do. I see in the comments “Rider” but I hear you mention Jetbrains. I’m not familiar with either. But I’ll go look them up

Love your video, I'm having an interview next week and I thought I was wrong if I ask questions about what they expect of me in the position but you just clear my mind

Seems I have found another connoisseur of package by feature, not by layer. It's a shame industry standards still side with the latter! Excellent video, excellent code, excellent explanation. I only have one comment: it seems that for the current scope of the feature, Fakes might be a bit too much. After all, you only want to validate interactions between the repositories and the service, so stubs and spies should be enough. Fakes are the most powerful (tied with mocks) test doubles there are. The downsides of this power are: 1) complexity, as fakes need to emulate the behavior of a real system, and their code can spiral out of control; sometimes you can end up needing testing for your fakes! 2) performance, as using fakes for thousands of unit tests can make your test crawl to a halt. Fakes are best reserved for tests higher in the testing pyramid such as component, integration, system, acceptance, ... That being said, I am not against their application in this video. The code is "simple" enough where fakes are a perfectly fine choice. Furthermore, introducing two test double types (stub for the basket repository, spy for the order one) may be overwhelming for the target audience of this video. TDD is already hard enough! Furthermore, I am not familiar with the .NET world (I've only worked with Python professionally), and using fakes might be an industry standard I am unaware of. If that's the case, it's another good reason to have used fakes in the video!

Hi, I do not think you can compare nUnit and xUnit, nUnit is Unit testing, xUnit is Integration testing, with xunit, you test the full api , in nUnit you only test that unit? As far as I know you cannot do Integration testing with nUnit?

Enable subtitles to understand him.

Hello, could you tell me name of the tune that plays in the background ?

Tenho hoje uma entrevista, isto veio mesmo a calhar. Obrigado!

not working good in long-term perspective

It's all good and fun until you realise you have to start testing and returning the Result all the way up to the GUI. And all your void functions all of a sudden have to return Result. It'll get messy very fast.

I'm too confused now :) but maybe it's because imma jr.

Yay design patterns! I love your accent by the way. "Margherita Director" has such beautiful pronunciation. I will definitely be using the builder pattern to help reduce redundancy in my tests. Thank you!

What is this "public transportation system" you speak of? Just kidding :) American joke.

Excellent! Thank you Gui!

Shouldn't you have written the test for IsDivisibleBy first before implementing the method? And you cantually did not implement a test for it at all. Anyway, great video that explains the principle of test driven development.

Great explanation! Just a sugestion, please give it one more second when you drop code to be read. It always shows and then jumps of to another screen lol

I would at least make it useful by turning it into a monad with a Map and Bind method..

I like this structure, looks obvious and clean. However, you have forgotten to demonstrate how each of these endpoints gets DI dependencies injected: Repositories, Logger, TelemetryClient, DBContext, whatever else real life app needs. And then again, there is never a practical app without Authentication/authorization. You need to show how to apply those in this pattern as well, otherwise this remains just a dead-end concept without practical guidance.

Well explained. Thank you!

Love this video. Thank you!

Why bother with cursor? It's absolute trash

The language, sdk, and runtime are all open source. The debugger is the tool that uses them. Both facts can be true.

While I agree, all the exception-handling stuff can be moved into the global exception interceptor. The fluent validation type can be inferred by pattern matching in the TryHandleAsync method of IExceptionHandler. With that, we won't need to call the _validator.ValidateAsync on each HandleAsync.

It sometimes doesn't make sense when you throw the word `Open Source` thinking someone should spend time and money to create something entirely free without benefits. If 'Cursor AI' thinks it needs to cater for .NET developers, they should be creative to create their own debugger, just as JetBrains did. Microsoft isn't doing things because they love us but to benefit as well.

I didn’t cover debugging in this video, but you can find it here: ruclips.net/video/vbMe7NgQ9FQ/видео.htmlsi=Z0ZkBhBMS3ZHviBQ

All good mate. Thank you for the update and the great videos.

Cursor is limited to only its own IDE. Copilot can work with anything.

I'm using all 3 IDE's (Cursor, Rider and VS). Do I need to? No, but I feel more productive with all 3. I have my solution open in all three and I jump between them for their strengths. Thankfully they all detect and process external changes reliably (at least they have for me). For blasting out code I already know how to write, Rider. For debugging, performance tuning and legacy code VS. For new frameworks or for areas where my experience is minimal, I use cursor to get me started in flushing out the bones of what I need, then I jump over to rider once I get my head around whatever the AI showed me. If Rider starts to emulate cursor with it's AI offering (right now I found it clunky), I think I agree with you Gui, I would fallback to just using Rider and VS.