Michel belleville
Practical Tips for Hiring Ruby Web Developers. The topic of 'hiring' always generates a lot of discussion. And why not? Talking about hiring is a convenient way to pass judgment on large groups of people while keeping a professional, detached demeanor.. Ouch! But the topic has enough technical basis to warrant the interest of experienced developers, so here we are. This post is for those who handle the technical evaluation necessary to hire candidates, especially in the Ruby and Rails scenes, although the overall strategies are language-agnostic (though I'd hope if you're hiring folks to work on missiles and nuclear power plants, all bets are off).
This is a guest post by Tim Goh of Trikeapps, an Australian software development company. Some Structure While hiring processes differ, I'm organizing my advice by the following components that, assumedly, most processes include: the job posting itselfthe coding testthe phone screen The Job Posting You need a permanent "Careers" page Include a filter question A Philosophical Interlude Conclusion.
CoffeeScript. Sass - Syntactically Awesome Stylesheets. #haml. How to Start a Startup. March 2005 (This essay is derived from a talk at the Harvard Computer Society.) You need three things to create a successful startup: to start with good people, to make something customers actually want, and to spend as little money as possible. Most startups that fail do it because they fail at one of these. A startup that does all three will probably succeed.
And that's kind of exciting, when you think about it, because all three are doable. Hard, but doable. If there is one message I'd like to get across about startups, that's it. The Idea In particular, you don't need a brilliant idea to start a startup around. Google's plan, for example, was simply to create a search site that didn't suck. There are plenty of other areas that are just as backward as search was before Google.
For example, dating sites currently suck far worse than search did before Google. An idea for a startup, however, is only a beginning. What matters is not ideas, but the people who have them. People Raising Money. Hacker News | Founders who can't code. An advise to founders who can't code If you are a business/idea guy and looking for a technical co founder, stop. Stop right now. Take 6 months off and go learn how to code (day and night, weekends including). Most web apps do little besides save, show and update data. No, You will NOT become an engineer, programmer, or web developer, but you will be able to put a prototype of your idea together and maybe get one or two beta users for feedback. At this moment it will be much easier to recruit a technical cofounder. The reason why most technical cofounders can create great products is not because they have a deep domain knowledge or they are great hackers.
Here is the thing, 1 year from now, you will still have plenty ideas. Stop and go learn. Note 1: If your idea is to build something truly technically challenging, then scratch my advice. Note 2: Off course all the above would mean little if I wasn't the marketer/business/idea/support/whatever guy who spent the past few months learning.
Help. Abeauvois.