Skip to content
View derrekc's full-sized avatar

Organizations

@duke-libraries

Block or report derrekc

Block user

Prevent this user from interacting with your repositories and sending you notifications. Learn more about blocking users.

You must be logged in to block users.

Content in all repositories owned by your account will be closed.
Maximum 250 characters. Please don’t include any personal information such as legal names or email addresses. This note will only be visible to you.
Report abuse

Contact GitHub support about this user’s behavior. Learn more about reporting abuse.

Report abuse
derrekc/README.md

Hey, I'm Derrek. 👋

Derrek L. Croney
Software Engineer | Systems Thinker | Problem Solver

I'm a software engineer who enjoys building things that solve real problems—and figuring out why things that should work occasionally don't.

My professional background spans application development, backend services, systems integration, Linux infrastructure, and production operations. I've spent much of my career working at the intersection of writing software, keeping it running, and helping people make sense of the technology they depend on.

I still enjoy getting my hands dirty with code. I also enjoy bringing people together to solve difficult problems.

Turns out those two interests work surprisingly well together.

🔧 What I work with

Languages: Go, Perl, JavaScript, PHP, SQL, Bash

Application development: REST APIs, backend services, data integration, Drupal, Dancer2

Infrastructure & deployment: Linux, Docker, Kubernetes/OKD, Helm, GitLab CI/CD, Apache

Data technologies: MariaDB, Solr, AWS DynamoDB integrations

Other interests: Application architecture, system reliability, troubleshooting, technical mentoring, and Agile/Scrum facilitation

🥚 Don't be afraid of breaking eggs.

That's something I regularly tell fellow developers when we're exploring unfamiliar technologies.

Experiment. Challenge assumptions. Try something different. Break things in environments where it's safe to do so—and learn why they broke.

Some of the most valuable engineering lessons come from discovering that your first approach wasn't quite right.

I believe curiosity should be encouraged, mistakes should become learning opportunities, and experience should make us more willing to explore—not less.

Of course, there's a difference between breaking eggs in development and making an omelet out of production. 😉

🧠 How I approach engineering

  • Solve the problem, not just the symptom. Understanding why something fails is often more valuable than making the error disappear.
  • Build for the people who come after you. Maintainable software, clear documentation, and thoughtful architecture matter.
  • Deployment is part of development. If I build it, I want to understand how it runs, how it fails, and how it recovers.
  • Good engineering is collaborative. Some of the best solutions emerge when technical and nontechnical people understand one another.
  • Keep learning. Experience is useful. Curiosity keeps it from becoming obsolete.

🚀 What you'll find here

This GitHub account is a collection of personal experiments, utilities, learning exercises, and occasional side projects.

Not everything here represents my current professional technology stack, and much of my production engineering work lives in private organizational repositories.

I'm more interested in sharing useful ideas and thoughtful implementations than maintaining a daily contribution streak.

🎹 Beyond the keyboard

When I'm not working with computer keyboards, there's a good chance I'm sitting behind a musical one.

I'm also a pianist, songwriter, and independent music producer. Music production and software engineering have more in common than they initially appear to—both involve experimentation, problem-solving, and occasionally wondering why something sounded better yesterday.

I also enjoy retro arcade games, chess, and the occasional opportunity to appreciate an exceptionally bad programming joke.

💬 A final thought

I believe good software should solve meaningful problems, good systems should be understandable, and good engineers should never lose their curiosity.

Still writing code. Still learning. Still asking why.

And yes, sometimes the problem really is DNS.

Pinned Loading

  1. excel-to-json excel-to-json Public

    Small coding project where data from an Excel spreadsheet is converted to JSON

    Go

  2. asm-say-hello asm-say-hello Public

    Simple "Hello World" Using ASM (aarch64)

    Assembly 1