SAP Developer Challenge - CAP Knowledge
Welcome to the Developer Challenge for this month of June 2026. You can guess from the "CAP Knowledge" title of the challenge that it's about CAP, and specifically knowledge of CAP. What does that mean, and perhaps more interestingly, why?
(Alternatively, jump straight to the questions or the analysis.)
Background
Both questions can be answered together, with one phrase: Cognitive Discipline.
Today's AI facilities in the area of development are as wonderful as they are powerful. There's no denying their ability to help us level up with regards to building and developing, not least in the SAP world.
While we continue to build, today's era and AI context means it's actually more important than ever to retain ... no - scratch that ... to double down on our understanding, our knowledge of the tools, libraries, architectures, frameworks and best practices that we and our agentic colleagues are using.
There's a significant possibility that we will start to lose the ability to reason about what's being built, to understand, validate and review the architecture approaches, the library design and use, and the code - whether that's declarative or procedural or something entirely different.
That in turn leads to largely as yet unknown challenges down the line, not only challenges for the maintainability of what's been built, but our ability to retain enough knowledge to continue to steer its direction and ensure the best possible outcomes.
Ironically, the best approach to mitigating this risk, is to turn to what (in these days of search-first and AI summaries of specific issues or solutions) is becoming a little out of fashion ... and that is reading.
Reading + thinking = comprehension.
And that is the simple key to practising and retaining what some folks today are referring to as "cognitive discipline", the active and conscious effort to remain relevant, retain knowledge of the tech we're steeped within, and grow our ability to continually vet and monitor the design and implementation of the apps and services that are being created.
The challenge
This Developer Challenge is in that context, in that it is designed to:
- help us attain and then retain our understanding of CAP
- celebrate the accomplished and exemplary documentation unofficially and affectionately known as "Capire"
And we all know what "Capire" means, right? :=)
So this month's challenge is a series of questions, each of which has a simple and concise answer. The questions are deliberately based on content in Capire, and each question's intro will hint at where in the content you should explore to find the answer.
And that's the key to this challenge, and (hopefully also) the fun and the beauty. The questions have been designed to cause you to dive into Capire, in search of the answers. But don't rush! When you get there, take your time, spend some extra minutes exploring and getting acquainted with what's there, how the information is structured and presented, what the navigation feels like, and perhaps even try out the realtime search (hint: use Ctrl-K or Cmd-K).
It's about the journey.
Taking part
We're using the approach we first introduced back in 2023 for the August challenge on APIs. So the idea is that each answer will be a single word, or technical term, usually without spaces. Note also that the answer values are case sensitive, so ensure you get that right too!
And to submit your answer, you should use the same mechanism as we used for that Aug 2023 challenge, namely the "answer obfuscator", or "value hasher", described in the Task 0 post of that challenge back then: SAP Developer Challenge - APIs - Task 0 - Learn to share your task results.
Before embarking on this challenge, please head over there to that Task 0 post to make sure you "understand the assignment", which is basically for each question:
- read the question details, picking up hints on where to look in Capire
- determine your answer
- use the hashing mechanism to hash your answer
- submit the resulting hash (and nothing else!) in a reply to the individual question thread
This is simply so that we can all have a go at answering the questions, and submitting our answers, without spoiling it (revealing the answer) for everyone else. And, if I can conjure up the right incantations, I can automate the checking of the answers too 🙂
The questions
We'll post a new thread, with a new question, every Monday, Tuesday, Wednesday, Thursday and Friday in each of the full weeks of this month (June), meaning there will be 20 questions in total*. So be sure to keep an eye on the new posts here. To help you find them, we'll also add a link to each new question post to this post (below), as they're created.
Week 1
Week 2
Week 3
*We were planning 22, but decided on 20 to keep a nice round number and align to the full weeks.
Bluesky
