distributed-work   4

Understanding the Git Workflow
"Think of branches in two categories: public and private.

Public branches are the authoritative history of the project. In a public branch, every commit should be succinct, atomic, and have a well documented commit message. It should be as linear as possible. It should be immutable. Public branches include Master and release branches.

A private branch is for yourself. It’s your scratch paper while working out a problem.

It’s safest to keep private branches local. If you do need to push one, maybe to synchronize your work and home computers, tell your teammates that the branch you pushed is private so they don’t base work off of it."
git  project-management  distributed-work  version-control  advice  design-patterns 
august 2011 by Vaguery
Microtask
We feed paper documents into IT systems. Our service understands handwriting and ambiguous data. It works by combining computers with distributed human intelligence.
crowdsourcing  outsourcing  distributed-work  technology-company  tools  entrepreneurship  startup  social  web2.0  business  company  services  work  freelance  inspiration  cloud  data  distributed  future  automation  jobs  from delicious
may 2011 by guttertec
Microtask
A crowdsourcing startup, Microtask, is ripping crowdsourced labor into even smaller pieces. Microtask's automated platform splits dull, repetitive tasks into tiny pieces and distributes them over the Internet.
crowdsourcing  outsourcing  distributed-work  technology-company  tools  entrepreneurship  startup  social  web2.0  business  company  services  work  inspiration  freelance  cloud  data  distributed  automation  future  jobs  from delicious
may 2011 by guttertec

Copy this bookmark:



description:


tags: