A few weeks ago, one of our Windows Server made a reboot in the middle of the day. That was not planned, so we wanted to know what happened. Windows logs events like the reboot in the event log. The challenge is to find the right message in the huge pile of unrelated log messages. As it turns out, we can use a filter and get the right message in no time.
Back in Oslo at last. After an online edition of NDC Oslo in 2020 and the travel restrictions at the start of the Omicron wave in 2021, I haven't been to Oslo for a while.
Visiting in September is in many ways different from June. It is colder, and it gets dark early (around 7 pm), yet Oslo is still the same with its constant changes. The Munch museum and the new Deichman main library are now open. After seeing for years how those buildings grow, I now had the opportunity to visit them. Both are close to the Oslo Opera House and worth a visit.
Developers spend a lot more time on reading code than writing it. Therefore, if we want to get more effective, we must take a deep look at the reading part. In this Workshop Mark Seemann uses a set of heuristics to address the common obstacles developers face when it comes to understanding code.
Keep in mind that heuristics are a rule of thumb that you always should take with a grain of salt. They may be a great help for certain situations but may miss important details in others.
As I was working on a project, GitHub Desktop bombarded me with this login dialog:
If your Git client does not clean-up the local branches after those branches got deleted in your remote repository, you can run this command to get rid of them:
Figuring out what version of .Net is on your computer is not so easy to answer. Do you have the new .Net or the .Net Framework? Let’s look at ways to answer this questions.
I got a new work laptop, a Dell XPS with a lot of power. The machine is great, but it had one big problem. Whenever I tried to use an external screen, I got this error on Windows 10:
When we write code to solve a tricky problem, we often end up with methods that show us the whole journey of how we got to the solution: there is code to load data, followed by transformation logic intertwined with data clean-up hacks to prevent the creation of a report from exploding.
It is nothing wrong with writing code that way and to iterate until we reach the goal. The problem is that we keep everything in the order in which we initially wrote it. The developer who needs to fix a bug does not care if we found a missing default value at the beginning of the implementation or at the end. They much more prefer code that separates the different phases (load, clean-up, transform, report) and guides them towards the place where they should implement the fix.
If you try to create a folder with a leading dot, like the .well-known folder for domain validation or the security.txt, you may end up with the error "You must type a file name" on Windows Server:
We run into a strange error when we added a new environment variable to our Docker Compose file:
ERROR: Invalid interpolation format for "environment" option in service "api": "MY_KEY=Abc$5"