We, as contributors, know how valuable it can be to share with others what we’ve learned and picked up throughout our career, instead of keeping it to ourselves – one of the main reasons behind this initiative.
“By the Community, For the Community…”
CUGC stands for Citrix User Group Community, which shares the same spirit and passion as we do within several local and global Citrix communities. Giving people from the community a podium for, and in front of, other community members and beyond. The main reason why this is the slogan of our latest community (book) project called: Byte-Sized. And YOU can be part of it too!
The idea behind Project Byte-Sized
The idea behind this project is simple. We’re looking for as many Cloud design principles, best or common practices, quotes, and architectural recommendations as possible. Forget about AWS, Azure, Google, IBM, Oracle, and all others, it’s the concept that matters, not the underlying vendor – 99 out of 100 times anyway. It can involve SaaS, IaaS, DaaS, PaaS, RaaS, or whatever aaS you can think of – private, public, or hybrid Cloud are all optional. General recommendations are more than welcome as well, it doesn’t have to involve technology per se.
We want to hear from you! Tell us what you think. What are your thoughts on Cloud in general, what works, what doesn’t? Where do you see ‘Cloud’ going within the next couple of years (or not)? Any lessons learned from the field, best or common practices, potential pitfalls, an approach nobody thought of before perhaps? You name it, we’ll list it.
Our book project in a (tiny) nutshell
Preferably, we’d like to keep your comments/quotes/bits of advice, etc. relatively small and direct. To be honest, we’re nerds, that’s why we named the book ‘Byte (yes, the binary digit) Sized Cloud Design Principles and Architectural Recommendations.’ Therefore, we ask you not to use more than 250 words. This makes sure all contributions will take less than one minute to read and will still give everyone enough room without going overboard, so to speak. However, if you’re able to fit your submission into a Tweet-sized message (approx. 50 words/280 characters) that’s totally fine as well. It’s all up to you.
No matter which Cloud vendor has your preference, if you are a Microsoft, Citrix, or VMware kind of guy or girl, a EUC Specialist, Architect, Hardware Hugger, Software Programmer, or a Helpdesk Technician, we don’t care! If you have any thoughts, tips, recommendations of some sort to share with us, please do, more is better in this case.
”It goes without saying that we need your help. We want to reach as many people as possible. Please help us spread the word, it would be greatly appreciated.”
What we want to ask you to do
All we want from you is/are the best advice, recommendation, design principle, tips and/or tricks, etc… you can give us, it’s that straightforward.
Here are some writing guidelines to help you get started:
- All submissions must be in English.
- As mentioned, a maximum of 250 words, give or take.
- No bad or foul language.
- Your quote has to make some sense in the context of the topic.
- Please, do not make it an advertisement, never mind the product or vendor behind it, we won’t publish it.
- If you work for a vendor, that’s no problem. Keep your quote, advice, design principle etc. as generic as possible. We know you are all very smart and creative people, show us!
- As mentioned, if you would like to add an image to your quote, that’s great, please do – PNG and JPEG’s only, please. We’ll take care of the conversion from there. No vendor or sponsor logos are allowed.
- And, you can contribute as much as recommendations/quotes and principles as you want!
Submit your contribution here
Or send your submission to email@example.com
Who we are
We are Christiaan Brinkhoff and Bas van Kaam. We share the same mindset as described in the first section. Further, we are both very active within various Microsoft, Citrix, and VMware orientated communities, as part of their programs.
“We, as contributors know how valuable it can be to share with others what we’ve learned and picked up throughout our career, instead of keeping it to ourselves – one of the main reasons behind this initiative.