Discover and read the best of Twitter Threads about #abap
Most recents (3)
1/ I'm on my way to self-employment and since I don't have any projects yet, I'm dedicating my time to open source projects on GitHub.
I am primarily working in the SAP ecosystem.
github.com/marianfoo
Here are all the projects I have been working on lately:
I am primarily working in the SAP ecosystem.
github.com/marianfoo
Here are all the projects I have been working on lately:
2/ @exercism_io is an open source and free code learning platform.
@LarsHvam has created a tremendous solution to compile ABAP to JS.
This made it possible to add #ABAP to #Exercism.
I have added two new exercises here that can be solved by you:
exercism.org/tracks/abap
@LarsHvam has created a tremendous solution to compile ABAP to JS.
This made it possible to add #ABAP to #Exercism.
I have added two new exercises here that can be solved by you:
exercism.org/tracks/abap
3/ "Best of UI5" is the new entry page that shows the best community projects in the UI5 Ecosystem.
As a little pet project of my own, together with @pmuessig . I improve it all the time.
Currently new packages have been added:
bestofui5.org/#/packages?sor…
github.com/ui5-community/…
As a little pet project of my own, together with @pmuessig . I improve it all the time.
Currently new packages have been added:
bestofui5.org/#/packages?sor…
github.com/ui5-community/…
You can run #ABAP applications in your browser 🤯
No #SAP system required ❗
Any questions, @SAP @SAPdevs @SAPcommunity ❓
No #SAP system required ❗
Any questions, @SAP @SAPdevs @SAPcommunity ❓
Yeah, I thought so... You have your doubts 🤔 💭
We know. We surely must have a big server and an SAP Kernel 🖥️
"I'm really really good at #debugging" a #sap #abap developer friend once said to me. I replied "oh thats awful". Why? Because it means he spent a lot of time finding bugs in code that was probably not covered by tests. But how do you debug efficiently? (1)
Many people use breaks points, watchpoints, breakpoints on messages, exceptions, post mortems, job debugging, etc and are successful that way. But at some point you have to "look at code". Over the years I've seen a few repeating patterns: (2)
"Just go for it". Is the error reproducible at all? Before debugging, it is better to check that, otherwise you lose a lot of time with code in which the error is not / only difficult to see by debugging. Because everything works as it should durching your debugging session. (3)
