medinism

They did.there is a paraprog guide to raspberry pi. Came out this week

this article was super valuable to me. clearly not in depth enough to convince a believer to change allegiances, but good enough for the uninitiated.

Is anyone at all surprised their tech-stack is php? is it because of legacy or is it because any sensible person moving petabytes of data would use? or does it even matter

Hopefully this is adding value to those who are calling in. It looks a little self serving Exec marketing stunt. But, good on them!

Danso - agreed. this is a gem! will make me think of how I use adjectives for ever

I agree. you can get around the skeleton crew issue by asking everyone to be at hand, nearby in case shit hits the fan. no biggie if all take turns manning the update.

SEEKING FREELANCER -San Francisco/New York/Boston remote ok as long as it is within the US

Project: HTML5 consumer app for Flash-sale site. Needs to be able to render in a number of devices, phone, PC and tablet.

Project is posted on GroupTalent: a hacker-centric marketplace for high-end development and design freelance projects. more info at [email protected], or sign up to get access to projects.

Good point. the way I was thinking about it was more like this 1- you provide an overall estimate on where you think you could come in at. you do this to give all clarity on how you are thinking about the problem, anchors your estimate and the functionality you are about to build, and allows the owner to get a sense of price 2- only commit to a week or 2 at the time. this allows the client to tweak things, see quick progress, and add or subtract features as you make progress. Or even stop, test features on customers - and pause.

thoughts?

I agree giving the project owner the appearance of certainty will make him feel safe and comfortable - however it is not good for them. The longer and more complicated the project the more likely your estimate will be wrong. So giving the customer a sense of overall effort is good - misleading them by telling them you know how much the overall project will cost is bad.

Below a few nuggets from what we have observed at GroupTalent: 1- Hire a freelancer based on work performed not on CV. Not only we do this by allowing our teams or single devs creating portfolios (which is privileged information displayed only to interested employers) but also by asking them to show us the code or design they are most proud of. 2- Have them come up with an overall plan for the project but commit to only the first sprint. Creating the overall plan for any project will allow you to see how the dev thinks about solving the problem while paying only for the first sprint will limit your risk and allows you to see a bit of his work at the time. 3- Limit the sprints to 1 week at most - and make sure at least a feature is developed in the sprint. Short sprints will help you a- prevent cost overruns, b- cap your risk of working with a bad apple and c- allow you to see features developed early on. 4- Try to manage the whole thing through github. Great programmers hate to add additional layers of estimation, communication, tracking, etc. yet you as a project owner need insight into the work. Make sure you agree to some schedule of commits with the dev so that you get to see progress along the way.

Feel free to ping us at grouptalent.com if any additional questions. otherwise - happy building!

starting your day in a creative mindset does frame your day in a different way. Not sure this is panacea, but optimizing for production rather than consumption seems like the right framework. dying to try it!

I disagree. Investment is a two way street. Angels benefit from deal flow as well so making themselves unavailable does seem odd. If they want to invest in early stage ventures but don't have the time there are plenty of other vehicles to put their money in without being bothered

I feel some of this discussion misses the point. To date the best predictor of the future is the past. And the best way to measure the past is by reviewing work done - not a self-declared history of yourself. If Github does not get you there, then creating some kind of show and tell for anyone to review is necessary. The other stuff you would assumed you can get out of a CV, ie cultural fit, etc you can only assess by meeting the person and working with him/her for a while. At the end of day Github is the best catch all for "show your work" for programmers

I actually find it entertaining and fun - specially the bits about history, how they found common vision etc. It was an interesting human take to subject that could be inherently jargon-laden and boring