I've programmed C# for nearly 15 years, and have used goto twice . Once to simplify an early break from a nested loop, essentially a nested continue. The second was to refactor a giant switch statement in a parser, essentially removing convoluted while loops, and just did a goto the start.
It's one of those things that almost should never be used, but the times it's been needed, it removed a lot of silliness.
The opinion is not "cherry-picked", nor are the highlighted examples from the book unique or lacking context. It is a long, thoughtful and articulate criticism of multiple passages from "Clean Code", and display a fundamental problem with the advice it gives. It's not to pretend there's no good advice in the book, but that the bad advice is really bad and very prominent. Also, it's impossible to finish since the back half is Java-centric, a relic of the era it was written.
Certainly not everything in his books is bad, and not everything that is bad today was bad when it was originally written. The biggest problem with the quality of his books, is that there's a mix of good, bad, and out-dated advice in there, and for the beginners/Juniors reading his books, it's genuinely hard to tell the difference. I think people would be better off looking for sources that avoid some of the mistakes that he made, amd speak to a more modern audience who are working with recent technologies and in work environments as they exist today.
FB is only huge because they've expanded all over the globe, even providing internet to developing nations to facilitate new user acquisition. In reality they've been bleeding the original Western users that signed up between '04-'10, and growth among new generations flatland a long time ago. There's a reason Meta aggressively expanded to other ventures (or attempt to create platforms) like Instagram, Threads, what's app, VR and metaverse. Metas only chance at sustainable growth and capturing young people is to build or buy platforms young people will use, because it ain't Facebook.
I never saw that, that's legitimately funny. I'd love to be in the room when that feature was designed, and the reaction of the developer it was handed too.
Machines aren't people. Machines don't learn. Machines copy data, manipulate and replicate it. That is copyright infringement. The laws for Machine duplication don't apply to human learning.
Razor is the templating engine that's been there since the original MVC. Blazor Server is the one that needs a server and streams changes to the client using signalR. Blazor WASM is the one that uses Web Assembly. As of .Net 8, Blazor can now also ne used as a generic SSR backend. They all use Razor Components, which is a component model using the Razor engine.
Not to be confused with Razor Pages, which is also a generic SSR backend.
C# will definitely spoil Java for you. Even modern Java, there's just no going back from the .Net ecosystem without feeling like you're timetraveling 10 years.
Our last major college project that spanned multiple semesters was worked on by 5 devs all editing the same source files over Dropbox. The school had servers for svn, but no one knew how to do source control. It was exactly the type of shitshow you would expect.
Don't be fooled, there has always been a class system in every society. Some choose to formalize it, but the best ones pretend it doesn't exist and dangle the illusion of social mobility.
I've programmed C# for nearly 15 years, and have used
gototwice . Once to simplify an early break from a nested loop, essentially a nestedcontinue. The second was to refactor a giant switch statement in a parser, essentially removing convolutedwhileloops, and just did agotothe start.It's one of those things that almost should never be used, but the times it's been needed, it removed a lot of silliness.