Cloud
The focus of my degree and where most of my study time goes.
- AWS
- Cloud infrastructure concepts
- Virtualization
- Infrastructure fundamentals
Cloud & Network Engineering Student
I'm Cedric Cliatt Jr. — studying cloud and network engineering, and putting it into practice on a home lab I actually maintain, small applications I actually use, and operational problems for a real business. Cloud, networking, Linux, automation and the code that ties them together.
Currently Linux administration
Open to internships and entry-level cloud/IT roles
01 — About
I'm working toward a Bachelor of Science in Cloud & Network Engineering at Western Governors University, with an AWS specialization. Most of what I know outside of coursework came from picking a problem I actually had and building something to solve it.
That pattern repeats: a home lab that started as one spare machine and turned into a small set of self-hosted services I depend on daily; a bar that needed a better handle on its inventory, so I built tooling for it; personal apps for budgeting and habits because the off-the-shelf versions never fit. Each one taught me more than a tutorial would have.
My interests sit where infrastructure meets software — cloud platforms, networking, Linux and Windows administration, automation, and writing the code that ties them together. I'm comfortable with programming fundamentals in Java, C++ and C#, and I use those same fundamentals in the Python and web work my own projects need.
I'm early in this career and I'd rather be accurate about that than oversell it. What I can point to is a habit of shipping working systems, running them, and fixing them when they break.
02 — Skills
Grouped by area rather than dumped in one list. These are things I've worked with — the depth varies, and I'd rather say that plainly than imply mastery across the board.
The focus of my degree and where most of my study time goes.
Coursework plus a home network I actually have to keep running.
Day-to-day environments for both study and personal projects.
Languages from coursework, and what I reach for when building.
Front-end work for my own projects and internal tools.
What the work runs through.
03 — Projects
Personal and technical projects. Most of these run on hardware I maintain, which means I also get to deal with them when they break.
Home lab architecture
The home lab is where most of my Linux, networking and service-management practice happens. Everything reaches it over an encrypted private network rather than an open port, and storage is split by purpose so a rebuild never puts the data at risk.
A personal Ubuntu server running the services I use every day. It handles storage split across separate drives for the OS, applications, media and backups, network-wide DNS filtering, private remote access, and the small web apps I write for myself. It is where I practice the Linux administration, networking and service management side of my coursework on something I actually depend on.
Needs detail Confirm this description and the architecture diagram above are accurate before sharing the site.
A self-hosted web app for tracking what I spend and seeing it summarised by month. Built to fit how I actually budget rather than how a commercial app assumes I do.
Needs detail Add the repo link if you want this one public, plus a screenshot.
A tracker for habits, recurring chores and skills I am working on, backed by a small relational schema so history is queryable rather than just a running list.
Needs detail Confirm the current status and add a repo link or screenshot.
Tracks workouts and nutrition, and turns planned meals into a grocery list. The most data-model-heavy of my personal apps — it is where I have done the most work on schema design.
Needs detail Confirm the current status and add a repo link or screenshot.
A static portfolio built with Astro. All of the content lives in typed data files separate from the components, so updating a project or a skill is a one-file edit rather than a rewrite. Deployed automatically from the main branch.
Needs detail Add the repo URL for this site once you are happy publishing it.
04 — Now
A running snapshot of what has my attention right now, rather than a finished list. It changes often.
Working through the AWS specialization in my degree — core services, how they fit together, and building small things on them rather than only reading about them.
Routing, switching, DNS and firewalls, reinforced by keeping my own network segmented and working.
Running Ubuntu Server day to day — service management, permissions, storage layout and backups.
Adding to the set of small Flask apps running on my home lab, and improving how they are deployed and backed up.
Replacing the manual steps in my own workflows with scripts — deployments, backups, and routine maintenance.
Using AI coding tools as part of how I build, and learning where they help and where they need to be checked.
Front-end work for my own tools, and static site tooling — this site included.
Last updated: September 2026
05 — Applied Work
Work where the constraints came from a business rather than from me. Different problem shape than a personal project — the requirements arrive from how people actually work, and the system has to survive a busy shift.
Practical AI and admin help for small businesses and solo professionals: setting AI tools up around the work a business already does, closing the gaps where information gets retyped between systems, ongoing back-office support, and small custom tools where nothing off the shelf fits. It grew out of the same observation as most of the work below — the hard part is rarely the technology, it is fitting a system to how people already work.
Independent technology and process work
Worked on technology and process projects for a bar, focused on inventory and the day-to-day operational workflows around it. The problems here were less about interesting technology and more about fitting a system to how people actually work during a shift — which turned out to be the harder part.
Needs detail Add the technologies you used once you are happy naming them publicly, and check with the business before publishing anything more specific about their operations.
06 — Journey
Not a long résumé — a record of how the skills actually accumulated, and what I'm aiming at next.
Early on
First real exposure to writing code — Java, C++ and C#, and the fundamentals underneath them: variables, control flow, functions, and how a program is actually structured.
Along the way
A spare machine turned into a server. Learning Linux by having to keep something running rather than by following along with a lesson.
Recently
Applied the same skills to a real operation — inventory and workflow problems at The Library on Carson, where the constraints came from how a business actually runs.
In progress
Currently pursuing the degree with an AWS specialization, covering cloud platforms, networking, systems and security.
Ongoing
A growing set of self-hosted services and small applications, maintained rather than abandoned — which is where most of the actual learning happens.
Next
Working toward a role where I can do this at scale: cloud infrastructure, networking and the automation that holds it together.
07 — Contact
Happy to talk about cloud and networking work, a project, or a role. The quickest way to reach me is below.