portrait of eric brown
codengo.

within some software engineers...
there is a machine.

move to revealdrag to revealscroll to exploretap to explore

engineer & ai researcher

eric
brown.

you know the brands.
meet the engineer.

i build the go services behind real products and go deeper into the architectures behind ai.

step inside the work
eric d. brownthe person behind the code
40+ years buildinggo since 2013

01 / a few things i’ve worked on

familiar on the outside.
my work is inside.

eight chapters. eight objects.
hover to open. select for the story.

different products. the same drive to understand what’s underneath.go one layer deeper
the next layerskip to the research

from backend apis to ai architecture.

the services behind
the experience.

the architecture behind
the intelligence.

esn / kan / mlp / transformers / llmsfrom production systems to first principles

02 / independent ai research

open the model.
follow the evidence.

what’s actually in a model? what did it learn? what can we prove?

my independent research practice

optrenium.ai

my research into neural architectures,
learning systems, and model internals.

byte-level inspection.
learning from scratch.
evidence you can inspect.

03 / the person behind the code

eric d. brown

engineer.
researcher.
builder.

haslet, texas
working with teams everywhere.
the professional profile

my father built the computer.
i wanted to understand it.

in 1981, my father built a zenith heathkit h89. by seven, i was teaching myself basic. that early fascination became a lifelong drive to understand how things work and to build them myself.

from c and c++ to go in late 2013, i’ve always been drawn to the machinery beneath the abstractions. today, that means neural architectures, learning systems, and the mathematics behind intelligence.

i bring that same curiosity to engineering teams: clear thinking, honest evidence, practical mentorship, and systems that hold up after they ship.

40+years writing code
2013my first year in go
1981the spark

a heathkit h89 at home.

1984the first code

basic. age seven.

1990sunder the hood

c, c++, and systems.

2013finding go

simplicity. concurrency.

2024 →building intelligence

first-principles ai research.

how i think

make it work. make it efficient.
never stop learning.

my engineering philosophy

the résumé / every chapter

the full record.

roles, responsibilities, and the technologies i worked with.

full-time · remote

support enterprise consulting engagements across api integration, system design, and ai development. updated api systems for capital one’s discover merger, adding support for discover card metrics and related integration requirements. validated merger-related changes through a coordinated, multi-week manual testing effort covering end-to-end api workflows. currently work with amazon on a proprietary calculation tool with integrated ai pipelines. provide technical direction through architecture discussions, implementation, code review, and collaboration with client engineering teams.

api integrationai pipelinessystem designend-to-end validationtechnical leadership

“he is eager to learn and faces any challenge head-on. any team would be lucky to have him on their side.”
mike deremusformer teammate · linkedin recommendation, june 2024

04 / notes from the workbench

a place to show
the working.

a new journal on model architecture, go, and what happens when an experiment meets reality.

open the journal
codengo / field notes
notes on
how things
work_
a new chapter

open to the right challenge

have a hard
problem?
let’s build.

ai architecture, backend apis, or a team that needs an experienced technical lead. tell me what you’re working on.

haslet, texas · remote collaboration

let’s start with your idea

i’m looking for help with
start a conversation

opens your email app with your brief. prefer linkedin? connect here ↗