Daily · SAP development & configuration

What SAP work becomes next.

A plain read on where SAP technology is going, which business problems it actually solves, and how the people who keep these systems running can regear for what's coming.

SAPCodeMonkey mascot working at a laptop

What this covers

Three questions, asked every day

Technology on its own is trivia. It matters when it solves something real — and when you can see what it does to your own job.

01 · Technology

What's actually changing

The platform shifts, explained by someone who works in them rather than sells them. What's real, what's still a slide, and what breaks if you ignore it.

  • Clean Core & ABAP Cloud
  • S/4HANA migration reality
  • RAP, CDS, BTP extensions
  • Joule and AI tooling
02 · Business

What problem it solves

Every capability is sold as transformation. Few are. The useful question is which business driver it serves, what it costs, and whether standard already does it.

  • Driver vs vendor pitch
  • Where automation pays back
  • Cost of custom vs standard
  • Building the business case
03 · Your career

How to regear for it

If you support these systems today, the job is changing under you. This is the practical version: which skills hold value, which ones fade, and what to learn first.

  • What support roles become
  • Skills that survive automation
  • Moving from doing to judging
  • Learning paths that pay off

Which seat are you in?

Pick one and the changes below rewrite themselves for your role.

What's changing

Six shifts already underway

None of these are predictions. They're happening now — the open question is what each one does to your day.

Writing the code Judging the output

Rules-based workflow AI agents that decide

Knowing the transactions Knowing the business Explainer →

Upgrades every few years Continuous change

Delivering the request Owning the outcome

Go deeper

Two things worth understanding properly

Interactive explainers rather than another wall of text. Both take about five minutes and answer questions you'll otherwise get asked in a meeting.

The channel

New every day

Short, specific, and built from real system work — not vendor slides. Watch, argue with me in the comments, tell me what I got wrong.

Collaborate

This works better as a conversation

Most of what's useful here came from someone describing a problem I hadn't hit yet. Bring yours.

?

Ask a question

Stuck on a dump, a config gap, or a migration decision? Send it over. Good questions become videos, and I'll credit you unless you'd rather stay anonymous.

Send a question →

Share what you're seeing

Field notes from real projects are worth more than any roadmap deck. Tell me what your Clean Core move actually cost, or what your team decided about AI tooling.

Share a story →

Suggest a topic

If something here is missing, or a shift above doesn't match what you're living, say so. The role lens exists because someone pushed back on a one-size answer.

Suggest a topic →

Who's writing this

An independent SAP consultant working across both the technical and functional sides — R/3 through S/4HANA, development and configuration. The background is only here so you know the takes come from inside real systems.

25+ years in SAP · available for project work when it's a fit

Work together

Get the next one

A new video every day on where SAP development and configuration are heading — and what it means for your job.

Subscribe