Kind of high level, but good summary of the key players / market share in observability from Barclays (Observability Industry Review: Volume 7, October 2023. Sorry, no public link). Would be intere…
Mention the words "maintenance programming" to a group of developers and
they'll, to a man (or woman), recoil in horror. Maintenance programming is
widely viewed as janitorial work.
But maybe that's an unfair characterization.
In Software Conflict 2.0 : The Art and Science of Software Engineering
[http://www.amazon.com/
Data science is a relatively new term for a relatively old discipline. Essentially, it is data analysis, particularly for large data sets. It involves techniques as wide-ranging as statistics, comp…
What 5G Fixed Wireless Boom Can Teach Us About Technology
The 5G Home Broadband is booming. However, the journey of fixed wireless access has neither been simple, easy, nor cheap. This recent boom teaches us a big lesson: the unpredictable and often arduo…
There's a coding convention known as "Yoda conditions" that imparts a valuable lesson in preventing subtle bugs and fostering cleaner code. Named after the wise and syntax-flipping Yoda from Star Wars these conditions involve reversing the typical order of comparison in expressions. Let's delve into the wisdom behind Yoda conditions and why they are embraced by developers. What are Yoda Conditions? In traditional conditional statements you might see comparisons written as variable == constant . However Yoda conditions flip this order presenting the constant first: constant == variable . The unconventional style is intentional and serves a specific purpose. The Wisdom Behind Yoda Conditions 1. Guarding Against Accidental Assignment: Consider the following scenario: if (x = 5):
# This is syntactically valid but assigns 5 to x instead of checking equality
# This can lead to unintended behavior and difficult-to-find bugs
# Yoda conditions guard against such accidental assignments
On the other hand: if (5 = x):
# Results in a syntax error catching the mistake early in development
# Yoda conditions provide a safety net against accidental assignments
By placing the constant on the left a syntax error is triggered if a single equals sign is mistakenly used instead of a double equals sign for comparison. 2. Improved Readability: Proponents of Yoda conditions argue that they enhance code readability. The unconventional structure draws attention to the constant making it clearer that a comparison is taking place. This can be especially helpful when scanning code quickly reducing the chance of misinterpreting the intention of the statement. Conclusion: In the coding universe Yoda conditions serve as a small but powerful tool to prevent subtle bugs and improve code maintainability. While coding styles can vary embracing the wisdom of Yoda conditions contributes to a cleaner safer and more readable codebase. May the force of consistent and clear coding conventions be with you!
In my recent blog posts, I’ve primarily focused on hardcore crypto topics, which may be too specialized for a broader audience. In this post, I aim to address issues that resonate with the experiences of most software engineers and demonstrate how they can be solved when writing code with Elixir. Specifically I’ll describe how to write maintainable and easy to test code which makes requests to external services.
One piece of flippant commentary that you’ll hear occasionally is that it’s “Better to be lucky than to be good.” On an individual level, it’s almost certainly true that being very lucky outperforms being quite good: I certainly know a number of folks who are financially successful after working at companies that succeeded, but where their direct impact was relatively small. Companies get lucky, too. This is true both in the sense that the door to acquisitions was much more attractive last decade than it is today, and also in the sense of Ben Horowitz’s quote from The Hard Thing About Hard Things, “Wartime CEO knows that sometimes you gotta roll a hard six.