We will create an Angular library, publishable to NPM, with multiple entry points, unit tests and CI/CD in GitHub. Source code for each step will be provided, as well as complete solution in a GitHub repo.
Suppose we need to convert a legacy .NET 4.5 MVC or API project to .NET Core 6.0. It might sound like daunting task at first, and if you never did this, might cause you headache for a few days/weeks, or even months depending on the size of the project. In this article I will do my best to reduce that headache by giving you starter info and some follow-up articles to learn more about the topic.
Suppose you have the following ES6 code and you want to have a refactor safe way to output the service name without instantiating an object. MyFancyService.name will work fine in dev, until you decide to minify it with webpack. You see, by default, class names will be minified, and at runtime the above code line will become something like Ab.name.
Below video is from 2018, so almost 3 years old now, but somehow I only found it now. It's a handy overview into microservices, has a few gotchas such as avoiding internal communication when fulfilling client requests, to reduce latency, as well as async workflows like adding items to cart.
Here are some of the notes I took while attending Jetbrains .NET Days 2021 online event - for select sessions from Days 1 and 2. Specifically, I skipped 1 session from Day 1 (React/CosmosDB), and only watched 1 session from Day 2 (AWS/Kubernetes). This is similar to my earlier MS Build notes articles.
When hiring software developers, it seems that recently the focus has been on the speed of coding. Many companies give automated 1-1.5 hour coding tests where your code can be of low quality, as long as it passes all unit tests. Is speed of producing the initial dirty version of the code actually important in modern software development?
Outsourcing is a trap most big and mid size companies fall into. Advising to outsource is like advising someone to walk on a rope. Sure 1 of 100 would be careful and do it right. What about the other 99?
When we write software for our own use, vs for enterprise - it is a fundamentally different process. What works for a team of one person, does not work for a team of 100. Let's take a look at the most common processes that are in place to ensure that code survives the test of time when maintained by a big team.
I recently bought a new 2TB SSD to handle my virtual machines. This one is m.2, was previously using 256 GB SATA drive. Nothing against SATA, it just can't compete on speed with m.2.
Every developer should know their code editor, version control system, how to make incremental changes to code, not be afraid of trial and error and respect achievement of other developers. Let's take a look in more detail on what each of these means and why they are all important.