The Software Industry & Its Roles

SAP Implementation Consulting & ERP - Startupistan Germany · Block I · study notes for revision.

---

Two things in one chapter: the mindset I need to work in tech, and the map of who does what. The map matters because an SAP consultant sits at its crossroads - I end up talking to almost everyone on it.

The mindset for working in tech

I’m not just learning a tool, I’m stepping into a whole industry. That reframe helps: one hard afternoon is one room in a very large building, not the whole building.

Three habits that actually matter

• Stay curious, expect to get it wrong. Things breaking, cryptic messages, “worked yesterday, not today” - that’s the normal texture of the work, not a verdict on me.
• Comfort with not-knowing. Nobody holds the field in their head.
• Everyone looks things up. Professionals search all day. The real skill is finding the answer fast, not memorising it. That takes the pressure off.

Learning it the self-led way

This is a blended course: a few live sessions plus a lot of self-paced hours. The live time is where I get unstuck and get feedback - but most of the progress happens alone, so a routine is what makes it real.

What keeps me going

Motivation is a feeling - real, useful, unreliable. The pair that replaces it:

• Discipline = showing up to the study block because it’s on the calendar, not because I feel like it.
• Dedication = the specific reason I keep the discipline (the why).

They prop each other up. And study actively - build it, explain it out loud, recall from memory before checking. Passive re-reading feels like learning but isn’t; the effort is the learning.

Getting unstuck - the #1 beginner skill

The single most valuable early skill isn’t knowing answers, it’s knowing what to do the moment something won’t work. It’s a named, reusable routine - same four moves, in order, every time.

1. Restart it. Turn it off and on, or close and reopen. Clears a confused state and fixes a genuinely large share of everyday glitches - for free. Try this first.

2. Read the message. Don’t click the error away in a panic. I don’t need every word - I hunt for the plain-language clue: a file name, not found, no internet connection, permission denied. Partial understanding usually points straight at the cause.

3. Search well. Turn the problem into a specific search: the program’s name + the exact words of the message. If the first try flops, change the words and search again.

4. Ask a person. When restart / read / search aren’t enough, asking is the smart move, not a failure - as long as I give enough to work with (template below).

Ask a question that gets answered fast

Fill these in before sending. Four lines and a helper can usually spot it immediately:

1. What I was trying to do
2. What I expected to happen
3. What actually happened (+ the exact error, quoted word-for-word)
4. What I’ve already tried

Same shape scales into the job: a good bug report to my team is exactly these four lines. Post in a shared channel over a private DM - someone else with the same question learns too.

Traps to un-learn

“Restarting is a silly non-solution” - no, it genuinely works. · “Asking = I’m behind” - no, the people who ask early stay on track. · “A vague question is fine, they’ll know what I mean” - a helper can’t read my screen or mind; specific gets a useful answer far faster.

How a product moves through a company

Easiest way to make sense of the roles: don’t list them, follow one product from idea to live service. Every role owns one stage of this relay - no single person does it all.

Decidewhat & why

→

DesignUX · UI

→

Buildsoftware · data · AI

→

Shiptest · release

→

Run & keep safeops · security · support

→

Users

A product is a relay passed hand to hand. One tap in a finished app - say booking a clinic slot - touches half a dozen fields: design shaped the screen, developers built the action, data people decided how it’s stored, security encrypted it, infra kept it fast, a tester made sure the slot couldn’t be double-booked, support helps if the user gets stuck.

Note

Keep three words apart: a field is a broad area (security, design); a role is a job inside it (security analyst, UX designer); a title is whatever a company prints on the badge - and titles vary wildly. Learn the role behind the title.

The map of tech roles

Grouped into families, one line each. The goal is recognition, not memorising every box - roles blur and people wear several hats in real life.

Building - software, data, AI

Role	What they do
Front-end developer	Builds the parts you see and touch - screens, buttons (the “dining room”)
Back-end developer	Builds the hidden machinery - logic, storing data, making things happen (the “kitchen”)
Full-stack developer	Works across both front and back
Software engineer	≈ developer, with stress on discipline & maintainable code, not just code that works today
Data analyst / engineer / scientist	Analyst answers questions from data · engineer builds the pipelines · scientist finds patterns & predictions
AI / ML	Builds systems that learn patterns from data rather than following fixed rules - leans heavily on data roles

Note

Under almost all of it sit databases - the organised stores where information lives. Nearly every system depends on one. This matters most in the enterprise/SAP world below.

Design & experience - no coding required

Role	What they do
UX (User Experience)	How the product works - is it clear, findable, does the flow make sense? Good UX is invisible; you only notice bad UX
UI (User Interface)	How it looks - colours, spacing, buttons, fonts, visual polish
Product designer	Where UX + UI meet: something both usable and attractive, then handed to developers to build

Run & keep safe - ops, security, infrastructure

Role	What they do
Sysadmin	Looks after servers & systems - configured, updated, working
Networking	Keeps everything connected - data flow between machines, offices, the internet
Cloud / DevOps / platform	Runs systems on rented computing; builds pipelines to release software reliably
IT support / help desk	Front line when a laptop won’t cooperate
Cybersecurity	Protects systems & data - defensive (build protections, watch), offensive (break in with permission to find holes first), governance (rules & compliance). Touches every other field

Tip

Ops & security are judged by things not happening. Building = power, lifts, plumbing. Security = locks, guards, alarms. You only notice either when one fails.

Business, product & quality - where career-changers often fit

Role	What they do
Product manager (PM)	Decides what to build and why, and in what order - from user needs + business goals
Business analyst (BA)	Translates business problems into requirements the tech team can act on - big in the enterprise world
Project / program manager	Keeps the work organised, coordinated, on schedule
Tech marketing	Brings the product to its audience - digital marketing, SEO, growth, content
QA / testing	Catches problems before users do; deliberately tries to break things
Technical writer	Makes complex things understandable - guides, manuals, help pages

Two pairs I keep confusing

PM vs project manager: product manager decides what & why; project manager keeps the building organised & on time. · UX vs UI: how it works vs how it looks - partners, not the same, and a product needs both.

Where enterprise software & the SAP path fit

Enterprise software runs the operations of a large organisation (not one personal user) - its finance, staff records, supply chain, all at once and at scale. Large, stable, well-paid corner of the industry.

ERP in plain words

ERP = Enterprise Resource Planning. One big connected system a whole company runs on - finance, logistics, HR, and procurement (buying) sharing the same information instead of each keeping separate records. Like one shared board on the kitchen wall everyone reads from and writes to, instead of everyone keeping their own private list that never agrees.

Every ERP sits on a database - every record, transaction and update lives there. An ERP is only as good as the database beneath it, which is why data is handled so carefully in this world.

SAP

One of the world’s leading makers of enterprise software; its systems run a large share of major companies. Learning SAP = learning the systems a great deal of the corporate world depends on - which is why the skill is in steady demand.

ABAP

SAP’s own programming language, used to build and customise behaviour inside SAP systems. Where general programming might be taught with JavaScript, the SAP world has ABAP for its own systems.

Implementation consultant

The role this pathway leads toward - sits right at the crossroads, bridging what the business needs and what the system can do.

The key point: an SAP role is not an isolated corner. Implementing an ERP touches nearly the whole map at once.

Business analysts - what the company needsData / DB - the database beneathSecurity - sensitive finance & personal dataDevelopers & testers - customise & checkProject managers - keep it on track

Tip

So the whole role-map is really a map of my future colleagues. And a handy instinct falls out of it: I can often guess who’s responsible without being told. App confusing → design (UX). Leaks private data → security. Crashes under load → infrastructure. Feature does the wrong thing → the developer who built it or the tester who missed it.

Revision summary

Must-know	One-line recall
Tech mindset	Curiosity + comfort with not-knowing; everyone looks things up - finding beats memorising
Discipline vs motivation	Motivation is an unreliable feeling; discipline shows up anyway, dedication is the why
Active study	Build / explain / recall from memory - passive re-reading feels like learning but isn’t
Getting unstuck	Restart → Read → Search → Ask, in that order
Ask well	Trying to do / expected / actually happened (+ exact error) / already tried
Product journey	Decide → design → build → ship → run - a relay; no one builds it alone
Field vs role vs title	Broad area vs the job vs the company’s badge - learn the role
Building family	Front/back/full-stack devs; software engineers; data analyst/engineer/scientist; AI/ML
Design family	UX = how it works · UI = how it looks · product design = both, handed to devs
Run & safe family	Sysadmin, networking, cloud/DevOps, support; security = defensive/offensive/governance
Business & quality	PM (what & why), BA (needs→requirements), project mgr (on time), QA, tech writer
ERP	One connected system uniting finance, logistics, HR, procurement - on a database
SAP & ABAP	SAP = leading enterprise-software maker; ABAP = its own language
SAP consultant’s place	Crossroads role bridging business ↔ system; touches nearly every other field