exline
The most important requirements is to be passionate about creating software and be able to quickly grasp new technologies. Other requirements include strong knowledge of Javacript, Java, experience with Ruby, SQL, Git. We filled our last position through a previous 'Who is hiring' post with great success and hoping to do it again.
Contact me directly if you are interested, email is in my profile.
When the startup died, I moved into contracting. I was doing quite well contracting and then one of guys who was on our board of advisors needed some development work and that led to me having substantial equity in the company and still working from home.
So the start up was a total failure, but I learned a lot and it lead me to where I am today which is much better than where I started.
I can see the ability to have a score board of some kind where you can share your grades with friends. This could help spread the word a bit.
1) They are interested in coding. This was done on their own time, away from work. This means they actually like to code.
2) A lot of work is done to learn a new language/technology. This often shows desire to learn and the ability to at least hack together something that is new to them. This is important because we will be asking them to come up to speed quickly in our code base.
3) You can look at the code and get a feel for how they code. We are a small team and each developer will have the ability to have a big impact (for good or bad). Getting an idea of how they think, how they solve problems is a huge plus.
I don't think you need to have a lot of code available. Pick your favorite project, or 'best' project and make it available. I see very little downside.
How are you going to attract visitors?
That said, you've already made it this far which is a great firs step. Good luck.
The most important requirements is to be passionate about creating software and be able to quickly grasp new technologies. Other requirements include strong knowledge of Javacript, experience with Ruby, Java, SQL, Git.
Contact me directly if you are interested, email is in my profile.
The most important requirements is to be passionate about creating software and be able to quickly grasp new technologies. Other requirements include strong knowledge of Javacript, experience with Ruby, Java, SQL, Git.
Contact me directly if you are interested, email is in my profile.
Its far better create a product and grow the business. I also like owning the whole business and calling the shots. I'll take a 50% chance at a moderate success over a 1% chance at a huge success.
I'm sure there are other costs some optional, some not. Depending on how lean you want to run you can have a very low overhead.
It also depends on what level of developer you are hiring.
If you price per user, but not everyone at a company needs the product, they will tend to restrict the use of the product to minimize the expense to them. With plans, you still have this, but to a lesser degree I believe.
IM/Voip (Gtalk/Skype) for daily communication Email (Pretty much goes without saying) Skype Screen Share/ GoToMeeting when required to view things together. RedMine for bug/issue tracking
We actually never use video calls, don't see it adding to much. I already know what they look like. When we have major design or planning sessions, we will get together for a face to face meetings, scheduled out in advanced. We also try to get together for lunch/dinner/meeting every month or so.
One thought is that the bigger your customer is, the more they can afford to pay for the service. You don't want to leave to much money on the table. Its pretty normal for people to undercharge for their services. Do you have any feel for if you are going to get more 1-3, 4-10, 11-25 users?
The things I don't like about tiered services, is that there is a big price jump when you move between tiers. Moving from 3 to 4 users in your example doubles the cost to the service. I'd make more gradual tiers rather than big jumps.
Just keep in mind that you don't want to be too focused on what your competition is doing. Its ok to check them out, but focus on your customers. They are the ones that really matter.
I'd focus on a few major markets and work hard to get as many menus up as possible. People are always looking for free advertisements and having their menu online is one form. I'd push that as much as possible. Since this is your full time effort, you may need to spend money on marketing to get the ball rolling. Perhaps enter the menu's yourself (or hire a VA to do it) and then drop the restaurant a note saying that their menu is now online and they can make changes at this website for free.
Other ideas, perhaps white label it to newspapers and/or city websites? In San Diego, there is a dining guide section at signonsandiego.com and this would fit into what they are doing. They also have someone who is doing reviews weekly, which could now include populating the full menu.
Returning paying customers, that is the gold standard.
The value proposition is not very clear. Why would I use your product, what is the benefit of using it. It appears that your business model is to target conferences, is that correct? Will it always be free to everyone else?
One minor issue, on the FAQ page, it says: "A Quirk is a type of QR code, a two-dimensional barcode represented by a pattern of black and white squares (like the one at the top of the page)." But there is no a QR code on the to of the page.
The valuation of each company should also be figured into equation. It really only matters when there is an exit, but it would effect your payout. Have the founders/owners had a successful exit before? Are they going to raise capital, thus diluting your ownership in the future? Given these questions and my past experience, I'd take the job that is more interesting to you. If both are equal, then take the higher salary.
It would be far better to launch now, get some initial users, improve your product based on their feedback and then really turn on the marketing effort. The key thing is to get started now, start getting users. Find out how they use your product, find out what they like or don't like.
I registered for an account, but it didn't not automatically log me in. Not a huge deal, but little things add up. Then after I logged in, it kept me on the login page. You should redirect to the home page.
I like the idea. I think there have a been a number of posts both here at HN and other places basically saying, here is an idea for someone, or someone solve my problem. I would find those and use that to help populate it.
One feature/benefit that would be useful is to find how who liked/wanted the idea. Perhaps there needs to be 2 types of voting. 1 vote is 'that is a cool idea' the second is 'I would buy this now if it existed'. The second feedback is much more valuable than the first.
But I think it is a lot easier now then it was in the past. There are lots of opportunities to work on open source projects. What I look for in student or recent graduate resume is decent list of technical skills (languages, db, methodologies, etc.) These you can pick up at school. The biggest issue for me is to see some code. You can learn a lot about a person by looking over their code. So I'd publish a few of your personal projects. Reference the website where the code and documentation sits on your resume.
I less concerned about buzzwords. They don't tell me anything. They may help you get past a resume screener, but they will not help you beyond that. If you have experience in the area, you should specifically list that.
That said it could in theory be up to 5-10K documents a month in a year from now, but right now it is probably only 100-200 a month. Currently we are using an open source tool and having decent results. Not great, but acceptable so far. The second option is to require their users to provide only PDF, which is not ideal, but also acceptable.
It seems like this is a commodity product, so figure out what the cost is per document (or per gig of data.) Then add in some profit and that is your price. You can have larger profit on smaller plans and less profit on the larger plans. To do this, I would charge by data not document, since you can determine costs by data, not document.
If you are self employed or work at a small company, then insurance is a big deal. I'm going to pay $6K a year for crappy insurance and I'm still going to pay $7k out of pocket expensive this year because my son had to have surgery and our deductible is 7500. So I think the insurance situation sucks. And I got a notice yesterday that they are raising my rates again. For small business that want to cover the health insurance for their employees it is also a big expense and one that keeps rising. It amazes me that insurance companies can raise rates 15-40% a year and get away with it.
As far as saving up for college education, that is not as difficult because it is a matter of living within your means. Make it a priority and save. That said I have different views on fully paying for 4 years of college vs. having my kids pay part of their way. My parents put me through my first year of school and then I was on my own. I tended to work hard at school (to get it finished) than those I know who's parents were footing the bill.
I also got a lot of help from business communities online. Listening and learning from others that have been successful.
The single biggest factor was getting paying customers. This validates your product/service, and gives you a huge boost of energy and confidence. This is one reason to cut back requirements and get your MVP out the door as soon as possible. Also if you are stuck (or in a rut technically) pick something on the fringe of your project that is small and that you can quickly do. Making progress helps ease the frustration.
I think that you are going to get very different %'s based on the type of app. I have a SaaS so it's different, but for what its worth, my conversion rate from trial users to paying users (which are my active users) is less than 5%.
I'm curious what your business model is. I'm in your target market since I use google reader.