My two cents about software development on the web


How to run a good workshop

How to run a good workshop by Scott Berkun

Workshops are hopeful things. They’re sold on so much promise, but that promise is often dashed as students discover their instructor has little idea how to teach anything.

For years I was a workshop guy. I taught them, I studied them, I even hired people to do them for other companies. I watched many instructors run them and I know the common mistakes. Here’s my best advice on how run a workshop people will love.

  1. A 3 hour lecture is not a workshop
  2. The more students you have, the less of a workshop it is
  3. Work the triad: explain, exercise, debrief
  4. Stay out of the center
  5. Beta test your exercises
  6. Match promises to exercises
  7. Always have a whiteboard or flipchart in the room
  8. The room should look like a workshop when you are done
  9. Build a workshop checklist
  10. Give students the next thing to do after they leave



Learning Git

Git is a free and open source distributed version control system. Git originates from the Linux development community and is used by many popular Open Source projects. Since its birth in 2005, Git has evolved and matured to be easy to use and yet retain its initial qualities. It’s incredibly fast, it’s very efficient with large projects, and it has an incredible branching system for non-linear development.

Here are references to tutorials I used to learn Git.


Importance of testing with large data sets

It’s sometimes hard or impossible to get suitable large data set that represents real data for your product. That’s why it’s important that already when you are learning a new technology you train your skills with large data sets. This way you will learn the performance and concurrency challenges when running your own throwaway training programs where it’s easier to find sample data rather than later building the product for a company.


Plan your first application in a way that you can run large data sets through it. Even if it’s purpose is for you to just learn the technology. Nowadays there are so many easy to use libraries for accessing xml-files, data-files, databases, etc. that it will not add much effort on your application development to support importing large sets of data. And learning to import data is surely a skill that you’ll need later.

source: Importance of testing with large data sets


Introduction to Android development : TouchCalculator – CodeProject®


In this tutorial article I will try to introduce you to the general development principles of Android by building a real calculator application (TouchCalculator). By the end of this tutorial you will be able to build Android applications with simple user interfaces and backing business logic.

See on Introduction to Android development : TouchCalculator – CodeProject


Why Developers Should Understand Design

Mike Kus recently published this article about why designers should be able to code.

We might suggest the opposite article be written as well: Why Developers Should Understand Design. Expanding your knowledge of the industry certainly can’t hurt the quality of the work you output… yet there’s a time and a place for specialists in the mix, too.

From our small (yet global) studio perspective, it’s in our best interest to be generalists. Generalists are big picture people. They get the connections between things, and they understand the world view.

Specialsts have their place, and in a big company they absolutely fit in. But in small business like ours, we thrive off diversely talented people who are good at understanding many things.

source: A Generalist Mentality