Data Driven Portfolios using RESTful APIs

How developers can let their work speak for itself.

Transcript

1. Data Driven Portfolios using RESTful APIs Why you want open and easy access to your profile data.
2. Let your work speak for itself. • Keep the focus on coding – let the tools automatically showcase you and your projects. • Avoid duplication of labor – drive the profile from the data source. • Trust shouldn’t be an issue – The services you use should prove your worth.
3. Why REST? In a word, consumability. You want this information to not only be public and accessible, you want it to dead easy to use by anyone who wants to showcase your skills. Our job is to focus on being sure the data that is stored in these RESTful systems is what we want it to be, and targeted to our consumer.
4. A little like SEO • Pick a professional profile handle, keep it consistent, keep it clean. • If your reputation is not clean, try and drive good search results above it. • Tools to monitor your reputation: google – use this the way an employer might TONS of services to help you here mention.net - http://bit.ly/XGPnNK
5. GitHub These guys changed the game, by getting to the most important data source for developers, source code, and showcasing it in a transparent, easy to use, fun and cool way that showcases the developer.
6. Project Hosting + How is it showcasing me? • GitHub – The center of the open source universe. • Bitbucket – Free private repos! • Codeplex – API questionable open, still very important for Microsoft developers. • Assembla – lots of tools, costs money • Gitorious • Gna.org • Savannah • Google code • Java.net • Sourceforge
7. Other than hosting projects… There are still a lot of great ways to make your work public • Work in the cloud – Koding, compilr, cloud 9 (c9.io) • Integrate into your IDE – Channel9 for VS • Prototyping/Snippets – codepen, jsfiddle
8. Learning and Teaching • Learning - Code School, Treehouse, coursera • Presentations – Speakerdeck, Slideshare • Even the stuff you read can help you get a job! Readability, Pocket, Instapaper • Meetup – Join your local developer group. • Learning can be fun! Project Euler, Fight Code
9. Publishing You may or may not have a choice about this, but try and release your code on a marketplace that can showcase you as a developer. • App store • CPAN • Rubygems • npm • Nuget • Envato • html5 ninja
10. Documentation • If it’s not secret sauce, make it public. Other people can learn from it, and it lends you credibility. • Put it on your own blog, but also publish to applicable forums – codeproject, java.net, ycombinator’s hacker news, gamedev.net.
11. Above and Beyond – Community • Help Your Community - Your ability to communicate solutions to problems can be proven to the world! Stackoverflow, codeproject, java.net, gamedev.net, ycombinator’s hacker news. • If visual design is part of your game, make sure you are sharing and getting feedback on Dribbble, Forrst, or Behance. For example…
12. Above and Beyond – Networking • LinkedIn – It’s not a wonderful site, but a lot of the people that are hiring will expect to connect with you here. • Twitter – You can meet a lot of new people this way. • Developer Centric Social Networks and Profiles – cloudspokes, geeklist, coderwall. • Wait, what about coderbits?
13. What’s in it for me? • Klout – gives you a score of your influence, based on all the typical social networks, twitter, fb, etc. • Coderwall – Badges for your github • Workforpie (no API) – Scores you, get ready for some data entry • Masterbranch (API theoretically?) – source code scoring, from more than just github
14. Coderbits • More than 50 services consumed, even the ones that don’t have nice APIs. • Automatic social connections. • Lots of badges to earn, anywhere you code. • And yes, we have a REST API. • Beta invites available.