Înapoi la articole →

Cel mai recent articol

Ultima verificare

Urmăritori 0 urmăritori
Articole: 200
  1. Using a pull request to merge the same commit to multiple branches causes GitHub Checks and validations to fail.

  2. When it comes to code, what you don't know can hurt you.

  3. How does .NET determine debug or release at runtime?

  4. It seemed like simple indigestion from a spicy dinner.

  5. Not completely sure about the differences between Debug and Release builds in .NET?

  6. Instead of using symbol servers to index our PDBs, we can use an open, standardized approach to map our symbols to source code and improve the debug experience.

  7. It's not really an exploration of PDBs and debugging without talking about symbol servers.

  8. Almost a decade ago, John Robbins opened up the details of PDBs to the developer world.

  9. Certificates rely need a system of trust, and this starts with certificate authorities (CAs).

  10. Despite decades of use, certificates tend to be a mystery to most developers.

  11. Most package management systems support "universal artifacts" storage.

  12. If you need to integrate an external system or execute parts of the CI process asynchronously, the GitHub Checks API can provide a way to make that happen.

  13. Executing a GitHub Action for a pull request creates a surprising number of SHA commits.

  14. Monorepos are often seen as the simple solution to complex collaboration and code management problems.

  15. Many people are familiar with the idea of the template repository.

  16. GitHub Actions provide powerful workflow support but rely on trusting third-party code.

  17. Dev container features provide a quick way to add functionality.

  18. Azure VM SKUs start with a letter to indicate the workload it was optimized to handle.

  19. Azure continues to grow, offering nearly 300 services.

  20. Git's safe directory configuration helps to protect users, but it can create challenges.

  21. GitHub Actions allows you to create matrix builds to execute steps multiple times with different parameters.

  22. It's important to understand how to securely access package repositories when doing a Java build.

  23. Last week, we examined some common myths about time.

  24. There are three common ways we misuse time in development.

  25. Everything coded can be exploited, including GitHub Actions.

  26. Explore what happens to files in Git after squashing a set of commits that have a tag applied to them.

  27. Understand how branches work with the process of triggering Actions workflows in GitHub.

  28. In previous articles, we've explored the costs for inefficiencies in the development practice.

  29. Want to deploy ARM with a custom wizard, just like the Microsoft-provided resources?

  30. Create financial models that help you understand the actual costs of your technical debt and bad development practices.

  31. Major products and companies disappear without a trace.

  32. Trying to integrate your custom processes with GitHub doesn’t have to be challenging.

  33. Learn how to use the Docker BuildKit gha, inline, and registry layer caching with GHCR, and GitHub Actions to improve build performance.

  34. Dive deeper into dev container Features and Linux scripting to create an entrypoint for the non-root users.

  35. Sometimes scripting in containers just isn't enough.

  36. Explore the basics of the specification and how it lets you create reusable components for your dev containers.

  37. GitHub has a lot of options for verified domains.

  38. In this post, we'll see if we can run some Docker commands from inside our Alpine dev container using Docker-from-Docker and a bit of configuration.

  39. It’s incredible how fast the time flies!

  40. Learn the dev container trick for accessing a host port to create a proxy SSH connection to a Git server.

  41. Learn a trick for using SSH to connect to multiple GitHub environments and Git hosts with minimal effort.

  42. Explore what a non-compete is, what it does, and why it may not be a problem for much longer.

  43. Public presentations have a lot of copyright considerations.

  44. Contracts are hard.

  45. My wife and I have been long-time fans of Google’s products (until they discontinue them, of course!)

  46. Trying to secure code is no easy task.

  47. Databricks is an exciting and powerful platform for creating solutions that can process big data into actionable content.

  48. There’s a lot of documentation around using Azure Data Factory, but surprisingly little on implementing DevOps practices.

  49. It’s been fun spending time re-exploring the data platform this week.

  50. The other day I was needing a quick and easy way to configure Node.js in an Ubuntu environment.