IT & Technology
Siphiwe
Siphiwe
Khumalo
I work across the stack — hardware, networks, infrastructure, cloud, and code — to keep technology doing what it's supposed to do.
I work across the stack — hardware, networks, infrastructure, cloud, and code — to keep technology doing what it's supposed to do.
I'm Siphiwe Khumalo — most people call me Ronnie. I'm interested in technology as a whole system, not just the part that's visible on screen. A slow computer, a flaky connection, a site that won't load, a business process held together with spreadsheets — I want to know what's actually happening underneath, and then fix it.
Day to day that means I move between different layers of the same problem: sorting out a hardware or network issue one moment, writing and shipping code the next. I currently split my time between freelance development work and hands-on IT support, alongside studies in Tourism — a background that keeps me thinking about technology from the perspective of the people actually using it, not just the systems themselves.
Projects completed
Years building & troubleshooting
Layers of the stack I work across
Most problems don't stay in one layer. A "slow website" might actually be a network issue. A "broken system" might just be a hardware fault upstream. I try to start wherever the problem is actually happening, not wherever it's easiest for me to look.
This is roughly how I think about the stack — and where in it I tend to spend my time.
Diagnosing and fixing the physical machines — PCs, peripherals, the stuff that fails first.
Getting devices talking to each other reliably, from Wi-Fi to wired infrastructure.
The wiring behind the scenes — including systems like CCTV and VoIP that businesses depend on daily.
Microsoft 365, cloud services, and the administration that keeps them running smoothly.
Building the applications and websites people actually interact with.
Where all of the above has to translate into something that just works for the person relying on it.
Not a skills list so much as a map of the areas I'm actively working in and around, from the hands-on to the behind-the-scenes.
A handful of the things I've actually built — mostly self-directed, all used as a chance to learn something specific.
HTML · CSS · JavaScript · OpenAI API
HTML · CSS · JavaScript
HTML · CSS · JavaScript · TMDB API
HTML · CSS · JavaScript · Quotes API
HTML · CSS · JavaScript · AI Integration
A developing technology professional, not a finished one — this is the order things actually happened in.
Working in a hands-on IT support capacity, handling day-to-day hardware, network, and systems issues — the practical, on-the-ground side of keeping technology running.
Developed custom web solutions for small businesses and startups, including promotional pages, interactive tools, and e-commerce platforms — delivering 15+ projects to date.
Creative problem-solving, client communication, and project management, with a consistent emphasis on responsive design, performance, and actually understanding the person using what I build.
Studies in Tourism, exploring the intersection of technology and digital storytelling — a reminder that most of what I build is ultimately for someone outside of tech.
Going deeper than day-to-day troubleshooting into how networks and infrastructure are actually designed.
Building a more deliberate understanding of the risks behind the systems I already support.
Extending Microsoft 365 and cloud services knowledge beyond day-to-day administration.
Pushing the software side further — more advanced patterns and interactive, three-dimensional interfaces.
I could narrow down to just IT support, or just development. I'm not in a hurry to do either. The version of my career I'm most interested in is one where the hardware, network, infrastructure, and software knowledge all keep informing each other — because in practice, that's how most real problems actually show up.
Longer term, that probably means growing into a role that sits across IT and technical systems more broadly, while keeping software and web development as a skill I keep sharp rather than one I set aside.
Open to conversations about IT, infrastructure, or development work — or just to talk through a technical problem you're stuck on.
I work across the stack — hardware, networks, infrastructure, cloud, and code — to keep technology doing what it's supposed to do.
I'm Siphiwe Khumalo — most people call me Ronnie. I'm interested in technology as a whole system, not just the part that's visible on screen. A slow computer, a flaky connection, a site that won't load, a business process held together with spreadsheets — I want to know what's actually happening underneath, and then fix it.
Day to day that means I move between different layers of the same problem: sorting out a hardware or network issue one moment, writing and shipping code the next. I currently split my time between freelance development work and hands-on IT support, alongside studies in Tourism — a background that keeps me thinking about technology from the perspective of the people actually using it, not just the systems themselves.
Projects completed
Years building & troubleshooting
Layers of the stack I work across
Most problems don't stay in one layer. A "slow website" might actually be a network issue. A "broken system" might just be a hardware fault upstream. I try to start wherever the problem is actually happening, not wherever it's easiest for me to look.
This is roughly how I think about the stack — and where in it I tend to spend my time.
Diagnosing and fixing the physical machines — PCs, peripherals, the stuff that fails first.
Getting devices talking to each other reliably, from Wi-Fi to wired infrastructure.
The wiring behind the scenes — including systems like CCTV and VoIP that businesses depend on daily.
Microsoft 365, cloud services, and the administration that keeps them running smoothly.
Building the applications and websites people actually interact with.
Where all of the above has to translate into something that just works for the person relying on it.
Not a skills list so much as a map of the areas I'm actively working in and around, from the hands-on to the behind-the-scenes.
A handful of the things I've actually built — mostly self-directed, all used as a chance to learn something specific.
HTML · CSS · JavaScript · OpenAI API
HTML · CSS · JavaScript
HTML · CSS · JavaScript · TMDB API
HTML · CSS · JavaScript · Quotes API
HTML · CSS · JavaScript · AI Integration
A developing technology professional, not a finished one — this is the order things actually happened in.
Working in a hands-on IT support capacity, handling day-to-day hardware, network, and systems issues — the practical, on-the-ground side of keeping technology running.
Developed custom web solutions for small businesses and startups, including promotional pages, interactive tools, and e-commerce platforms — delivering 15+ projects to date.
Creative problem-solving, client communication, and project management, with a consistent emphasis on responsive design, performance, and actually understanding the person using what I build.
Studies in Tourism, exploring the intersection of technology and digital storytelling — a reminder that most of what I build is ultimately for someone outside of tech.
Going deeper than day-to-day troubleshooting into how networks and infrastructure are actually designed.
Building a more deliberate understanding of the risks behind the systems I already support.
Extending Microsoft 365 and cloud services knowledge beyond day-to-day administration.
Pushing the software side further — more advanced patterns and interactive, three-dimensional interfaces.
I could narrow down to just IT support, or just development. I'm not in a hurry to do either. The version of my career I'm most interested in is one where the hardware, network, infrastructure, and software knowledge all keep informing each other — because in practice, that's how most real problems actually show up.
Longer term, that probably means growing into a role that sits across IT and technical systems more broadly, while keeping software and web development as a skill I keep sharp rather than one I set aside.
Open to conversations about IT, infrastructure, or development work — or just to talk through a technical problem you're stuck on.