Most people meet LEDs in the same wonderfully humble way: a small red dot on a circuit board starts blinking, and suddenly the world of electronics feels conquerable. Blink on. Blink off. Congratulations, tiny astronaut, you have made light obey code.
Then someone like Mike Harrison walks into the room and politely reveals that blinking an LED is not the end of the story. It is the first sentence of a much larger novel involving current control, thermal behavior, PWM dimming, gamma correction, color rendering, wiring losses, addressable pixels, driver chips, installation maintenance, and the ancient engineering curse known as “it worked perfectly on the bench.”
Mike Harrison, known in maker circles through Mike’s Electric Stuff and his appearances in Hackaday projects and talks, has built a reputation around the kind of electronics work that looks playful from across the room and brutally practical up close. His projects include miniature LED curiosities, custom hardware, PCB experiments, lighting installations, and the sort of one-off engineering that artists love because it looks magicaland engineers respect because it survives real-world abuse.
The title “Mike Harrison Knows Everything About LEDs” is funny because no honest engineer would ever claim to know everything about anything. LEDs alone are a rabbit hole with a rabbit hole inside it, wearing a tiny headlamp. But Harrison’s work offers a rare lesson: LED design is not about making light. It is about making light reliable, controllable, efficient, serviceable, and beautiful without setting your power supply on an emotional fire.
Why LEDs Look Simple Until They Aren’t
At beginner level, an LED circuit is wonderfully approachable. You need a power source, an LED, and a current-limiting resistor. The LED has a forward voltage. The resistor limits current. The LED glows. Everyone smiles. Nobody calls the insurance company.
That simple circuit teaches several important ideas at once. LEDs are diodes, so polarity matters. They require forward current, not merely “some voltage.” Their brightness depends on current. Their color is tied to semiconductor materials and, in white LEDs, phosphor conversion. Their life depends heavily on staying within electrical and thermal limits.
But scale changes everything. One LED on a breadboard is a lesson. One thousand LEDs in a public installation is a negotiation with physics, manufacturing tolerances, cable resistance, heat, data timing, maintenance crews, and the person who insists that “warm white” should feel like candlelight but also be bright enough to locate a dropped earring.
This is where Harrison’s practical philosophy becomes useful. He is not only interested in whether an LED turns on. He cares about how many LEDs can be driven, how precisely they can be dimmed, how smoothly colors blend, how long they can run, and how easily a system can be configured when it is already installed in a museum, airport, city space, theater, or similarly unforgiving environment.
The First Rule: LEDs Want Current, Not Vibes
One of the biggest beginner mistakes is treating LEDs like tiny light bulbs that can simply be connected to a voltage source. That can work only under specific conditions, and often only briefly. LEDs are current-driven devices. Once forward voltage is reached, current can rise quickly. Without a resistor or driver to control that current, the LED may become bright, then brighter, then historically significant.
A current-limiting resistor is the classic entry-level solution. The calculation is simple in spirit: subtract the LED’s forward voltage from the supply voltage, then choose a resistor that sets the desired current. In practice, a responsible designer also checks resistor power dissipation, LED current rating, temperature, and variation between parts.
For a single indicator LED, a resistor is usually enough. For high-power LEDs, long strips, dense arrays, or installations where color consistency matters, constant-current drivers become far more important. A good LED driver does more than prevent smoke. It regulates brightness, improves efficiency, protects against faults, supports dimming, and helps multiple channels behave predictably.
Why PWM Dimming Is More Than “Blinking Really Fast”
Pulse-width modulation, or PWM, is often explained as turning an LED on and off very quickly so the eye sees an average brightness. That explanation is accurate enough for a classroom, but incomplete for serious LED work. PWM frequency, duty cycle resolution, driver response, switching losses, flicker, camera artifacts, and color stability all matter.
Analog dimming changes LED brightness by changing current. PWM dimming changes perceived brightness by changing the duty cycle while keeping the LED current more consistent during the “on” portion. PWM often gives better color stability because LEDs can shift color when driven at different current levels. That matters in RGB and RGBW systems, where a small mismatch can turn a carefully designed amber glow into “haunted refrigerator peach.”
Harrison’s LED thinking lives in this practical zone. The question is not merely “Can I dim it?” The better question is “Can I dim it smoothly, repeatably, without visible stepping, without flicker, without color shift, and without making the installation impossible to service?” That is the difference between a demo and a professional lighting system.
Gamma Correction: Because Human Eyes Are Weird Little Liars
LEDs do not look brighter to humans in a perfectly linear way. Double the electrical value and the perceived brightness does not simply feel doubled. Our eyes respond nonlinearly, which is why LED fading can look strange when controlled with raw linear values.
Gamma correction compensates for this. It maps control values to brightness levels in a way that appears smoother to human vision. Without gamma correction, a fade can feel abrupt at the low end and sleepy at the high end. With it, dimming feels more natural, especially in decorative lighting, stage effects, art installations, and addressable LED animations.
This is one reason LED expertise gets deep quickly. A beginner sees a number from 0 to 255. A lighting engineer sees perceptual response, driver bit depth, color channel matching, PWM frequency, refresh timing, and the silent judgment of every smartphone camera in the room.
RGB, RGBW, and the Trouble With “White”
RGB LEDs mix red, green, and blue light to create a broad range of colors. In theory, equal parts red, green, and blue should make white. In reality, RGB white can look cold, uneven, or strangely artificial. That is why RGBW LEDs add a dedicated white channel, improving efficiency and producing a more convincing white for many applications.
White light quality is often described using color temperature and color rendering. Color temperature tells us whether light appears warm, neutral, or cool. Color rendering index, or CRI, estimates how naturally colors appear under a light source. A high CRI LED can make wood, skin, fabric, food, and paint look more accurate. A low-quality light can make a living room feel like a bus station at 2:17 a.m.
For installations, this matters. A lighting project may need saturated color one moment and pleasing white light the next. Museums care about color fidelity. Restaurants care about food looking edible. Retailers care about fabric not looking like it lost a custody battle with fluorescent lighting. Engineers must choose LEDs and drivers that support the visual goal, not just the electrical requirement.
Power Planning: The Part Everyone Ignores Until the Wires Get Toasty
Addressable LED strips make ambitious projects look deceptively easy. Buy a reel. Connect a microcontroller. Load a library. Bask in rainbow glory. Then the far end of the strip turns brownish, the power supply wheezes, and the wiring begins auditioning for a role as a space heater.
Dense LED arrays consume serious current. A single RGB pixel at full white may draw far more current than expected because all three color channels are active. Multiply that by hundreds or thousands of pixels and suddenly the project needs power injection, adequate wire gauge, fusing, voltage drop calculations, and a power supply selected with margin rather than optimism.
This is where practical LED experts sound less like magicians and more like electricians with trust issues. They plan current paths. They avoid routing huge loads through tiny connectors. They think about failure modes. They design installations so one bad segment does not take down the entire show. They label things. They respect connectors. They know that “temporary wiring” has a dark habit of becoming permanent.
LED Heat: Cooler Than Incandescent Does Not Mean Cold
LEDs are efficient compared with incandescent lighting, but they still generate heat. The difference is where that heat goes. Incandescent bulbs radiate much of their energy as heat. LEDs send less heat forward with the light, but heat still builds in the semiconductor junction and must be managed through the package, PCB, heatsink, fixture, or surrounding structure.
Heat affects efficiency, color, and lifespan. Run LEDs too hot and they degrade faster. Push high-power LEDs without thermal design and their output drops, their color can shift, and their life expectancy becomes a polite fiction. In large installations, thermal planning is not optional. It is the quiet reason a project still looks good after months or years instead of fading into expensive sadness.
Good LED design includes thermal paths, conservative current settings, airflow awareness, and realistic assumptions about ambient temperature. A product tested on an open bench may behave differently inside an enclosure, behind acrylic, in direct sun, or above a ceiling where air moves with the enthusiasm of a tired sloth.
Mike Harrison’s Real Lesson: Installations Need Practical Configuration
One of the most memorable ideas associated with Harrison’s LED work is the value of practical configuration. In multi-part installations, relying entirely on software can be elegant until someone needs to replace a module on-site. Then elegance becomes a laptop hunt, a firmware version mystery, and a person standing on a ladder asking why the blue channel is now speaking fluent chaos.
Physical configuration methods, such as DIP switches or simple address settings, may look old-fashioned, but they can be extremely useful in the real world. They make modules identifiable. They reduce dependency on hidden software state. They allow technicians to configure hardware without needing a developer environment, source code, or a ceremonial offering to the USB driver gods.
This is the difference between a clever project and a maintainable system. Clever projects impress builders. Maintainable systems impress everyone who has to keep them alive after the original builder has moved on to a new obsession involving lasers, clocks, or suspiciously small circuit boards.
Tiny LEDs, Huge Lessons
Harrison is also associated with beautifully tiny builds, including miniature LED blinky projects that compress a complete flashing circuit into an absurdly small footprint. These projects are fun because they are small, but they are impressive because they force discipline. At tiny scale, every component choice matters. The microcontroller package, capacitor size, LED footprint, energy storage, soldering technique, and even handling method become part of the design.
A tiny LED blinker is not just a novelty. It is a lesson in constraints. What is the smallest useful circuit? How little energy can it consume? How do you assemble it? How do you test it without launching it across the room with tweezers? How do you make something that is simultaneously ridiculous and technically elegant?
That spirit explains why Harrison’s work appeals to makers. It combines curiosity with precision. It says: yes, electronics can be playful, but the fun improves when the engineering is solid.
What Makers Can Learn From Harrison’s LED Approach
1. Read the Datasheet Before the LED Becomes a Fuse
Datasheets are not decorative PDFs. They contain forward voltage, recommended current, peak current, thermal limits, viewing angle, wavelength, luminous intensity, and package information. If your design depends on an LED behaving consistently, the datasheet is not optional reading. It is the map that keeps you out of the swamp.
2. Use the Right Driver for the Job
A resistor is fine for a simple indicator. A constant-current driver is better for power LEDs and consistent output. Dedicated LED driver ICs can handle dimming, fault detection, current regulation, and multi-channel control. Choosing the right driver is often the difference between a project that works once and a system that works every day.
3. Budget Power Like a Pessimist
LED projects are full of optimistic current estimates. Build in margin. Use adequate wire. Inject power along long strips. Fuse large supplies. Avoid asking tiny connectors to carry heroic current. Electricity has no respect for your mood board.
4. Design for Human Vision
Smooth fades require more than changing numbers. Use gamma correction. Consider PWM resolution. Test at low brightness, where stepping and flicker are most obvious. If cameras will record the installation, test with cameras too.
5. Design for Maintenance
Large LED systems should be serviceable. Label modules. Make addressing clear. Avoid hidden dependencies. Consider physical configuration. Leave room for connectors. Document the system. Future you deserves kindness.
Why LEDs Became the Maker Movement’s Favorite Gateway
LEDs are small, cheap, visible, forgiving, and instantly rewarding. They turn invisible electrical behavior into something the eye can understand. That makes them perfect for learning microcontrollers, soldering, circuit design, power management, programming, and debugging.
The classic Arduino blink example remains iconic because it gives beginners immediate feedback. Code changes. Hardware responds. The invisible becomes visible. It is the electronics equivalent of a first chord on a guitar: simple, slightly noisy, and powerful enough to start a lifelong obsession.
But LEDs also scale upward beautifully. The same basic concept can become a wearable badge, a mood lamp, a clock, a sculpture, a stage prop, a building facade, or an interactive wall. Few components travel so smoothly from “my first circuit” to “major public artwork.”
The Professional Side: When LEDs Meet Art
One of the most interesting parts of Harrison’s career is the intersection of electronics and art. Artists often care deeply about the result but not necessarily about the circuitry. They may ask for light to shimmer, pulse, breathe, ripple, follow people, react to sound, vanish into architecture, or create an atmosphere that cannot be described without waving both hands.
The engineer’s job is to translate that vision into hardware that works. That means choosing LEDs, optics, diffusers, drivers, power supplies, sensors, wiring, control protocols, and enclosures. It means building prototypes, testing assumptions, and simplifying wherever possible. It also means preparing for the realities of installation: dust, vibration, heat, curious fingers, long cable runs, and the occasional terrifying sentence, “Can we make it brighter?”
In that world, LED knowledge is not trivia. It is survival equipment. The system must look effortless because the engineering underneath did the hard work quietly.
Common LED Mistakes That Harrison’s Style Helps Avoid
The first common mistake is underestimating current. A strip that looks harmless can draw several amps. A sculpture with thousands of LEDs may require serious power distribution. The second mistake is ignoring voltage drop. Long runs of wire or copper traces can cause color shifts and dimming at the far end.
The third mistake is trusting default brightness curves. Raw LED values rarely look visually smooth. The fourth mistake is forgetting thermal behavior. The fifth is building a system that only its creator can configure. The sixth is assuming every LED strip, driver, controller, or dimmer behaves like every other one. In LED work, “compatible” is a word that should be verified, not admired from a distance.
Harrison’s practical approach encourages builders to test early, test realistically, and design for the environment where the project will actually live. A kitchen-table demo is useful, but it is not the final boss.
The Beauty of Knowing Enough to Be Careful
The more you learn about LEDs, the less casual you become. That is not a bad thing. It means you start seeing the hidden engineering behind smooth fades, clean colors, consistent brightness, and installations that do not randomly fail after opening night.
Mike Harrison’s reputation around LEDs is not about memorizing every LED part number on Earth. It is about understanding the system-level behavior: current, heat, color, perception, control, power, wiring, configuration, and reliability. That is the knowledge that turns blinking lights into professional lighting.
Extra Experiences and Practical Reflections: What Working With LEDs Teaches You
Anyone who spends enough time building LED projects eventually collects a private museum of small disasters. There is the first LED installed backward. The resistor that was “probably fine” until it became a fingertip branding iron. The LED strip that worked perfectly until full white turned the power supply into a disappointed toaster. The breadboard jumper that was not quite seated. The microcontroller pin that bravely gave its life because someone forgot that LEDs need current limiting, not motivational speeches.
These experiences are not failures in the dramatic sense. They are tuition. LEDs teach electronics because they respond immediately. If polarity is wrong, nothing happens. If current is too high, something too exciting happens. If the PWM frequency is too low, the flicker becomes obvious. If power injection is missing, the far end of an RGB strip starts making artistic choices nobody approved.
One practical lesson is to prototype at the same brightness and density the final project will use. Many LED builds look perfect at 20 percent brightness on a desk. Then someone tests full brightness and discovers that the power system was designed with the financial confidence of a raccoon holding a credit card. Always test worst-case current. Turn on full white. Let the system run. Touch nothing dangerous, but check for warm connectors, warm wires, hot regulators, and unhappy power supplies.
Another lesson is that diffusion matters almost as much as the LEDs themselves. Bare LEDs can be harsh, dotted, and distracting. Good diffusion turns points of light into a surface, a glow, or a shape. But diffusion also absorbs light, changes color perception, traps heat, and may require more brightness. That means optics and mechanics are part of the electrical design whether you invited them or not.
Color mixing is another humbling topic. Two LED strips labeled “warm white” may not match. RGB values that look balanced on one batch may look slightly green on another. Camera sensors may see flicker or banding that your eyes ignore. A lighting design that looks gorgeous in a dark room may disappear in daylight. The best habit is to test under real viewing conditions, with the actual diffuser, enclosure, brightness, and ambient light.
Maintenance is the lesson people learn last, usually while standing on a ladder. A beautiful LED installation should be easy to repair. Use connectors that can be reached. Keep spare modules. Label cables. Document addresses. Save firmware. Write down power supply ratings. Add test modes. Make it possible for someone else to understand the system without summoning you from a vacation.
The biggest experience-based lesson is restraint. LEDs make it easy to add more: more pixels, more brightness, more animation, more color, more “wow.” But the best LED projects often use control rather than excess. A slow fade can be more elegant than a rainbow explosion. A well-rendered warm white can be more impressive than a frantic chase pattern. Good lighting supports the experience; it does not always need to shout, “Look, I know SPI!”
That is why Mike Harrison’s LED work remains so instructive. It respects both sides of the craft: the playful thrill of making light move and the serious engineering needed to make that movement dependable. LEDs are easy to start with and difficult to master, which is exactly why they remain so addictive. One blink teaches you the basics. A thousand synchronized LEDs teach you humility, power distribution, human perception, and possibly new vocabulary.
Conclusion: LEDs Reward the Curious and Punish the Casual
Mike Harrison knows LEDs in the way that matters most: not as isolated components, but as parts of living systems. He understands that LED design is electrical, visual, thermal, mechanical, and human all at once. A successful LED project is not just bright. It is controlled, consistent, maintainable, and appropriate for its purpose.
For beginners, LEDs are still the perfect starting point. For professionals, they remain a serious engineering challenge. Between those two worlds sits the joy of making light do exactly what you imaginedand then making sure it keeps doing that after the demo, after the applause, and after someone unplugs the wrong cable.
So yes, “Mike Harrison Knows Everything About LEDs” is a playful title. But it points to a real truth: the deeper you go into LEDs, the more you realize how much there is to learn. And if your first lesson is a blinking LED, your next lesson should be this: light is easy. Good light is engineering.
Note: This article is fully rewritten in original American English for web publishing and synthesizes real electronics, lighting, and maker-engineering information without inserting source links into the body content.
