SASdeveloper
@SASdeveloper
Enabling developers worldwide to make the most of SAS software
Potrebbero piacerti
A5: Knowing where to concentrate effort. So much diverity (languages, organizations) Knowing whom to support is a #SASDX challenge #saschat
Lots of great insights - thanks everyone! Follow us and help us make a great #DeveloperExperience for @SASsoftware users! #saschat #SASDX
SASDeveloper is interested in building community 4 #SASDX starting with developer.sas.com Help us define it - send feedback. #saschat
I’m David Biesack, Principal API Architect at SAS (in R&D) and I help SAS build great APIs and developer experience #saschat #SASDX
Welcome to today’s #digitalevent w/ an expert panel discussing developer experience – use tags #saschat #SASDX. Introduce yourselves!
Hidden Insights: The growing influence of developer experience in high performance analytics blogs.sas.com/content/hidden… and join #SASDX Aug 3
blogs.sas.com
The growing influence of analytics developer experience in high performance analytics
Why is analytics developer experience a growing area of focus? Read the interview to Mark Frankish, one of SAS resident data scientists and developer coach.
"a team will become very familiar with the API and might fail to see how others cannot intuit how the API works" blog.hellosign.com/the-rise-of-de… #DX
Welcome, developers! Follow @SASdeveloper and watch developer.sas.com for how to tap into the power of SAS!
United States Tendenze
- 1. New York 1.03M posts
- 2. New York 1.03M posts
- 3. Virginia 509K posts
- 4. $TAPIR 1,610 posts
- 5. #DWTS 40.2K posts
- 6. Texas 213K posts
- 7. Prop 50 171K posts
- 8. Cuomo 400K posts
- 9. TURN THE VOLUME UP 14.5K posts
- 10. Bulls 35.4K posts
- 11. Harden 9,451 posts
- 12. Sixers 12.7K posts
- 13. Jay Jones 97.5K posts
- 14. #Election2025 15.8K posts
- 15. Embiid 6,069 posts
- 16. Maxey 7,874 posts
- 17. Eugene Debs 2,388 posts
- 18. #BlueWave 3,177 posts
- 19. WOKE IS BACK 32.5K posts
- 20. RIP NYC 16.6K posts
Potrebbero piacerti
Something went wrong.
Something went wrong.