1Lucas1apk · 20 years old · Developer
I break things to understand them. Sometimes I even fix them.
Hey, I'm Lucas.
I write code, get curious about things I probably shouldn't be spending three hours investigating, and occasionally end up turning that curiosity into an actual project.
Most of my work happens around JavaScript, TypeScript, and Node.js. I enjoy building libraries, messing with audio-related stuff, and figuring out what happens behind the scenes when software does something unexpected.
I'm not the kind of person who can just accept that something works and move on. I usually want to know why it works, what happens when it doesn't, and whether there's a better way to do it.
Which is great for learning. Not always great for the amount of time I spend on a tiny bug.
A project born out of my interest in music bots and the systems that make them work.
I built Moonlink.js to give developers a way to manage music playback in their Discord bots without having to deal with every underlying detail themselves. Along the way, there's plenty to figure out about player state, events, connections, and all the little things that can go wrong during playback.
It's one of those projects where a seemingly small feature can teach you much more than expected.
🪐 NodeLink
Audio, but with more things happening behind the curtain.
NodeLink is part of my work around audio streaming and media playback with Node.js. The interesting part isn't simply getting audio from one place to another; it's understanding the chain of components responsible for making that happen.
Formats, decoders, data flowing through a pipeline, unexpected behavior, performance quirks — there's always another layer to investigate.
🪲 Reverse engineering & the rabbit holes
This is where curiosity can get a little out of hand.
I enjoy digging into existing software, reproducing strange behavior, tracing execution paths, and figuring out how something works when the answer isn't immediately obvious. Sometimes the goal is to understand an implementation; sometimes it's to reproduce a bug that refuses to make sense.
My favorite part is that moment when a mess of observations finally starts connecting.
It's a bit like solving a puzzle, except the puzzle occasionally crashes, lies to you, and gives you a completely different result on the next run.
JavaScript and TypeScript are where I spend most of my time. I also explore other languages when a project gives me a good reason to step outside my usual environment.
Beyond languages, I spend time with audio processing, data persistence, debugging, APIs, and the internal mechanics of software. My interests tend to follow whatever technical problem has caught my attention lately.
I'm still figuring things out — and that's kind of the point.
Understanding systems beyond their public interfaces. Making complicated behavior reproducible. Exploring how components fit together. Finding out whether a strange bug is actually a bug or just a very convincing misunderstanding.
I don't always start with a clear answer. More often, I start with a question, a test case, and a terminal full of output that makes absolutely no sense.
Eventually, it usually starts making sense.
Discord: 1lucas1apk
🔍 There is probably a simpler explanation. I just haven't found it yet.