Înapoi la articole →

Cel mai recent articol

Ultima verificare

Urmăritori 0 urmăritori
Articole: 200
  1. Two of the operations you often do with your code is to discuss it, or perform a search over it.

  2. Debugging our .NET applications can be cumbersome.

  3. Is your string really empty, or has it hidden characters?

  4. Senders and Receivers handle errors on Azure Service Bus differently.

  5. The Principle of Least Surprise is a simple principle that helps you writing clear, obvious code: this helps other developers foresee what a component does without worrying of unexpected behaviors.

  6. Queues or Topics?

  7. Do you need the index of the current item in a foreach loop with C#?

  8. Azure Service bus is a message broker generally used for sharing messages between applications.

  9. Choosing meaningful names takes time!

  10. Knowing the Assembly Version of the API you’ve deployed on an environment may be helpful for many reasons.

  11. Doing a tech talk is easy.

  12. It’s not a good practice to return the ID of a newly created item in the HTTP Response Body.

  13. Code coverage is a good indicator of the health of your projects.

  14. Tests are as important as production code.

  15. Language details may impact application performance.

  16. Having fast API response is crucial for your applications.

  17. When performing a talk, the audience experience is as important as the content.

  18. Revise PowerShell basics with a simple script that opens a browser for each specified URL.

  19. DateTime, Guid, and Random values are not under your direct control.

  20. Code coverage is an indicator of the quality of your code.

  21. The way you handle errors on your code can have a huge impact on the maintainability of your projects.

  22. Is string.Format obsolete?

  23. How to effectively ping an endpoint in C#?

  24. MongoDB is a database based on JSON-like documents, but it can be queried using C#.

  25. Are Getters and Setters the correct way to think of abstraction?

  26. Wouldn’t it be nice if Visual Studio could autogenerate clients for external API?

  27. With HttpRepl you can perform HTTP operations as they were local folders, using the CLI.

  28. During this holiday I hiked for the first time.

  29. Swagger is a tool that exposes the documentation of your APIs and helps collaborating with other teams.

  30. Are all comments bad?

  31. Integration tests are useful to check if multiple components fit together well.

  32. You’re using DateTime.Now, aren’t you?

  33. I don’t have to tell you why you need to write clean code.

  34. Sometimes on your tests you need to access test files, for example for mocking external data.

  35. BenchmarkDotNet allows you to test the performance on .NET methods.

  36. Validating inputs is crucial for every application.

  37. Internal members can be accessed only within the same assembly.

  38. Singleton, Scoped and Transient: these are the possible lifetimes for DI with .NET Core.

  39. We’ve already seen some of the things you should know about enums in C#.

  40. Docker is a project that allows you to create and run applications in an isolated environment.

  41. Enums are often used with C#.

  42. Having a robust logging system is crucial for any application.

  43. Do you have an Azure Function that you want to upgrade from v2 to v3?

  44. Azure Functions are one of the best examples of serverless applications.

  45. Azure DevOps, among its capabilities, allows you to store NPM packages in their system.

  46. Asynchronous programming is often seen as something cumbersome, so many developers avoid it.

  47. You may need to run Google Chrome with CORS checks disabled.