Înapoi la articole →

Cel mai recent articol

Ultima verificare

Urmăritori 0 urmăritori
Articole: 200
  1. When designing a system’s architecture, you have many choices to make.

  2. Small changes sometimes make a huge difference.

  3. C# devs have the bad habit of creating interfaces for every non-DTO class because «we need them for mocking!».

  4. Learn how to organize similar unit tests using the TestCase attribute in NUnit!

  5. Learn how to zip and unzip compressed files with C#.

  6. You should always put a limit to the number of incoming requests.

  7. Learn how to integrate Oh My Posh, a cross-platform tool that lets you create beautiful and informative prompts for PowerShell.

  8. As you know, you should always validate input models.

  9. A Git commit represents the status of a system.

  10. API Gateways are often a component of a microservices architecture.

  11. Learn how to use Feature Flags in ASP.NET Core apps and read values from Azure App Configuration.

  12. Sometimes just a minor change can affect performance.

  13. Feature Flags are a technique that allows you to control the visibility and functionality of features in your software without changing the code.

  14. «Consistency, Availability, and Partition tolerance.

  15. Integration Tests are incredibly useful: a few Integration Tests are often more useful than lots of Unit Tests.

  16. Customizing the behavior of an HTTP request is easy: you can use a middleware defined as a delegate or as a class.

  17. ASP.NET allows you to poll Azure App Configuration to always get the most updated values without restarting your applications.

  18. If you need to handle lots of incoming requests, you should manage the incoming traffic by balancing the load across different servers.

  19. Centralizing configurations can be useful for several reasons: security, consistency, deployability.

  20. When writing unit tests, there are smarter ways to check if two objects are equal than just comparing every field one by one.

  21. By default, you cannot use Dependency Injection, custom logging, and configurations from settings in a Console Application.

  22. Testing Pyramid and Testing Diamond are two ways of managing automated tests.

  23. There are several ways to handle configurations in a .NET Application.

  24. We all use switch statements in our code.

  25. Downloading a file from a remote resource seems an easy task: download the byte stream and copy it to a local file.

  26. Interpolated strings are those built with the $ symbol, that you can use to create strings using existing variables or properties.

  27. A system should be robust: it should be able to resist change and, well, not generate regressions.

  28. Shorter code is often easier to read.

  29. Health Checks are fundamental to keep track of the health of a system.

  30. Lists have an inner capacity.

  31. Elasticity and Scalability: two important Architectural attributes, similar but quite different

  32. By using list patterns on an array or a list you can check whether a it contains the values you expect in a specific position.

  33. Using Conventional Commits you can define a set of rules useful for writing meaningful commit messages.

  34. In C#, nameof can be quite useful.

  35. Cache-aside, Read-through, Write-through, Write-behind: quite easy on the surface, but let’s go a little deeper!

  36. If you need a sequence of numbers, you can pick two ways: use a While loop, or use Enumerable.Range

  37. LINQ is a set of methods that help developers perform operations on sets of items.

  38. Exposing Swagger UI is a good way to help developers consume your APIs.

  39. A PriorityQueue represents a collection of items that have a value and a priority.

  40. Are you interested in C# 11 and .NET 7 - Modern Cross-Platform Development Fundamentals by Mark J.

  41. When you need to fire synchronous events, don’t use a while(true) loop: use a Timer!

  42. In a microservices architecture, an API Gateway hides your real endpoints.

  43. Don’t let the reader get lost in the code details!

  44. Building APIs with .NET is easy.

  45. C#, as every other language, has several reserved keywords.

  46. Every application relies on some configurations.

  47. DRY is a fundamental principle in software development.