Home

Welcome to the PSConfAsia2015Challenge wiki!

This challenge is open for attendees of the PowerShell Conference Asia 2015 only. Of course, anyone is welcome to Fork the project and do what they like to the code but Pull Requests will only be accepted by people who came to the event - because this is about Prizes!

In this Repo you will find a single function - Invoke-HulkSmash! We would like you to make some updates!

There is nothing specific we are looking for the function to be able to do, because this isn't about the function or the code itself. It's about GitHub use, elegant code and Pester Tests. So how does it work?

Why are you doing this?

As IT Pro's transition to DevOps futures there is a lot of Development practices that need to be learned to be successful. Some of the most important include Source Control, Testing, being able to collaborate with others on the same projects (no more huddling over your own scripts!) and just writing all around good code that you can share with others ... without them waiting for you in the parking lot to get you back for wasting their week! What better way to learn and practice these skills than in the safe environment of the PowerShell Community before you have to do it in the real world?

Why only PowerShell Conference Asia Attendees?

For this first challenge because there are prizes involved from the event, only those who attended are eligible to win. However, we are planning to open this out to everyone starting in December and highly encourage anyone, especially beginners, to get involved. We will have prizes along the way too!

How do I play?

1. Come up with an idea of what you want to add to the code - it really doesn't matter, it could be comment based help, another parameter, whatever you want.
2. Create a Fork of the Project.
3. Create a Pull Request - that's right! Before you have written any code, create a Pull Request and start a discussion thread on what you plan to add and how. This enables others to see what you're already planning to do so that when they Fork and start editing they can also make sure that they aren't going to create Merge Conflicts (when people add conflicting stuff to the code) and that they aren't overlapping or being overlapped.
4. Once we have discussed, add your code to the project - here is where you use the Elegant Code practices and can add some Pester Tests if you want.
5. We review the code (we don't really care about the code itself, the purpose of the exercise is collaborative discussion) and accept the Pull Request, merging your code into the function.
6. That's it!

You can add as many features as you want, you can make one update or multiple updates, multiple are more than welcome because it is practice, practice, practice! We will then review the whole project and award the prizes.

What can I win?

We have: 4 x Paperback copies of The Phoenix Project 2 x Hardback copies of Continuous Delivery

They will be mailed to the winners.

What are you looking for and scoring on?

So the important things to us are:

1. Collaboration on coding - discussion of what you're doing, coordination, taking feedback and contributing code
2. Use of GitHub features - we want you to show that you're learning Source Control and taking it seriously
3. Good code practices - we are looking for code that is shareable, not something that someone will inherit and curse your use of Aliases and so on! Make it understandable to everyone else and you're good to go
4. Pester Tests - this is actually optional but you get great favouritism if you create tests! Admittedly, Pester is not straightforward if you are not used to writing tests but you will not regret mastering the concepts, it is so valuable in DevOps.

So when does the contest close?

November 20th.

What learning resources can I use?

To be posted

That's all folks! We open this challenge on 10th October 2015. Happy coding and look forward to collaborating with you!!