Chief Alchemist - Business Consulting For The 21st Century Via A Holistic & Intelligent Approach
Share RSS 2.0 feed for Sign up for the mailing list. Follow Chief Alchemist on Twitter. 'Like' the Chief Alchemist's page on Facebook. See what Chief Alchemist has been Q&A'ing on Quora. Chief Alchemist bookmarks & highlights on Follow the Chief Alchemist on Chief Alchemist channel on Chief Alchemist on Flickr. Mark 'Chief Alchemist' Simchock on LinkedIn. Free Initial Consultation. Email Chief Alchemist. Phone Chief Alchemist.
  • Mark ‘Chief Alchemist’ Simchock
  • 'Email me.Email => ca .at. ChiefAlchemist .dot. com
  • 'Phone me.Alchemy United => 732 997-0028
  • Free initial consultation.Free => Initial Consultation
  • Please be sure to subscribe to your communication channels of choice.
  • Click To Close => The small green (consultation), red (email) or blue (phone) icons in the top upper right.
Business Consulting For The 21st Century Via A Holistic & Intelligent Approach

GitHub and blog posts vs books and finding a mentor

Consumed => “Team Collaboration for Building with Open Source Code” by Jake Rocheleau on Speckyboy Design Magazine.

=> My value add (i.e., left a comment)…

Good stuff Jake, three quick thoughts:

1) I believe Trello is popular with developers/engineers because its metaphor (if you will) maps well to the agile methodology. For those who are interested, here’s a link to a free copy of Agile for Dummies:

1.5) For PM, Asana ( is also worth a mention.

2) Agreed, there is plenty of code to find. The issue is, which 50% of it constitutes higher quality and best practices, and which does not? The point is, it’s very easy to pick up bad habits and very hard to identify those that are best in class. GitHub and blog posts still don’t replace books and finding a mentor.

3) That said, when writing code, we should all be more mindful that there’s a good chance that someone else might see and use that code. Cryptic variable / method names are so 20th century at this point and should, in 2013, be considered unacceptable. Lack of comments is not a best practice. Period! We need to shift from judging code on how complex (and un-understandable) it is, and give points to how its able to turn complexity understood by one (or a few) into something that is clear, transparent and usable to as many as possible. Is that not the true intention of Open Source? GitHub, JSFiddle, etc. are supposed to be a valuable resources, not garbage dumps, yes?

Will not be published. Required.
Please include http://