Urgent.News

One page, thousands of outlets. See who else covered it.

Editions

Tech

"It works on my machine"

We've all heard this saying before. We've all seen the memes. Maybe we've actually said this before in our day to day work when someone says something isn't working on their machine. There are a lot of variables that could potentially go unaccounted for when a developing a feature. Different OSes. Different versions of the same OS. Different browsers. Different CPU architectures. It could even…

The adage "it works on my machine" has become a common refrain in the tech world, often accompanied by memes and a hint of frustration. There are numerous factors that can influence software performance across different environments. These variables include the operating system, version, browser, CPU architecture, and even the size of the monitor being used.

For instance, a feature that displays well on a large 27 or 32-inch monitor might not scale properly on a smaller laptop screen or when multiple web pages are displayed simultaneously on a 27-inch monitor. Sidebar elements that seem functional on large screens can also prove problematic for smaller displays.

Backend services also present their own set of challenges. Apple's M-series chips, while powerful, are not the standard for cloud-based servers. Developers typically work on x86-64 based servers, which may not offer comparable performance. A personal experience illustrates this disparity: during a project involving password hashing, the developer updated the algorithm to a more secure version.

However, after testing on their own laptop, everything appeared to be functioning correctly. Yet, when the updated code was deployed to a test environment running on older servers, the performance dropped significantly—taking up to ten times longer than on the developer's laptop. Further investigation revealed that even the production servers were over ten years old, and the new hashing algorithm would make them run about twice as slow as the developer's machine.

This example underscores the importance of considering the actual deployment environment when developing software, rather than just assuming it will run flawlessly on the developer's machine.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in Tech

OmniMem, IDE RAM monitor :)

OmniMem: el monitor de RAM que creé para VS Code y todos sus forks Desde aproximadamente 2018 utilizaba una extensión de Visual Studio Code que me resultaba especialmente útil: mostraba directamente…

Hashing across architectures

In a previous post, I mentioned how just because you develop on a brand new or nearly new laptop doesn't mean that's where your code is going to run, especially if it's deployed to the cloud.

More from Monday 17 August →