carpal
One incident, in particular, drove most of the hatred for my original (and now replaced) rant. It involved an M.B.A. recruiting me to work for “his idea”, promising a bunch of money and a sizable stake in equity (~35%). However, once the boss-employee relationship set in, the money evaporated and the equity shrank to 5%. In the end, I wasted 6 weeks of incredibly hard work and came away with a chip on my shoulder.
The argument doesn’t really have much to do with Hackers and Business types. As he points out, it simply has to do with the fact that in a small group of people (2 or 3), there is no room for pure leaders. At that group size they merely become bullies, and the whole group is less powerful because of it.
I've temporarily replaced the rant with my more complete and restrained thoughts on the subject.
In Atlanta's, the actual startup was an C-corp owned in part by Startup Weekend, LLC, in part by Atlanta Startup Weekend LLC, and the rest by the "core team" that existed after the weekend. People who participated in the weekend were given shares in Atlanta Startup Weekend, LLC, and not the C-corp. I think this was done to avoid any complications with the SEC, since LLCs are governed far less strictly.
http://subwindow.com/articles/12
It turns out that Apple is a totally perfect example.
1) Apple was a hardware startup. Hardware startups need funding and someone to aggressively sell the product in person to big vendors. Software startups don't usually need that kind of person (unless they're going after the Enterprise cookie).
2) It was in the 70's, and startups were, in general, harder to start than they are now.
However, 99% of the time they don't have funding, they've (at best) got "strong interest from investors" or some such.
I have no problem with homeless people in shelters. But when they're out in the street making people's lives miserable, you have to do something. A robot isn't the best solution, but when the city won't do anything, it might suffice.
If you want to learn skills, work at the small company.
Personally, I'd love to have a robotic centaur helping me around the house.
Who's to say a quadruped robot can't have 4 feet + 1 or 2 grapsing mechanisms? Or have two front feet that are also capable of grasping?
1) Height 2) Use of spare limbs for tools
Height doesn't seem to be much of an advantage for robots at this stage, and I think that robots could have 6 limbs with no problem. Therefore, biped robots are really only a novelty.
Its free, and has worked very well for me over the past year.
(sorry for the late response)
Elaborate?
Looking for someone who can kick ass and take names. A Rails developer would be great, but I'm also looking for someone who has business chops and a good understanding of accounting principles.
If you're worried about the MySQL license, you should try PostgreSQL. I've been using it for three years and have had nothing but extremely positive results. Version 8.3 is stupidly fast.
2) For a startup, small businesses might actually be better. They might still be able to spend a decent chunk of change (.25-1M) on an ERP system, but have much lower requirements making an easier implementation that is less likely to fail.
3) ERPs aren't really modular, that is true. I'm not sure there is a win to a real "modular" ERP system. The who idea behind an ERP is that everything in a business is connected, so the systems should be connected too. Sales people are connected to orders are connected to finished goods are connected to build processes are connected to inventory are connected to purchase orders. Removing one "module" in that chain defeats the purpose of the ERP.
It is currently being done with only one developer. We're 6 months into the implementation, and are piloting in several of the modules. It is going pretty well so far.
If it continues to go well, we're considering spinning it out into its own company. A well-designed and user-friendly ERP system is a killer asset to have, and being able to resell it is an even bigger one.
I've come to pretty much the same conclusion as you, about customizing. I figured we'd have a "standard" set of modules, which would either be completely replaced or slightly modified as necessary to fit the client company. Certain things like maintenance, receiving, purchase orders and sales teams probably don't vary much between companies. Other things like manufacturing routers and change orders probably do. This would allow us to be flexible where it is necessary, and to reuse code where it is not.
As a side note, we're hiring another developer to work on this system. IC to start. Let me know if you're interested.