What I Studied and What I Took Away

Eight completed micro-credentials. One Applied Computing degree.

One of the advantages of SIT's Applied Computing CSM pathway was the opportunity to explore different areas of computing through individual micro-credentials.

Each one was a qualification in its own right, but the greater value came from understanding how the disciplines connected.

Coming from a Computer Engineering background and working in technology product management, I was particularly interested in how these subjects applied outside an academic setting.

The headings below describe areas of study, not official micro-credential titles. I am checking the exact names against my SIT academic record.

The foundations behind the technology.

This area of computing brought me back to fundamental ideas such as logic, computational thinking, programming and the structures underlying digital systems.

Having studied Computer Engineering at polytechnic, some of these concepts were familiar.

But revisiting the fundamentals after gaining professional experience gave me a different perspective.

I had a better appreciation of why foundational knowledge matters, even when your day-to-day work involves higher-level platforms, abstractions and services.

It reinforced the importance of being able to reason through a problem rather than simply relying on tools and frameworks.

My takeaway: Technology changes, but the fundamentals behind it remain relevant.

Understanding data is not enough. You also need to understand its consequences.

This credential brought together analytical thinking, computing practices and the ethical responsibilities associated with technology.

I explored how data can be processed, analysed and interpreted, as well as the limitations and responsibilities involved in using it.

What stood out to me was that a technically correct result is not automatically a useful or responsible one.

Data can be incomplete, biased, poorly contextualised or interpreted in ways that lead to misleading conclusions.

In product management, these considerations are particularly important.

Metrics influence decisions, but the quality of those decisions depends on understanding what the metrics actually represent.

My takeaway: Good analysis requires technical competence, critical thinking and a healthy level of scepticism.

Designing systems that work beyond a local development environment.

Cloud computing is often presented as a collection of services and technologies.

What interested me more was the architectural thinking behind those services.

I developed a deeper appreciation for scalability, reliability, security boundaries and the trade-offs involved in different cloud designs.

A system might work perfectly during development but behave very differently when exposed to real users, unexpected workloads or security threats.

This was especially relevant to my experience in telecommunications, where availability and operational reliability are major considerations.

Cloud architecture also strengthened my understanding of how infrastructure choices influence cost, performance and long-term maintainability.

My takeaway: Good architecture is about making deliberate trade-offs, not simply choosing the most advanced technology.

Learning how systems identify patterns — and why they sometimes get things wrong.

Machine learning introduced a different way of approaching computational problems.

Instead of explicitly defining every rule, I explored approaches where models learn patterns from data.

I developed a greater appreciation for data preparation, model selection, training, evaluation and the risks of drawing conclusions from unreliable results.

One of the most important lessons was that model performance cannot be judged using a single impressive-looking metric.

You need to understand the dataset, the assumptions, the evaluation method and the types of errors the model makes.

My interest was not limited to building models.

I wanted to understand how machine learning could be applied responsibly to actual business and operational problems.

My takeaway: A machine learning model is only useful when its outputs can be understood, evaluated and applied to the right problem.

Understanding patterns across time.

Time-series forecasting gave me an opportunity to think about problems where historical behaviour can help inform future expectations.

These problems are particularly interesting because real-world systems rarely behave in perfectly predictable ways.

Changes in demand, unexpected events, seasonality and shifts in underlying behaviour can all influence a forecast.

The subject strengthened my appreciation for how forecasting depends on data quality, modelling assumptions and appropriate evaluation.

From a technology and product perspective, I could see the relevance to operational planning, capacity management and understanding trends.

I also learned that forecasts should support judgement rather than replace it.

My takeaway: Predicting the future is less about finding a perfect model and more about understanding uncertainty.

Going beyond using AI tools to understanding how they work.

Generative AI became increasingly prominent while I was studying, and I wanted to understand the technology beneath the applications people interact with.

This credential covered natural language processing, large language models and the concepts behind modern generative AI systems.

I explored areas such as text preprocessing, embeddings, transformer architectures, attention mechanisms, model evaluation and fine-tuning.

What interested me was the distinction between demonstrating an AI capability and turning it into something reliable enough to be useful.

A compelling demonstration is one thing.

Building a system that behaves consistently, manages errors and provides meaningful results is another.

The experience encouraged me to think critically about where AI genuinely adds value and where conventional software engineering may be more appropriate.

My takeaway: Understanding the capabilities and limitations of AI matters more than simply knowing how to use the latest model.

Building something is different from building something maintainable.

My Applied Computing studies also strengthened my understanding of software engineering and cybersecurity through academic work and projects.

I worked with concepts involving application development, security considerations, system architecture, deployment and the integration of multiple components.

This reinforced the importance of maintainability, testing, secure design and clear documentation.

One lesson I keep returning to is that technical complexity should never become an end in itself.

A solution should be as complex as necessary, but no more.

My takeaway: Good engineering is measured by how effectively a system solves a problem and how reliably it continues to do so.

This piece groups the subjects by learning themes. I am checking the official titles and module-specific details against my SIT academic record, so I have not presented these groupings as exact credential names.

---

Looking at each credential individually, it's easy to see a collection of different technical subjects.

Looking at them together, I see something more useful.

The foundations help me understand systems.

Software engineering helps me build them.

Cloud computing helps me deploy and operate them.

Cybersecurity helps me think about their risks.

Data analysis and machine learning help me understand information and patterns.

And artificial intelligence introduces new ways of interacting with and processing information.

But the most valuable part is learning when and why to use each approach.

I didn't pursue the degree simply to collect certificates.

I wanted to become better at understanding unfamiliar problems and identifying appropriate ways to solve them.

That's the perspective I hope to carry forward throughout my career.