that means working code that I can run, and access to all of it. Probably the best thing is a running website and a github repository. If the software is hard to run, then a video walkthrough or screenshots are acceptable substitutes.

1. Use of the code requires attribution
2. You can't put GPL code in the App Store
3. I can still grant BSD licenses on a case by case basis, and perhaps only on portions. To do so requires the developer to get in touch with me
4. Likewise, I can still choose to sell or give away commercial licenses, if I am contacted.

Photos capture information that you cannot get via written notes. Taking pictures of an object or a document can provide more insight that simple notes.

Dr. Lydia Zepeda and David Deal of the University of Wisconsin–Madison enlisted 43 subjects to photograph all of their meals or snacks prior to eating. Unlike food diaries, which require time-consuming entries often written long after eating, the photographs acted as an instantaneous intervention and forced people to consider their choices before the damage was done. In the words of one participant: “I was less likely to have a jumbo bag of M&Ms. It curbed my choices. It didn’t alter them completely, but who wants to take a photo of a jumbo bag of M&Ms?”

The researchers concluded that photographs are more effective than written food diaries. This is saying something, as prior studies had confirmed that subjects who use food diaries lose three times as much weight as those who don’t.

It happened despite having a clear, front row view of the transition of the industry from mobile voice to mobile computing. The shift in the basis of competition from “connecting people” to “connecting people to data” ended up being a classic disruptive trap. Many will argue that it was the failing of individual managers. Perhaps, but how did they conspire to fail simultaneously?

When you see disruption happening, it’s natural to seek out a cause, a pivotal magical “force” or event that enabled the weak to humble the strong–the proverbial sling that enabled David to defeat Goliath.

With the new touch-based devices of today, we are seeing similar migrations of utilization to new jobs to be done. The simpler creative tasks migrate first and the advanced (or emergent) uses follow. Like with the microcomputer, the first common creative task for tablets happens to be text-based editing.

Get specific. When you set yourself a goal, try to be as specific as possible. "Lose 5 pounds" is a better goal than "lose some weight," because it gives you a clear idea of what success looks like. Knowing exactly what you want to achieve keeps you motivated until you get there. Also, think about the specific actions that need to be taken to reach your goal. Just promising you'll "eat less" or "sleep more" is too vague — be clear and precise. "I'll be in bed by 10pm on weeknights" leaves no room for doubt about what you need to do, and whether or not you've actually done it.

• Publish 75 blog posts
• Work 3 hours per week on personal coding projects
• Publish 3 apps

• Be able to do 10 dead hang pull-ups
• Be able to do 10 ring dips
• Be able to bench press 155 pounds
• Rx 30 workouts at CrossFit
• Eat paleo food on 275 days

• Do 100 hours of community service
• Eat meals with 25 different groups of people

• On last weekend of each month, spend at least two hours alone somewhere outside and unpopulated. Look over goals and plan the next month.

Wikinews contributors have discovered that members of the United States Congress or members of their staff have recently been making questionable edits to Wikipedia.

[…] In one instance, Wikinews found that someone with one of the IP addresses, 143.231.249.141, began to edit the Wikipedia article for Steve Austria, the Republican representative for Ohio's 7th congressional district.

[…] Another individual, with the IP address 75.187.63.132, also removed the allegations of plagiarism from Austria's article in February. The individual removed what they called "Politically Motivated BS" from the article of Deborah Pryce.

Briefly, you look at a product as the job it was hired to do, rather than its category, features, benefits, who bought it, etc. Christensen makes the argument that jobs are enduring over time (as products and customer segments change).

Applying this insight gives SDK makers a way to target features, not at just the job the SDK does for their developer customer, and not just at what their application does, but also at the job that the end-user is trying to do.

If we were doing jobs research around the Starbucks offering, it would start with something like: "tell me about the moment when you first considered going to Starbucks. Where were you? What were you doing? Who were you with? What time of day was it?" The interview would move through the decision making process (what else did they consider?), the consuming process (being at Starbucks), and the end with "looking back" and understanding their concept of value (what it did for them) upon reflection.

By conducting a number of these interviews, you can begin to see "jobs" emerge.

If you hire social media, especially to promote your business, you will likely have your own reasons, but ask yourself the question, "What problem am I trying to solve?" This will likely get you to the functional element. To peer into your emotional and social why, also ask "what progress am I trying to make?”

1. Pick five categories that I can write about.
2. Brainstorm 10-20 topics in each category. If I can’t think of that many, throw out or alter the category.
3. For categories that don’t pan out, try to find a spin on the topics I generated for it, so that they fit in one of the better categories.
4. Pick a week’s worth of topics and put them in a queue.
5. Each day write the next one, and put another in the bottom of the queue.

• Software Business: This is obvious, since this is what I spend the bulk of every day thinking about
• Programming: I have been programming for a long time, I have some personal projects that I want to open-source, and it also naturally fits into what I know and think about. I intend to get away from the more technical posts that I typically write, and focus on high-level ideas and follow my projects’ progress.
• Programmer’s Job Market: Ever since I became a member of my local Regional Employment Board, I’ve been thinking more about the labor market and how it’s changing for programmers.
• Reviews (books, apps, etc): I read a lot about marketing, business, and other non-fiction topics. I don’t read nearly enough for book reviews to be a category, so I expanded it to apps and other things that I use.
• Riffs: Tweets, Hacker News, other blogs, my own past blogs -- these are all fertile ground for topic ideas. It gives me an opportunity to link to others, and make this blog part of a larger conversation.