Technical Articles
Roadmap to become SAP BTP Developer – “Developer is the KING”
Hello, Developers/Architects/Project Managers
My name is Partha,
I’m an “Architect-Developer“.
Let me share some of my experiences and realizations.
So far… I have been involved in multiple S/4 HANA implementations.
One thing, I realized vividly and truly believe is that developers are the king in Software/Technology Industry!
Let’s analyze the power of developers.
For that purpose, I would go a little deeper and categorize the developer tag.
Again per me, there are three kinds of developers
1. Development-Developer
2. Pro-Developer
3. Architect-Developer (like me 😎)
I will conclude the blog with the definitions of the 3 developer tag.
Let’s come back to the topic now…
As I said, “Developers are the King” here! I mean it. 🤴
For a successful S/4 HANA Implementation in the new era (keep the core clean), we definitely need the Project managers, Digital Transform strategists (big names.. haha)…
But don’t forget the developers, repeating myself ”Developers are the King”.
So, what are the skill sets we need, to praise a developer, as the “KING” !?
Or how you can become the “KING” as a developer !?
A must-have skill sets for any successful S/4 HANA Implementation project with the “keep the core clean” strategy in BTP (Business Technology Platform),
here you go…
🤴👩💻👨💻
how to become the “KING“ – Roadmap to become SAP BTP Developer:
Please enlarge the image to get a complete view or simply download it from the given link below.
Roadmap to become SAP BTP Developer
Download PDF : Click here
If you are afraid of seeing the above pic with a whole lot of new things or having a kind of FOMO, please don’t worry! Maybe you don’t need to know all the skills at the initial go, to be part of any S/4 implementation project with BTP
Keep reading…
Now as I promised earlier, let’s analyze a bit more the developer’s category. So that you can get some relief.
1. Development-Developer:
The majority of the developer pool falls under this category. And this is also one of the most important developer personas we need for any successful implementation. This category of developers has hands-on experience in a particular area ( like frontend or backend or database or integration or.. etc)
2. Pro-Developer:
The ratio is less compared to the point 1 developers. But this pool holds specialized skills to solve the problems faster and with bug-free delivery, at the same time, generally, they are lazy developers! 😛
Sometimes they are known as full stack cloud developers ( can code for multiple areas) and can help development-developers in the overall delivery of software.
3. Architect-Developers:
As a project manager, you might need a very less proportion of this kind of developer persona, but you definitely need it, I have seen projects were failing badly just because there is no allocation for this position at all. Or sometimes, there is no right kind of allocation for this position.
Now, the question is who are those Architect-Developers?…
You can imagine someone who has profound knowledge of all the skill sets mentioned above (pdf) and is visionary enough to give futuristic/future-proof solutions.
In simple words, as a project manager, you should hire one or multiple Architect-Developer(s) who have the overall system understanding, business understanding, and definitely technology hands-on experience.
So far whatever I said, is completely based on my own experience. Please don’t get offended if somewhere the truth is coming harsh to you.
We can always discuss this topic further.
I will try to reply to the comment section here. You can also reach out to me on LinkedIn: /parthasap
Thanks for the great roadmap as PDF! That's an awesome illustration!
Thank you Stefan Graf for the feedback!
I think the mat.yaml can link to the micro services, since that was a configuration file to register the micro service component
correct my if wrong 🙂
BTW, good roadmap
It is! thanks Minjie Lao for reading it out.
But I feel it's more than the MS linkages.
And as it's holds all the deployment information (descriptor) for any application, which tells the CF's cloud controller about the deploying application, like what is the application ID and what is the version of it and then its goes to Diego brain, Diego cell, garden containers and connects to other microservices and databases using service broker.
It also holds the buildpack informations (like nodejs, java, python etc), which runtime to be used to compile and serve to end user. which is very important.
And if I cut short it, it's (mta.yaml) basically SAP's way of handling the manifest.yml file, rest of the world call this manifest file as deployment descriptor, hence I do 😎
If you want to understand the CF architecture which I tried to explain in few sentence before, just check it out from below:
https://www.youtube.com/watch?v=tNDguipfUWs
appreciate your read! 🤗
I would suggest that the Architect is "KING", with the opportunity for a Developer to become a "Rock Star".
I think engaging an Enterprise Architect (as opposed to an Architect-Developer), who has depth and breadth of expertise with both business processes and SAP BTP, who can lead developers and act as a bridge between developers and business users is critical to the success of a project. Left in the hands of developers alone, you run the risk of producing a technical solution rather than a business solution.
Hi Mustafa Bensan,
Appreciate your reading, and comment!
And thank you for disagreeably agreeing with my points 😀
Anyways, "Developers" should feel like a "KING" !
Be it "Architect-Developer" or "Pro-Developer" or in your term "EA-Developer"
Ex: You can think of any big company nowadays, started by the developers only (be it Google, FB, apple or even SAP)
Now the question is how do you see an EA? 🤔
I already described "Architect-Developer" definition in my way in the blog.
Thank you!
I really like your mind-map, good job!
Thank you for the nice feedback!
Is it only me who misses ABAP/RAP from your diagram?
Yes, After some promising releases of the ABAP for Cloud platform (steampunk), it truly deserves the space in the roadmap, I will update the detailed version of the roadmap very soon!
How can I forget that I'm also a hardcore ABAPer, I still love ABAP 🙂
Thank you for your feedback!
Thank you for nice roadmap!!
with steampunk & embedded steampunk out in latest release it seems steampunk /ABAP/RAP deserves a space in roadmap.
May be in next blog/roadmap.
I fully agree
Yes, After some promising releases of the ABAP for Cloud platform (steampunk), it truly deserves the space in the roadmap, I will update the detailed version of the roadmap very soon!
How can I forget that I'm also a hardcore ABAPer! and I still love ABAP 🙂
Thank you for your feedback!
Nice roadmap,
but i am missing Application Logging service, Kibana and then the topic of multi tenancy regarding real SaaS applications.
Best Regards,
Lukas
You are right!
due to limited space, I did not put all the backing microservices. There are lots of them, I guess almost 100
I should have put .. [dot dot] in the backing services section.
My intention was to put the bare minimum, which is absolutely needed to start and execute a project.
Thanks for reading!
Personally love the infographic. Looking forward to an expanded version covering Kyma 🙂
Hi Kevin, thanks for the lovely feedback!
Definitely, there will be a detailed version of this roadmap. There will be ABAP (steampunk), Kyma, SaaS provisioning, data Lake, Hyperscaler options, AI Core .. many things need to come up in the next version of the roadmap.
I will constantly upgrade it!
Perfect.. SAP BTP Developer is King...
Excellent document, Partha - this makes you the "King of communications", because nobody else has explained BTP as well as you!
Mike McNally
Thanks Partha for sharing such detailed roadmap and the definition of Architect- Developer and its need . Loved the quote “Developer is the KING”, makes developer like me so proud 🙂 !
Thanks
Shweta