DEV Community: Codetard

Return of Codetard: Arduino Lore

Codetard — Mon, 19 Oct 2026 07:49:27 +0000

THE RETURN

So I was doom scrolling and testing how wrecked my attention span can get, when I came across a reel which was a small Arduino project and it lit my curiosity and I decided to make a tony stark inspired portfolio for myself which is still a work in progress hopefully it's done before November, you can check it on https://x.com/anon5877/status/2104931447513768448?s=20. Meanwhile I was working towards building this I came across a very interesting concept which today i wanna share with you all. So sit tight we are about to learn how my keyboard and a tiny chip manage to agree with everything without a shared brain.

LORE I - Three strangers in a trench coat

I press a key. The ring LED on my desk obeys. Now the question is how?- how do they obey with no one in charge. When I press the keyboard carries its own tiny microcontroller and speaks a USB standard called HID (Human Interface Device). It has no idea that a ring exists. The OS(Operating system) hands the browser your keypress. The Browser-our second character-establishes a key distinction: it's a relay, not a boss. It passes messages; doesn't command anything. Now a tiny device called the Arduino Nano, an ATmega328P which is our third character which is also connected to the serial line but has no idea the keyboard exists. So - how do they agree ?

LORE II — The Laws of the Wire

As I searched the depths of my codebase, I found a file called PROTOCOL.md. Yes, a simple text file-and the first thing it told me was that the wire itself knows nothing. It says the wire does not know what a message says or means. Its only job is to move bytes at a fixed speed- and hand them over in whatever clumps it feels like, which means we can never control how the bytes arrive: one read can hand you half a message, or three glued together. So structure can't come from the wire. It has to come from agreement. The agreed boundary: every message is LABEL:value ** and ends with **\n. Why \n: it can't appear inside a message, so it's a safe "end here" marker. The buffer: collects bytes; whenever the delimiter appears, drain everything before it as one clean message. So: irregular bytes become messages the moment both sides agree where the fence ends.

Messages have now structure but structure isn't agreement. Anyone can shout; these two character of our story had to agree on how to behave while shouting. There's no boss , so there are certain set of rules do all the work. Four rules. A tiny constitution.

Law 1 - messages say "be at X," not "do X again" → repeats are harmless → that's why there are no acks and no retries. Its like say I have a fever and I shout repeatedly that I have a fever, the shouting will not change my fever so: it is idempotent in nature.

Law 2 - each value has one owner, the other mirrors → conflicts can't form.

Message	Meaning	Writer
`SPEED:12`	animation speed — 0 to 50	browser
`POWER:200`	LED brightness — 0 to 255	browser
`COLOR:255,0,0`	LED colour — r, g, b	Arduino

Law 3 - neither device trusts the other; each clamps values into legal range on its own. So: no trust required between strangers.

Law 4 - when the nano boots, it announces where it stands; when the browser isn't sure, it asks. (That asks command is SYNC).

They don't coordinate - they follow the same polite rules.

THE SIGN-OFF

So that's the whole trick. One keypress, three strangers who've never met, and a wire that has no idea what it's carrying.

Turns out the internet runs on the exact same idea — bytes over a wire, agreed boundaries, polite rules. The whole thing, desk-sized.

They never needed a common brain. They needed a contract — and a few polite rules. Two things don't agree because someone forces them to; they agree because they both keep the same promise.

The build's still going — hopefully wrapped before November. You can watch the chaos here: https://x.com/anon5877

Thanks for reading. See you in the next one — assuming I don't vanish again.

Noise, Attenuation & The Secret Life of Signals – A Beginner’s Dive into the Physical Layer

Codetard — Mon, 21 Jul 2025 12:59:07 +0000

Hey guys, Codetard here! 👨‍💻

If you're coming from Twitter, you probably already know me. If you're new—welcome aboard! This little corner of the internet is where I’ll be diving into different computer science topics as I journey through university. So stick around, learn with me, and let’s geek out together. 😄

Today’s special topic on the menu is...

🌐 Attenuation and Noise in Computer Networks

This comes from one of my favorite subjects: Computer Networks. It’s all about how data—be it your messages, downloads, or YouTube videos—is sent across devices using the OSI Model, which breaks communication into seven logical layers.

Now, the concept we’re tackling today lives at the very bottom—the Physical Layer (Layer 1). This is where all the actual signal transmission happens.

Bonus: If you're curious to explore the entire OSI model, here's a great visual reference I found helpful:

🎯 Noise – The Signal Disruptor

Imagine sending a perfect signal—a smooth, clean digital sine wave. It looks something like this:

But here’s the catch: as signals travel, they don’t always reach the destination unscathed. They often pick up noise—unwanted interference from external sources (like electrical signals, magnetic fields, etc.).

This noise distorts the wave, as you can see below:

Notice how the wave's surface becomes jagged and uneven. This is what happens when noise interferes—it messes up the shape of the signal. In real-world scenarios, this can lead to data loss, errors, or misinterpretation, which is a serious concern in industries like satellite communication, aviation, and more.

NOISE TECHNICAL DOWNSIDES:-

Data Corruption and Errors:- Unwanted disturbances in data transmission , power supply fluctuations, or sensors readings can introduce as false readings, furthermore as we have datasets in machine learning(ML) a noisy or corrupt data can cause degradation of overall learning parameters and prediction accuracy.

Bit error :- As you know during these transfer of data our data most of the time is converted into bits these bits hold all our information about our data but here comes our villain noise here acts and disrupts our signal which pollutes or flips a important bit like reading 0 instead of 1 this is why most files get corrupted.

Noise impact on real world:-

Have you ever wondered why you sometimes keep experiencing 'connecting' status during a video or audio call this is because of our villain noise. Noise here corrupts our signal due to which communication apps like WhatsApp, Telegram etc. have to retransmit our signals meaning retry giving signals or if receiving messages follow a very interesting approach of checksum(A part of bit error detection method) and if detected uses the same approach of retransmitting the original signals in there queues.

Environmental manipulation like water sprinkling near pollution sensors acts as measurement noise — the sensor reads cleaner air locally, but the true city-wide pollution remains unchanged.

📉 Attenuation – The Signal Fader

Now let’s talk about attenuation. This is when a signal loses strength the farther it travels.

Here's a visual from my project to help you picture it:

As you can see, the wave becomes flatter and weaker. This weakening can make the signal unreadable at the receiving end. That’s why devices like repeaters, amplifiers, or boosters are used—to regenerate or strengthen the signal along its journey.

This factor is critical in telecommunication networks, especially when we're covering long distances, like undersea cables or satellite relays.

ATTENUATION TECHNICAL DOWNSIDES:-

Reduces Signal to noise ratio which we call SNR in short form and why should we considered by it. So let me tell you SNR ratio is ration between power of signal and power of noise so what attenuation does is weaken the signal over distance which directly means a low signal strength or power thus disrupting the snr ratio
As we know that we communicate daily worldwide so in order to make these communications more easy we have to backup our infrastructure in terms of more amplifiers, repeaters etc. Which increases our maintenance cost , power cost and human resources and their management cost.

Attenuation impact on real world:-

Ever noticed how Wi-Fi is blazing fast when you’re near the router, but the moment you step into another room, everything slows down? That’s attenuation in action. What’s happening technically?

Wi-Fi signals lose energy as they travel through air.

Walls, furniture, and even humans absorb and weaken the signal.

Higher-frequency Wi-Fi (like 5 GHz or 6 GHz) attenuates even faster because it can’t penetrate obstacles well.

🧨 Real-world impact:

You get lower bars on your phone.

Download speed drops.

Online games lag.

YouTube drops to 360p “to save your sanity.”

Google Maps often becomes inaccurate—showing the blue dot drifting, spinning, or jumping to the wrong road—because GPS signals from satellites are extremely weak by the time they reach Earth, and attenuation makes them even weaker as they pass through obstacles like buildings, tunnels, malls, car roofs, and bad weather; this weakening causes your phone to lose precise satellite lock, leading to “GPS signal lost,” unreliable navigation, delayed updates, wrong directions, and frequent rerouting, all because the attenuated signal is too faint for the device to decode correctly.

🧠 Code Logic (Used to Determine How to Handle Attenuation and Noise)

If you're new to programming or computer simulations—don’t worry! Let's break this down together. 👇

We’re using a little bit of JavaScript code to simulate how noise and attenuation affect a digital signal as it travels.

Here’s the core logic:

const noise = ((Math.random() - 0.5) * noiseLevel);
const attenuationFactor = Math.pow(1 - attenuationLevel, x / width);

🎙️ Line-by-Line Breakdown:

1. Noise Simulation

const noise = ((Math.random() - 0.5) * noiseLevel);

Math.random() generates a number between 0 and 1.
Subtracting 0.5 centers it around 0, so now the value ranges from -0.5 to +0.5.
Then we multiply it by noiseLevel to control how intense the noise is.

👉 This simulates random distortion—just like real-life noise that can push a signal up or down unpredictably.

Example: If noiseLevel = 10, then noise will vary randomly between -5 and +5.

2. Attenuation Simulation

const attenuationFactor = Math.pow(1 - attenuationLevel, x / width);

attenuationLevel is how much signal is lost per unit distance (like 0.01 for 1% loss).
x is the position or distance the signal has traveled.
width is the total distance (like the full length of a cable).
The formula uses exponential decay to simulate gradual loss over distance.

👉 The farther the signal travels (x increases), the smaller the attenuation factor becomes, flattening the signal—just like in real life.

⚡ Putting It All Together

When we simulate a wave across a canvas or graph, we apply:

Random noise to simulate environmental disruption
A attenuationFactor to reduce its strength as it travels

This helps us visualize how clean signals degrade in real-world communication systems!

🧠 Wrap-Up

So today we looked at two major villains in the world of signals: noise, which distorts the signal’s shape, and attenuation, which drains its strength. Both are super important to consider when designing any kind of network system.

Hope this gave you some insights (and cool visuals) to imagine how raw digital signals behave out there in the wild! 🌍

🧪 Wanna Play With This IRL?

If you want to experiment with the simulation yourself—add chaos, tweak the noise, break some signals—
fork this repo and go wild on your own system:

👉 Noise-simulation (GitHub Repo)

Warning: May cause an unhealthy obsession with sine waves. Proceed at your own risk. 😵‍💻

More topics coming soon—until then, stay curious and keep coding.
If you liked this blog,
follow me on X to enjoy my shitposts (mostly coding, sometimes crying in console
– Codetard, signing off ✌️