In a previous job, I found that a coworker was spending a full work week building an excel spreadsheet from our Azure DevOps data, so I spent about an hour writing a small program to replace his entire job. This triggered an arms race between myself and the coworker where they would slightly change what they added to the excel spreadsheet, and I would add that into the simple program (and then make it better). This went on for about 2 weeks until I was called into the manager’s office and was told that I was bullying the coworker by doing this, which I disagreed with.
ML.NET provides a very simple way of performing Anomaly Detection on random variables as long as they are independent and identically distributed (i.e. daily sales totals recorded at the end of each and every day). With it also being possible to detect anomalies without requiring past examples beyond your dataset.
Companies often claim that the operate a “no blame culture”, and then joke tht its actually a “know blame culture”. A “no blame” culture and a “know blame” culture may sound similar, but they have significant differences in their underlying principles and how they are practiced within a software development organization. This is particularly notable in the software development industry due to its unique characteristics.
In recent years, the Zero Trust security model has gained prominence as a robust approach to safeguarding digital assets. However, when applied within a software development company, this policy can inadvertently hinder the productivity of software developers. This article delves into the specific challenges that arise when implementing a Zero Trust policy in this context, shedding light on why it may not be the most conducive approach.
In the fast-paced world of software development, achieving high levels of productivity is paramount for successful project completion. However, counterintuitively, overmanaging software developers can often lead to reduced efficiency and hinder the overall progress of a project. This article explores the reasons behind this phenomenon and suggests alternative approaches to foster a more productive work environment.
Yesterday, Gamers Nexus posted a video titled “The Problem with Linus Tech Tips: Accuracy, Ethics, & Responsibility”, which addressed several concerns that GN have with Linus Tech Tips, the LMG Labs, and Linus Himself.
With this post, I would mostly like to address several things Linus stated in his response to the video.
When it comes to choosing the right programming language, developers often find themselves faced with a myriad of options. Among these, C# and Java are two prominent contenders, each with its own strengths and weaknesses. In this article, we’ll delve into five compelling reasons why C# outshines Java, making it an exceptional choice for modern software development.
Here are 5 reasons why choosing C# is a better idea than choosing Java.
After being told by somebody on discord that it “is impossible to block elon musk on twitter”, when in fact, it is quite simple. I decided to make this post and this video to show just how simple it is.
GitHub hosts millions of different repositories, most are projects that developers are working on, but a fraction of them are valuable resources for learning. Over time, I have collected a list of repos that contain these valuable resources.
C# 12 introduces several features aimed at laying the foundation for future performance enhancements. These features include easy access to inline arrays, an experimental feature called interceptors, and enhancements to the