DEV Community

Cover image for Surviving a Neurotypical Industry: What "Janky" Workarounds Get You Through the Day?
Andrew Chadwick
Andrew Chadwick

Posted on

Surviving a Neurotypical Industry: What "Janky" Workarounds Get You Through the Day?

There is a running expectation in software engineering that everyone processes work exactly the same way. You are expected to read walls of linear documentation, jump seamlessly through rapid context-switching, and track everything chronologically in Jira.

But if you have a neurodivergent brain, that standard corporate workflow often feels like it was actively designed to work against you. We spend an astronomical "cognitive tax" every day just trying to operate in a business world set up for a completely different neurotype.

Whether you are untangling a massive C# architecture, writing complex SQL joins, or wrestling with JavaScript dependencies, the friction is real. For a long time, many of us focused on trying to "fix" our brains—trying to focus harder, read faster, or cope better.

But we are engineers. When a system is broken, we fix it or build better systems.

The Graveyard of Polished Products

To survive, we don't wait for permission. We build scripts to manage executive dysfunction. We create recursive, nested, color-coded Excel sheets to handle linear text. We hack together local AI prompts to translate dense documentation into plain English that our brains can actually parse.

These tools are usually chaotic. They are the definition of "janky" code. They have zero UI, they would fail a code review, and the world never sees them.

But they are the exact reason we can function and thrive in our roles.

Enter r/LobACob: A Workshop for Systemic Adaptation

It is time to stop hiding the messy hacks. We just launched r/LobACob a brand-new professional community for neurodivergent technical minds (developers, engineers, architects, PMs, and managers) and our neurotypical allies.
"Lob a Cob" is our metaphor for cognitive engineering. It’s about taking the chaotic, unstructured information thrown at us every day the "cobs"(or a roll if your from London) and building it into a functional, personalized system.

We are not here to cope. We are here to re-engineer our environments.

Who Should Join?

The ND Professional: This is your safe workshop. We want to see your real, raw survival tools. Code quality does not matter here; functional wins do. Share your messy scripts, your architectural mental models, and your strategies for stopping the "PM Interruption" from clearing your mental RAM.

The Neurotypical Ally & Manager: You are incredibly welcome here! Neurodivergent folks are forced to be masters of aggressive efficiency to reduce cognitive load. Hang around, and you will absolutely find systemic productivity hacks and workflow workarounds worth stealing for yourself. Good systems benefit everyone.

What is Your Workaround?

Tech’s standard operating system isn't working for everyone, but we know how to push fixes.
Over at r/LobACob, we have stickied a thread dedicated to these janky survival tools. Come introduce yourself and answer the question: What is the weirdest, messiest, most chaotic workaround you use just to get through your workday?
Let’s share the solutions that actually work.

Join the discussion at r/LobACob here!

Top comments (0)