90 karma · joined September 28, 2010
This goes inline with working out, but it's certainly harder to convince yourself to do 45 minutes of strenuous workout vs a nice long walk with your best friend(s). I figure, even if I'm sick, tired, and my body aches, I can always walk miles.
And sure, pretty much all of these components can be provided by third-party, but if you did that, then your goods and customer service need to be amazing to make up for the technology costs.
As much as I don't like to drink the 37Signals juice, they have a strong belief and commitment to their business. This is a lot different than being an employee where you should always be moving around every few years (unless you have a piece of the pie). However, if you're the owner, be proud of what you're building and who you're building it for.*
* Could be for investors, but hopefully it's yourself.
In the movie, his life was pretty depressing to see. Much like other child prodigies who have a great beginning, years down the road you're wondering what ever happened to them.
His awkwardness and ignorance had to have a great affect. I imagine a lot of it came from not having a father figure (or guidance in general) and becoming entirely consumed by chess at such a young age. He really closed himself off in his own world.
Oh, and Crate is already profitable. No worries about losing your stuff because the business tanks.
That's helpful, but not a guarantee.The site seems a little too bare to trust with my credit card, though the free version sounds really great. It seems like it's missing something. Like a weekend project that still has some details to flesh out.
Reads just like a bad movie script.
Bookmarking client side for me is > web based because of speed.
The #1 person to hire after the founder is the developer. I hear this all the time. So why would you not give them a voice on the business side? Or perhaps they had it in the beginning, but as the company grew too many layers were added. Developers are the problem solvers of the business.
A user will always be a user. One business may need 12 projects while another may only have 1 project everyone is working on. But if both have 30 users they use up the same amount of bandwidth.
And as you suggested, it really comes down to how different businesses work. Some companies work faster than others where 1 project may last 2-3 days. Someone in that company would have to be on top of closing that project and the next one. Or do they create a Generic project for the quick ones and a specific project for the more long term ones?
Properly utilizing Projects (and milestones for that matter) have always been a challenge for me with the project management applications I've used (Basecamp, FogBugz, etc).
Maybe add a Team layer to the mix. A user can belong to multiple teams. You can have a Dev team and an IT team. Then an overall Tech team which includes everyone in Dev and IT. Then update the dashboard to allow you to view by Team or Project.
You'd have to work out a good way of explaining/displaying this to users.
Additionally, it'd be great to see the last 2 updates underneath each person. Or maybe on the team view list all updates under each person for the same day (otherwise show last 3).
This it personal preference, but adding different views to the dashboard would be pretty simple and would help sell me on this for my use.
Lastly, I don't know how well the pricing model works by limiting to a certain number of projects. To me, users is a more important grouping and I would do pricing based on that.