five years ago i was part of a team called lucent.
looking back, this was probably my first real introduction to engineering something beyond the technical side of things. not necessarily writing code, but building systems, managing people, establishing an identity, and figuring out how to make different moving parts work toward the same vision.
i was 18 at the time.
we had acquired the branding, reworked the entire identity, and started building our own culture around what we wanted lucent to represent. we ran an extremely lean operation, but somehow managed to establish a pretty recognizable name for ourselves within the fortnite community.
what's interesting to me now isn't necessarily what we accomplished, but how differently i'd approach the exact same opportunity today.
back then, we weren't particularly content-centric. we cared about the identity, the people, the edits, and the reputation we were building. monetization wasn't really at the forefront of our decisions.
and sometimes that's just how it goes. you can genuinely love building something without ever seeing a financial return from it.
but five years later, i realize how much opportunity exists in the infrastructure surrounding content. distribution, partnerships, brand deals, creative direction, and the ability to turn a community into something economically sustainable.
a content team today could operate like a small media company if the right people understood their roles and shared the same hunger. the talent matters, but so does the system supporting it.
that's probably the biggest thing engineering has taught me. building something people enjoy is one challenge. building something that can sustain itself is an entirely different discipline.
i also think there's something worth saying about creative integrity. know what you want to put into the world before you start chasing whatever gets the most attention. shortcuts are always available, but so are the consequences of taking them.
anyways, i was going through some old work and came across this fortnite new year's teamtage we had produced.
funny how something you worked on at 18 can still teach you things five years later.
some projects pay you in money. others pay you in perspective.
this one gave me a little bit of both, just not in the way i understood back then.
the binance hack is a reminder of something i think more people building in crypto need to take seriously.
we're reaching a point where the tools available to exploit a product are advancing just as quickly as the tools being used to build one.
there's been a lot of emphasis on how quickly we can ship, how much we can automate, and how accessible development has become. not nearly enough conversation about the vulnerabilities that come with that accessibility.
especially in crypto, where you're not just handling user data but potentially someone's entire financial position.
i think more builders need to spend time understanding how their systems can be compromised rather than exclusively focusing on how efficiently they can be developed.
security is an architectural decision, not something you revisit once a product starts gaining traction.
the more financial responsibility your product takes on, the less room you have to treat security as an afterthought.
Looking to expand my network and find some reliable resources in the prediction market space.
If you're actively trading markets like UFC, MLB, NBA, NFL, boxing, crypto, or even more niche categories, I'd like to know where you're sourcing information and identifying high conviction positions.
Open to specialized communities, research groups, or more generalized networks. Ideally looking for people with a proven, transparent track record.
If you can point me toward a solid group and I end up joining, I'll gladly send something your way. Happy to reward anyone who helps get me into the right pipeline.
DMs open. Looking for quality information and people who take their research seriously.
started working through a python course on @codedex_io.
what initially caught my attention was the pixel-inspired aesthetic and interactive approach to learning. something about it makes the process feel a little more inviting.
they also have a pretty extensive library of tutorials to explore.
still early in the process, but finding myself more interested in how different approaches to learning can shape the experience itself.
i’ve spent a lot of time imagining the things i want to create, but somewhere along the way, i realized i was more focused on what i wanted to build than understanding what it actually takes to build something.
i want to change that.
i’m becoming more interested in the process itself. the thinking, the problem-solving, the countless small decisions that make something work.
going deeper into programming, interfaces, and engineering. experimenting with ideas, questioning what i know, and documenting what i learn along the way.
less concerned with having something to show, more interested in developing the understanding to create it.
here’s to humble beginnings.