About andyism

Technical experience shaped inside real communities.

I’m Andy—an IT graduate with a cyber security background and hands-on experience across systems administration, gaming communities, server infrastructure, web development and automation.

What I bring

Technical delivery with operational context.

I hold a BSc (Hons) in Cyber Security, awarded 2:1, and have practical experience across Minecraft administration, Discord operations, Lua development, websites, automation, networking and technical troubleshooting.

My community work includes helping operate a Roblox community approaching one million members, running a cross-platform Minecraft SMP, moderating creator communities and completing paid Discord setup work.

01Software and webPython, Java, JavaScript, TypeScript, SQL, Lua, APIs and web technologies.
02InfrastructureWindows, Linux, servers, networking, permissions, integrations and automation.
03Security thinkingAccess control, hardening, backups, logging, recovery and practical risk reduction.
04Community operationsModeration, staff workflows, incidents, events, documentation and member support.
Experience in context

The useful overlap between technology and people.

Communities rarely fail because of one missing plugin. The hard part is making systems, staff processes and member expectations work together.

Systems

Build and troubleshoot

Servers, websites, bots, permissions, integrations and operational tooling across multiple platforms.

Scale

Operate real communities

Experience with small private groups, public gaming servers, creator spaces and a community approaching one million members.

Support

Stay useful after launch

Documentation, maintenance and practical handover are treated as part of the build rather than optional extras.

Working principles

How I want projects to feel.

Clear communication and maintainable choices are part of the technical quality—not separate from it.

01 · HONEST

No mystery scope

Deliverables, assumptions, exclusions and third-party costs should be clear before work begins.

02 · PRACTICAL

Use the simplest good solution

Complexity is only worthwhile when it solves a real requirement or reduces future work.

03 · SECURE

Protect access and recovery

Permissions, backups and ownership are considered while building, not after an incident.

04 · DURABLE

Leave it understandable

The finished system should still make sense when it needs to be changed months later.

Working together

A few practical answers.

Do you work only with gaming communities?

No. Gaming communities are a strong area of experience, but website, automation and infrastructure work can also suit creators and small businesses.

Can you work with another developer or team?

Yes, where responsibilities, access, communication and ownership are clear. Existing conventions should be respected unless there is a reason to change them.

Can you sign a confidentiality agreement?

Potentially. The scope and terms should be reviewed before confidential material or production access is shared.

Work with me

Need something built, repaired or made easier to run?

Describe the goal, current setup and the outcome you want. A technical specification is optional.