-
Notifications
You must be signed in to change notification settings - Fork 170
[HW] <Ash Hopkins> #402
Comments
I wish I would have completed this workshop sooner 😅 From the point of view of a designer who doesn't code, and who is designing for developers, going through the end-to-end process and getting a better understanding of the steps to take, how CQL is written, etc. has given me a deeper perspective. Will be doing more of these! |
That's great to hear and glad you found the material useful. |
And I just realized who you are via your email above, lol. 👋 |
ash.hopkinsThank you for your efforts, it is a pleasure for us to give you your well deserved BADGE at the following link You can now brag about it on Twitter, Facebook or LinkedIn. It helps the workshops to be more visible and encourages us Advocates coming back every week with new content. Please make sure to use the hashtag #DatastaxDevWorkshops. 💚 🙏🏻 🙏🏽 🙏🏿 |
Haha, yes. The XD team is supposed to complete this as one of our OKRs this
quarter. Not sure who else has completed it yet, but you may see some more
DS emails come through this week 😂
On Wed, Oct 27, 2021 at 7:01 AM David Jones-Gilardi < ***@***.***> wrote:
And I just realized who you are via your email above, lol. 👋
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#402 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AVLGV67N2SFNJHUIAYUESQLUI7ZZPANCNFSM5GY274SA>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
--
Ashley Hopkins Boulder, CO
|
Name: ash.hopkins
Email: [email protected]
Linkedin Profile: https://www.linkedin.com/in/ashleyjhopkins/
Attach the homework screenshots below for both step II and step III:
The text was updated successfully, but these errors were encountered: