Education & Engineering Journey

Learning to build systems.

My education is not just about collecting certificates. It is the foundation behind the software, infrastructure, security research and products I build. University gives me the theory; projects force me to make that theory work in the real world.

Software Engineering Degree Program
2024 → 2028 Academic Journey
Build → Break → Learn Learning Loop

Bachelor of Science in Software Engineering

Kirinyaga University
Started 2024 Expected 2028 Software Engineering Security Focus

The program provides a structured foundation in software engineering, algorithms, databases, system development, programming and computing principles. I complement the academic curriculum with independent development, real products, experimentation and cybersecurity work.

CURRENT APPROACH
Theory → Implementation
Learn the concept, build something with it, discover what the textbooks didn't mention.

The journey so far.

Education and practical engineering have developed side by side. Each stage has added another layer to how I understand software systems.

2024

Started Software Engineering

Began the university journey with a focus on understanding the foundations of software development, programming, computer systems and engineering methodology.

2025

From Coursework to Building

Started connecting academic concepts with practical development — databases, APIs, web applications, authentication, deployment and full project workflows.

2026

Engineering Real Products

Expanded into SaaS development, analytics, cybersecurity, cloud infrastructure and production-oriented projects such as Mantemetrics, ManteAds, Riscaly and Cutlnk.

2027 → 2028

Deeper Engineering & Specialisation

Continue strengthening software architecture, cybersecurity, distributed systems, cloud engineering, product development and the ability to turn ideas into reliable software.

More than just code.

Software engineering is a wide field. These are some of the areas that shape how I approach development and problem solving.

Programming

Programming concepts, algorithms, data structures, abstraction, modularity and writing maintainable code.

Software Architecture

Understanding how components interact, how systems are structured and how software can evolve without becoming impossible to maintain.

Databases

Relational databases, SQL, schema design, relationships, indexing, queries and application data modelling.

Cybersecurity

Web security, HTTP, DNS, SSL/TLS, security headers, vulnerabilities, attack surfaces and defensive thinking.

Cloud & Infrastructure

Deployment, hosting, DNS, cloud services, Git workflows, server configuration and understanding production systems.

APIs & Backend Systems

REST APIs, authentication, server-side logic, request handling, integrations and communication between systems.

Version Control

Git, GitHub, branching, merging, conflict resolution, project history and collaborative software workflows.

Web Engineering

Frontend interfaces, responsive layouts, browser behaviour, JavaScript, backend integration and production websites.

Problem Solving

Breaking large problems into smaller systems, debugging, researching, testing assumptions and iterating toward a working solution.

The real laboratory.

Some of the most valuable lessons come from trying to build something that actually has to work.

Building my own projects means dealing with the things that assignments often simplify: deployment failures, database connections, authentication bugs, CORS, DNS, hosting, security, performance, product decisions and users.

~/mante/learning-loop
$ learn software-concept
→ understand the theory

$ build practical-system
→ turn theory into code

$ deploy production
→ discover reality

$ debug everything
→ find out why it broke

$ improve architecture
→ make the next version better

$ repeat ∞

How I turn knowledge into skill.

Learn

Understand the principles before blindly copying implementations.

Build

Apply the concept to an actual system where requirements and edge cases exist.

Break

Debug failures, question assumptions and understand what actually went wrong.

Iterate

Improve the implementation instead of treating the first working version as the final version.

The degree is the
beginning, not the finish line.

Software changes too quickly for learning to stop at graduation. The goal is to keep building, researching, experimenting and becoming a better engineer long after the classroom ends.