diff --git a/_includes/latest_project.html b/_includes/latest_project.html index d4420f8..a954333 100644 --- a/_includes/latest_project.html +++ b/_includes/latest_project.html @@ -1,19 +1,19 @@

current

-

The latest Code52 project is Say Wat? - a NodeJS experiment +

The latest Code52 project is Show and Tell

-
Say Wat? is an introduction to building NodeJS applications around a simple and fun idea. Details here.
+
We want to hear from you about the cool things you've been experimenting with or the cool things you've built. We explain the idea in more details here.

Want to get involved?

-
Not interested in this one? We'll announce the next project at approx. 10pm Sydney time, Monday. You can contribute to our past projects too!
+
Interested in contributing some code? You should check out our past projects!
\ No newline at end of file diff --git a/_posts/2012-04-09-say-wat-recap.md b/_posts/2012-04-09-say-wat-recap.md new file mode 100644 index 0000000..9fda11e --- /dev/null +++ b/_posts/2012-04-09-say-wat-recap.md @@ -0,0 +1,26 @@ +--- +layout: post +permalink: /say-wat-recap.html +date: 2012-04-09 23:59 +title: "Say Wat? Recap" +author: "@shiftkey" +comments: true +--- + +With the long weekend due to the Easter break, this has been an interesting and relaxed week for all involved. + +As I need to dive into preparing the next project, here's a bullet list version of the recap. Or you can just go and play around with the site: [sayw.at](http://sayw.at). + +### What we acheived + + - **Learning how a good NodeJS application is structured** - much love to [Chris Sainty](http://twitter.com/csainty) for giving us some guidance on this. While initial demos show off cool things like building chat servers, going from that to separating application configuration and logic. + + - **MongoDB** - we had a relatively simple schema to represent our data (question, answers and users) and MongoDB was an ubiquitous option for us to test locally or use in live environments. With the availability of [hosted databases](http://mongohq.com) and support on many cloud providers (even [Azure](http://www.mongodb.org/display/DOCS/MongoDB+on+Azure)) this was an easy choice. + + - **Deployment** - we can take the one codebase and deploy it today to Heroku and AppHarbor (as long as they have a MongoDB addin configured too). We also learned about how node_modules should be treated in [source control](http://www.mikealrogers.com/posts/nodemodules-in-git.html) and were bitten by overnight releases of packages breaking pull requests. + + - **Testing** - we added JSHint (static analysis tool for Javascript syntax) and Mocha (unit testing framework) and learned how easy it was to setup [Travis-CI](http://travis-ci.org) to build the project directly from the Github repository. + +### What's next? + +As this was a relaxed weekend, there's still a [number of tasks](https://trello.com/board/saywat/4f7974869bf90505711b92f8) to be picked off before the client (being @shiftkey) is happy with a V1 release. We've got a wiki which should help with [getting started](https://github.com/Code52/saywat/wiki/Getting-Started) on setting up your project. \ No newline at end of file diff --git a/_posts/2012-04-10-dodo.md b/_posts/2012-04-10-dodo.md new file mode 100644 index 0000000..25a5942 --- /dev/null +++ b/_posts/2012-04-10-dodo.md @@ -0,0 +1,29 @@ +--- +layout: post +permalink: /dodo.html +date: 2012-04-10 01:00 +title: "dodo" +author: "@shiftkey" +comments: true +--- + +A few weeks ago, we had a discussion about building a Twitter app. As a group with [history](http://www.theleagueofpaul.com/mahtweets-is-dead) in building apps, we didn't want to do something conventional - and with Windows 8 being focused on the tablet space we started down a different path. This quickly became one of our [hot ideas](https://code52.uservoice.com/forums/143105-code-52/suggestions/2673882-metro-style-twitter-client) and we've had lots of people asking when we're going to kick it off. + +### Capturing the madness + +Rather than use JabbR to capture the discussion, we used **sync.in** to write down and edit our ideas. Aside from a minor hiccup with the cap on concurrent users, we had a productive hour or two discussing ideas in real-time and having a nicely formatted document at the end. + +The results of this can be found [here](http://sync.in/KlhETAjkLy) and those will be tranformed into the backlog for tasks to acheive this week. + +### Goals + +To identify some broad goals for the week: + + - the project should ship a reusable Twitter library as well as a client + - the client will not follow the existing norms of displaying lists of tweets + - the client should demonstrate some wicked animations and transitions + - the client should implement some radical features for other Twitter clients to shamelessly steal + +### Get Involved + +We've started a skeleton of the app (it should allow you to authenticate and render some tweets) on [GitHub](https://github.com/Code52/dodo) and the [Trello board](https://trello.com/board/dodo/4f82e9dfc10221fb0db2cff2) has some initial tasks which are small enough to be started if people are curious. Got some ideas? There's people in the [JabbR](http://jabbr.net/#/rooms/code52) room to discuss ideas with. \ No newline at end of file diff --git a/_posts/2012-04-16-dodo-recap.md b/_posts/2012-04-16-dodo-recap.md new file mode 100644 index 0000000..159e860 --- /dev/null +++ b/_posts/2012-04-16-dodo-recap.md @@ -0,0 +1,62 @@ +--- +layout: post +permalink: /dodo-recap.html +date: 2012-04-16 20:30 +title: "dodo recap" +author: "@shiftkey" +comments: true +--- + +The Code52 team had some big news over the weekend which I will address in a later post, but before we should get to the fun stuff about [dodo](http://github.com/Code52/dodo). + +## What's been done so far + +This week has been about setting up a baseline and implementing core functionality. + +At this point in time, the project is split into two distinct features: + + - *dodo* - a Windows 8 Metro application. + - *boxkite* - a library for interacting with the Twitter API in .NET 4.5 Metro. + +## dodo + + The application currently supports: + + - OAuth login + - Browsing the user's timeline, mentions, retweets and messages. + - settings storage - persisting the user's token between sessions + - diagnostics capture - so that we can log messages to the application's sandbox for debugging purposes. + +Other functionality which as been started on but not integrated into master includes + + - Grouping tweets by relative time ("just now", "last hour") + - Semantic Zoom - collapse a group of tweets to see just the user's avatars + - User Streams - rather than querying for data periodically, Twitter can stream data down to an open connection inside the app. + + ![](/img/dodo-example.png) + +## boxkite + +Once boxkite is feature-complete, tested and documented, it will move to a separate repository with NuGet packages available so that people can consume the API. + +There are no immediate plans for boxkite to support other framework versions, as: + + - it uses a number of .NET 4.5-specific features - including async/await and WebAuthenticationBroker. + - there are a number of [existing libraries](https://dev.twitter.com/docs/twitter-libraries#dotnet) out there for .NET apps + - I would prefer to focus on the dodo application itself in the short term. + + If you still have the urge to check out a shiny new Twitter library, [Matt Hamilton](http://twitter.com/mabster) spent the week building a .NET 4 client called [Budgie](http://matthamilton.net/budgie) that uses the Task Parallel Library heavily. + +## The future of dodo + +Yes, that's a joke. + +I'm keen to continue building this application for several reasons: + + - many developers have been interested/curious to learn about it - while the concept of a Twitter app are familiar, being able to see the internals is where the real educational value lies. + - I still have an urge to create a different experience for people to interact with Twitter. With the basics done, the next step is to focus on the UX. + - There is enough lead time to have something ready for when Windows 8 ships. + - There is still [a lot of work still to do](https://trello.com/board/dodo/4f82e9dfc10221fb0db2cff2). + + And yes, others are more than welcome to get involved. Come [hang out](http://jabbr.net/#/rooms/code52). + diff --git a/_posts/2012-04-16-learning-week.md b/_posts/2012-04-16-learning-week.md new file mode 100644 index 0000000..464a13a --- /dev/null +++ b/_posts/2012-04-16-learning-week.md @@ -0,0 +1,54 @@ +--- +layout: post +permalink: /show-and-tell.html +date: 2012-04-16 23:00 +title: "show and tell" +author: "@shiftkey" +comments: true +--- + +The Code52 organisers have been bouncing around an idea over the past couple of weeks, but before we dedicate some time to getting it off the ground we want to test out our theory with a little experiment. And it involves you. + +## Some Background + +Since we kicked off Code52 at the start of the year, we've talked with many developers who are keen to get involved with OSS development but don't really have the time to dedicate a full week to working on a specific idea. + +Does that sound like you? Well this is your week. + +We want to hear about what you have been working with in your spare time. We want to hear about the cool stuff we haven't had a chance to use. We want to get jealous about hearing how you've used it and what you've learned about it. + +In short, we want to hear your stories. + +## Show and Tell + +We're looking for people to write short articles on stuff they've used recently or something they've built recently to share with the big wide world. + +We want to hear: + + - what did you find that is awesome? + - what is awesome about it? + - how did you use it? + - what did you learn from using it? + - is there some code that people can have a play with? + +It doesn't have to be a long post. And things like pictures and code snippets are fine to help show it off. + +## But how? + +Got something you want to share? You've got a few options + +### I've already posted it! + +Already written about something cool you'd like to share? Tweet a link to the [@Code_52](http://twitter.com/Code_52) account and we'll get in touch. If we're suitably impressed by your awesomeness, we'll share it with the world. + +### I don't have a blog! + +Don't have a blog? Don't worry! You can fork [this website](http://github.com/Code52/code52.github.com) on GitHub and add your own post to the [posts folder](http://github.com/Code52/code52.github.com/tree/master/_posts). Once you've written the post, send us a pull request and we can proof-read it before pushing it live. + +If you haven't seen it before, the site layout and content is used as input for [Jekyll](http://github.com/mojombo/jekyll/wiki) to generate the site content. + +### I'm not sure where to start! + +The Code52 gang built a tool for editing Markdown files - called [MarkPad](http://code52.org/DownmarkerWPF). This is a great way to get started with writing your own posts (its easier than writing HTML, and you can see the rendered content as your write it). + +If you drop into the Code52 [chat room](http://jabbr.net/#/rooms/Code52) we can help with editing and getting the content up on the site. \ No newline at end of file diff --git a/_posts/2012-04-17-show-and-tell-tugberkugurlu.md b/_posts/2012-04-17-show-and-tell-tugberkugurlu.md new file mode 100644 index 0000000..9fd2087 --- /dev/null +++ b/_posts/2012-04-17-show-and-tell-tugberkugurlu.md @@ -0,0 +1,35 @@ +--- +layout: post +permalink: /show-and-tell/1/generic-repository-pattern.html +date: 2012-04-17 23:00 +title: "Show and Tell #1 - Generic Repository Pattern series" +author: "@shiftkey" +comments: true +--- + +## Introduction + +When Tugberk sent me the link last night to this series, my curiousity was piqued. The generic repository pattern is something we had used for previous Code52 projects - which had also used Entity Framework as the backing store. + +For those who are not familiar with it, a *repository* is typically defined as (from [Edward Hieatt and Rob Mee](http://martinfowler.com/eaaCatalog/repository.html)): a component which "**mediates between the domain and data mapping layers using a collection-like interface for accessing domain objects.**" + +Why use the repository pattern? + + - decouple the application logic from the data access logic + - test the application logic in isolation - swap out the database for an in-memory collections of data. + + Anyway, before I go spoiling the content, Tugberk has written a series on this: + + - in the [first part](http://www.tugberkugurlu.com/archive/generic-repository-pattern-entity-framework-asp-net-mvc-and-unit-testing-triangle), he discusses the pattern and why you should care. + - in the [second part](http://www.tugberkugurlu.com/archive/how-to-work-with-generic-repositories-on-asp-net-mvc-and-unit-testing-them-by-mocking), he explains how you can use this with Entity Framework and MVC3. + - and to finish, he's [released](http://www.tugberkugurlu.com/archive/entity-framework-dbcontext-generic-repository-implementation-is-now-on-nuget-and-github) NuGet packages for bringing generic repositories into your apps (and the source is on GitHub). + +Lots of detail, lots of code samples. I hope you enjoy it. + +## About the Author + +Tugberk Ugurlu hails from Turkey and juggles university studies with his work as a Programmer and Internet Sales Director. He blogs at [www.tugberkugurlu.com](http://www.tugberkugurlu.com/) and is [@tourismgeek](http://twitter.com/tourismgeek) on Twitter. + +## Addendum + + - If you want to learn more on the repository pattern, Jon Galloway and Jesse Liberty did a screencast on **[Building a Repository using TDD](http://channel9.msdn.com/Series/The-Full-Stack/The-Full-Stack-Part-3-Building-a-Repository-using-TDD)** for their video series "The Full Stack". Check it out. diff --git a/_posts/2012-04-18-show-and-tell-garfbradaz.md b/_posts/2012-04-18-show-and-tell-garfbradaz.md new file mode 100644 index 0000000..d5ad1a7 --- /dev/null +++ b/_posts/2012-04-18-show-and-tell-garfbradaz.md @@ -0,0 +1,21 @@ +--- +layout: post +permalink: /show-and-tell/2/mvc-image.html +date: 2012-04-18 23:00 +title: "Show and Tell #2 - Learning by building MvcImage" +author: "@shiftkey" +comments: true +--- + + +## Introduction + +This post is from Gareth Bradley, who found the Code52 chatroom by accident while he was checking out [JabbR](http://jabbr.net/). When we announced the "Show and Tell" week, he wrote a post about what he does for a living and what [he's been learning in his spare time](http://garfbradazweb.wordpress.com/2012/04/16/code52-show-tell-my-open-source-application/). + +I share the same view as Gareth in that I **learn best by building something useful** - and Gareth's put together his own OSS project as a way to demonstrate what he's learned. + +The project code is at [mvcimage.codeplex.com](http://mvcimage.codeplex.com/), and I hope to see more cool stuff from him in the future. + +## About the Author + +Gareth Bradley is a 4GL applications developer on OpenVMS systems by day and learning various other technologies (including C#, C++, XNA and ASP.NET) by night. You can find his blog at [garfbradazweb.wordpress.com/](http://garfbradazweb.wordpress.com/) and he's also on Twitter as [@garfbradaz](http://twitter.com/garfbradaz). diff --git a/_posts/2012-04-19-show-and-tell-mabster.md b/_posts/2012-04-19-show-and-tell-mabster.md new file mode 100644 index 0000000..a7a88cc --- /dev/null +++ b/_posts/2012-04-19-show-and-tell-mabster.md @@ -0,0 +1,93 @@ +--- +layout: post +permalink: /show-and-tell/3/task-parallel-library.html +date: 2012-04-19 23:00 +title: "Show and Tell #3 - Building Budgie with the Task Parallel Library (TPL)" +author: "@shiftkey" +comments: true +--- + +## Introduction + +For those of you who aren't familiar with it, [Matt Hamilton](http://twitter.com/mabster) wrote a Twitter API library over a few nights last week as an experiment to better understand the Task Parallel Library. + +He's named it Budgie - you can [read up about it](http://matthamilton.net/budgie), browse the [source code](http://bitbucket.org/mabster/budgie), install the [NuGet packages](http://nuget.org/packages/Budgie) or try out his Twitter client [Halfwit](http://madprops.org/halfwit/) which uses it. + +I asked Matt if he was interested in discussing why he decided to use the TPL for his project and what was cool about it. + +## The problem with asynchronous code + +When thinking about what [Budgie's](http://matthamilton.net/budgie) surface API was going to look like, I knew one thing: it would be asynchronous only. There would be no methods like `GetHomeTimeline()` that blocked and waited for Twitter to respond. + +There are any number of ways to write asynchronous APIs. The one I've been most comfortable with to date (used in TweetSharp, another Twitter library that heavily informed Budgie) is to ask for a callback as a parameter to your method, and call that when your asynchronous task is done. For example: + + public void DoStuff(string text, Action callback) + { + // step 1: do stuff with text asynchronously + DoStuffResult result = ...; + + // step 2: call the callback with the result + callback(DoStuffResult); + } + +This technique works really well, but with the advent of C# 5 and the new "async" and "await" keywords, a new approach became the obvious choice: using the Task Parallel Library. + +The idea is simply to return a "hot" `Task` (that is, a task that is already running) from your method: + + public Task DoStuff(string text) + { + return Task.Factory.StartNew(t => ..., text); + } + +Note that the method above returns a `Task`, which is a special kind of `Task` that returns a result. If your method doesn't need to return a value (like a void method) you would return a non-generic `Task` object instead. + +The calling code can then decide what to do with that task. They might decide to block and wait for it to finish: + + DoStuffResult result = DoStuff("hello world").Result; + +Or they might use a continuation: + + DoStuff("hello world").ContinueWith(result => { ... }); + +Or, in C# 5, they might use the non-blocking "await" keyword: + + DoStuffResult result = await DoStuff("hello world"); + +Using the Task Parallel Library gives the caller some flexibility in that regard, and the fact that it integrates so seamlessly into the C# 5 syntax made it an obvious choice. + +## Using the TPL with WebRequest + +I decided to use good ol' `System.Net.WebRequest` when making my calls to Twitter, partly because it offered fine-grained control over the request and partly because I was doing "Google Driven Development" and a lot of code samples out there use it. + +`WebRequest` offers an async API in the form of its `BeginRequest` and `EndRequest` methods, and as it turns out, the TPL gives us a really easy way to turn those calls into a `Task`: + + return Task.Factory.FromAsync(request.BeginGetResponse, request.EndGetResponse, null); + +That returns a running Task which is performing the request and will return the response in the `Result` property. + +Budgie, however, doesn't use it. Why? Because I wanted all HTTP requests in Budgie to honour a Timeout property, and WebRequest doesn't honour its own Timeout property unless you use the synchronous `GetResponse` method. So my code actually looks like this: + + return Task.Factory.StartNew(() => request.GetResponse()); + +It could be argued that that's actually _more_ readable. :) + +From there I can use a continuation (since Budgie is written using C# 4 and doesn't make use of the "await" keyword) to take action when the task completes: + + return requestTask.ContinueWith(t => + { + if (t.StatusCode != System.Net.HttpStatusCode.OK) return null; + + Foo result = new Foo(); + + // populate result by deserializing the JSON returned in the response + + return result; + }); + +It's worth noting that `ContinueWith` in this case is returning a `Task`, since I've passed it a `Func` to execute. The fact that I'm "continuing" from a `Task` doesn't mean I have to return that type. + +All in all, it's pretty easy! Easier still had I written this code with C# 5, but I wanted to be able to build this from my home PC which doesn't have .NET 4.5 or the Async CTP installed. + +## Wrapping Up + +Using the TPL to create an asynchronous API is the logical choice in modern .NET development, and I wouldn't have done anything different in Budgie. I'm looking forward to the final release of VS11 and .NET 4.5, at which point I'll refactor the code to make use of the "await" keyword, but for now it's good to know that you can do this in a future-proof way with the current tools. diff --git a/_posts/2012-04-20-show-and-tell-davidburela.md b/_posts/2012-04-20-show-and-tell-davidburela.md new file mode 100644 index 0000000..3ecc03f --- /dev/null +++ b/_posts/2012-04-20-show-and-tell-davidburela.md @@ -0,0 +1,26 @@ +--- +layout: post +permalink: /show-and-tell/4/using-dvcs-to-host-code-examples.html +date: 2012-04-20 23:00 +title: "Show and Tell #4 - Using DVCS to host code examples" +author: "@shiftkey" +comments: true +--- + +## Introduction + +Ever come across a blog post from ancient history which includes an attachment that you really really need, but the link no longer works? [This post](http://davidburela.wordpress.com/2012/04/17/developer-blog-banter-3-responsecommunity-coding/) is for you. + +David Burela did a writeup this week on: + + - how he used to manage code samples with his blog posts + - the problems and limitations of this approach + - how he is using GitHub to make life easier for himself and his readers + +He explains how you can create your own repositories and include documentation, and references a [Windows Phone application](https://github.com/DavidBurela/Windows8DeveloperCampPhoneApplication) he wrote recently. + +David also mentions [MarkPad](http://code52.org/DownmarkerWPF)- an application built by the Code52 community to make writing Markdown-based files easier. + +## About the Author + +David Burela lives in Melbourne, Australia and focuses on Silverlight, Windows Azure and Windows Phone 7 development. He also just finished his first book "Microsoft Silverlight 5 and Windows Azure Enterprise Integration". He blogs at [DavidBurela.Wordpress.com](http://DavidBurela.Wordpress.com/) and is [@DavidBurela](http://twitter.com/DavidBurela) on Twitter. diff --git a/_posts/2012-04-22-show-and-tell-laumania.md b/_posts/2012-04-22-show-and-tell-laumania.md new file mode 100644 index 0000000..289ca07 --- /dev/null +++ b/_posts/2012-04-22-show-and-tell-laumania.md @@ -0,0 +1,24 @@ +--- +layout: post +permalink: /show-and-tell/5/porting-a-silverlight-game-to-xna-on-wp7.html +date: 2012-04-22 23:00 +title: "Show and Tell #5 - Porting a Silverlight game to XNA" +author: "@shiftkey" +comments: true +--- + +## Introduction + +Mads sent through a [blog post](http://www.laumania.net/post/2012/04/21/My-show-and-tell-post.aspx) yesterday about how his experiment on porting a game from Silverlight to XNA. + +His starting point: a game called "We are Bugs" from [Jeff Weber](http://www.farseergames.com/). + +You can go and play it [here](http://www.farseergames.com/wearebugs). I'll wait. + +Back? Great. So Jeff made the source code [available](http://www.farseergames.com/blog/2009/4/30/we-are-bugs-refactored-and-source-released.html) a while ago, and Mads has experimented with porting the code to Silverlight in WP7 and then in XNA. + +[His results are up on GitHub](https://github.com/Laumania/WeAreBugs-XNA) for those who want to compare and contrast the differences. + +## About the Author + +Mads Laumann is a developer from Denmark who works with C# and ASP.NET by day and experiments with a other Microsoft technologies in his spare time. He blogs at [laumania.net](http://laumania.net/) and is [@laumania](http://twitter.com/laumania) on Twitter. diff --git a/_posts/2012-04-25-re-evaluating-code52.md b/_posts/2012-04-25-re-evaluating-code52.md new file mode 100644 index 0000000..05d4492 --- /dev/null +++ b/_posts/2012-04-25-re-evaluating-code52.md @@ -0,0 +1,63 @@ +--- +layout: post +permalink: /reevaluating-code52.html +date: 2012-04-23 23:00 +title: "Reevaluating Code52" +author: "@shiftkey" +comments: true +--- + +I've been mulling over the contents of this post over the past couple of weeks - while it's been an amazing experience thus far, a few events behind the scenes have triggered some changes. + +## Farewells and Distractions + +Last week @aeoth decided to step down from his role co-ordinating and contributing to the Code52 group. He's been a big part in many of the things we've built so far, and we wish him the best with his future endeavours. + +@shiftkey will be spending his weekends living in airports as part of the Windows 8 Dev Camps around Australia over the coming weeks - plus some other things which he will talk about in the future - so he will not be as contactable as he has been previously. Once he returns from holidays in July (after [dddSydney](http://dddsydney.com) in fact) the schedule starts to look more like that of a normal person. + +So with logistics getting tougher to organise each week, we want to adapt to the situation in front of us - for everyone's benefits. + +## Rethinking the process + +So rather than continuing down this path to self-implosion, we want to try some changes to the process: + + - We want to start projects **when people want to build something** + - We want **the people involved to choose what we build** + - We want to **help people become contributors** + - We want to ensure that **everyone has fun and learns from the experience** + +## Nothing is set in stone + +Keep in mind that this is one big long experiment, and **we want you to get involved**. + +We've got a [massive backlog](https://trello.com/board/schedule/4f20b3df0162d41c670ffc6b) of ideas - if something stands out on that list that you'd like to work on, get in touch - [JabbR](http://jabbr.net/#/rooms/code52), [twitter](http://twitter.com/Code_52), or [email](mailto:code52@code52.org) all work. If you have something else that you'd like to do that's not on the list, don't worry - just get in touch through the same channels. + +With this change we are planning to drop our most radical requirement - time constraints. Up until this point, we've constrained ourselves to one week to focus on a project and get something working - which has been challenging at times. + +With this change, hopefully this frees projects up to evolve at their own pace and reduces the pressure on everyone. As we've found organising this, sometimes life just gets in the way - and that shouldn't be a barrier to getting involved. + +A complementary change to this is how we announce projects. Once we organise a project and a group of people to get involved, we aim to announce ahead of time (a week?) the project. This should give enough time for the group to get the groundwork in place, and give people who are following the action time to declare their interest and availability. + +## So what next? + +@shiftkey has something he wants to kickstart - specifically [this idea](https://code52.uservoice.com/forums/143105-code-52/suggestions/2730885-git-heat-map-generator) - but until he gets some spare time (next week at best), now is the opportunity for people to take charge and get involved - **what do you want to build?** + +@shiftkey has a number of OSS projects on the go - getting [Markpad](http://code52.org/DownmarkerWPF) in-app updates running, adding features to [Dodo](http://github.com/Code52/dodo), dogfooding [NSync](http://github.com/xpaulbettsx/nsync) on an internal app, reviewing pull requests and answering questions on JabbR - so I'll be hanging out in the [JabbR](http://jabbr.net/#/rooms/code52) room whenever I'm coding in my spare time. + +And of course, the [JabbR](http://jabbr.net/#/rooms/code52) room also tracks conversation history - so you can drop in and see what people have been talking about previously or just hang out and chat. + +## This week: @shiftkey explains more + +Over the course of this week, Brendan will discuss some of the philosophical goals in mind for Code52. While these are relatively simple goals, he will also discuss what we've learned so far and how we can improve things going forward. + +The topics he has in mind so far: + + - Always learning new things + - Push, Not Pull + - It should be fun + - Keep a balance + - Planning is a good thing(tm) + +Hopefully this helps to undestand more of what's been going on behind the scenes, and gives you a better idea of the *what*, *how* and *why* of Code52. + +We'll also keep the [Show and Tell](http://code52.org/show-and-tell.html) open as an ongoing thing people who want to share things they've learned or worked on - you should keep an eye on our [Twitter](http://twitter.com/Code_52) account for announcements. \ No newline at end of file diff --git a/_posts/2012-04-30-show-and-tell-belfryimages-setting-up-mef.md b/_posts/2012-04-30-show-and-tell-belfryimages-setting-up-mef.md new file mode 100644 index 0000000..bd568da --- /dev/null +++ b/_posts/2012-04-30-show-and-tell-belfryimages-setting-up-mef.md @@ -0,0 +1,18 @@ +--- +layout: post +permalink: /show-and-tell/6/setting-up-mef.html +date: 2012-04-30 20:00 +title: "Show and Tell #6 - Setting up MEF" +author: "@belfryimages" +comments: true +--- + +## Setting up MEF + +Ben posted yesterday about [setting up MEF](http://blog.belfryimages.com.au/setting-up-mef.html) with the goal of adding plugins to a simple application. It touches on splitting the plugin API from the application code, including two-way communication between the application and the plugin. This method will possibly be used to implement plugin support in [MarkPad](http://code52.org/DownmarkerWPF/). + +The project created for the post is [available on GitHub](https://github.com/belfryimages/mef-test). + +## About the Author + +Ben Scott is a developer from Rockhampton, Australia. He is employed as the IT manager of a financial planning firm, where he largely works on a C#, WinForms-based in-house investment portfolio management system, plus a number of slightly more interesting projects, some of them in */gasp/* PHP. In his spare time he likes to write posts about himself in the third person using other people's websites. He very occasionally writes at [blog.belfryimages.com.au](http://blog.belfryimages.com.au) and can usually be found on Twitter [@belfryimages](http://twitter.com/belfryimages) where he posts blurry photos of his lunch and complains about things. diff --git a/img/dodo-example.png b/img/dodo-example.png new file mode 100644 index 0000000..1dcce47 Binary files /dev/null and b/img/dodo-example.png differ diff --git a/projects.html b/projects.html index e7ba9bb..7ce50e9 100644 --- a/projects.html +++ b/projects.html @@ -1,6 +1,6 @@ --- layout: post -title: Previous Projects +title: Project Contributors --- diff --git a/readme.md b/readme.md index 284315d..975ae3a 100644 --- a/readme.md +++ b/readme.md @@ -6,12 +6,3 @@ Links - http://code52.uservoice.com/ -- suggestions and voting -Random slogans: - -- "new coding every week" -- "coding fun and games" -- "crowdsourcing software projects" -- add your own - - -