matthew brister

programmer

about

i build things that scale. every project i touch gets designed with modularity as the core principle because software should grow, not break under pressure.

i don't like people who don't make large projects modular. if you're going to build something significant, architect it right from the start.

"if it's not modular, it's not worth building"

commitment metrics

2+
years java
1
year c++
∞
too many hours debugging
100%
modular code

skills

java
minecraft modding taught me modular architecture. every system i build follows component-based design patterns.
c++
performance-critical applications. memory management, optimization, and understanding how code actually runs on hardware.
python
currently learning and experimenting with pygame. rapid prototyping and data processing.
system design
distributed systems, microservices, event-driven architecture. building things that don't fall over.

projects

approach

// every project starts the same way
if
(project.isLarge()) {
  architecture = "modular";
  design = "component-based";
  scalability = "priority";
} else {
  // still modular, just simpler
  architecture = "clean";
}

i approach every problem by breaking it into independent, testable components. this isn't just good practice - it's the only way to build systems that last.

contact

email: matthewbristergaming@gmail.com

github: github.com/BarneyCompiler