The idea behind Nudox

I started building Nudox, over two years ago, with zero knowledge, zero expectations for anything, just a rough idea on what I felt was missing. I've, always been a bit obessed with developer tools. With productivity and improving my systems and processes. This has meant a lot of things, but largely came out of my insistence on reading the absolute maximum wealth of things that I could get my hands on. Over the three years before, I had read over 10 thousand articles, MANY of them on personal success and the ability of self. And this isn't some crazy revalation, and proved to be very NOT useful to the rest of my life. In fact, very little, at all changed or progressed during this time in my life. But I did have a lot of ideas, on what could maybe come next. And as I began to get more integrated into programming, it became very obvious, very quickly, my view that: programming is an information game.

And what I mean by this is that, programming, much like any other knowledge worker job, has a classic twofer problem. How to solve an issue, and the implementation of the issue. The plan, and the doing. And unlike other knowledge worker jobs, coding is practically pure. There's less uncerainity than every other information gig, as the environment you work within is actually incapable of producing a random event (absent strikes from the sun). The most complicated organizations, DARPA, and NASA, take this to an extreme, spending the majority of the time before attempting a programming project in the planning and organization phase. For the rest of developer-kind, it's been prohbitively expensive to take the upfront time to establish the bearings within a codebase, of any size. Much less the kinds of giants that most go to, when they tackle the work of a large FAANG coorperations fifteenth microservice.

Only worsening this issue is the matter of coding agents, as they've come to approach near total domination of the blue collar programmer. Because, unlike average engineers, they aren't granted with ANY kind of onboarding time, and are expected to do much larger, and much more work, in pursuit of a goal. So returning to the phrase: programming is an information game. Programming, is far more than your individual skill as a developer, a matter of your ability to make sense of the situation you work within. The landscape of things and people that dominate the understanding of where you are. Of how things fit together, of what you need to do both before the work, as far as referencing, and planning, and after, in terms of testing, and following up. The best programmers only are able to write the best code because they understand the persons who go on to judge their work. How they understand the world. How to fit their expertise in the greater picture.

If you've worked with coding agents, you know this isn't an approach that they share. They don't share any memory, in fact. So you're always putting the rock further up the hill, as far as skills, explanations of where things are, and more. But the longer they work, the more code which is produced, they always roll back down: producing more symbols, more junk, breaking more standards. What I thought of two years ago, wasn't even for them, it was for me.

It was this perception that the coding I saw myself doing, the big ambitious kind (I've always been a dreamer) was destined to be hamstrung by my lack of ability to get my bearings quickly. To see, at a scale, how things fit together in a cohesive picture, without two months of talking with coworkers. And I'm glad it's only become more relevant :)