Reply to thread

Message

<blockquote data-quote="Jon L" data-source="post: 921776" data-attributes="member: 33844">eliquid beat me to it with the 'no one cares about your stack' point.&nbsp; I'll add this, though: each project doesn't care about another project's stack. Most of the apps my company builds for clients are very low volume: tens or hundreds of users at a company.&nbsp; A recent client is still pretty low volume, but with him, we have to think about things a little differently.&nbsp; A few hundred thousand records per day in a database still isn't a lot, but it can add up and make some things unwieldy if you don't plan for it.&nbsp; Another client from this last summer was completely different from anything we'd done in some respects.&nbsp; Usually, we do all the processing on our side - just to make things nice for our client and users.&nbsp; In this case, though, I'd joke with him that my job was to do as little as possible.&nbsp; And he loved the idea.&nbsp; (It meant that he wouldn't have to hire us to make changes every time he sold this application to a new customer.)So ... pick a project, go build it, learn and do it again.&nbsp; If you're building a company, though, you'll probably want to stop writing code at some point and run the company.</blockquote>

[QUOTE="Jon L, post: 921776, member: 33844"] eliquid beat me to it with the 'no one cares about your stack' point. I'll add this, though: each project doesn't care about another project's stack. Most of the apps my company builds for clients are very low volume: tens or hundreds of users at a company. A recent client is still pretty low volume, but with him, we have to think about things a little differently. A few hundred thousand records per day in a database still isn't a lot, but it can add up and make some things unwieldy if you don't plan for it. Another client from this last summer was completely different from anything we'd done in some respects. Usually, we do all the processing on our side - just to make things nice for our client and users. In this case, though, I'd joke with him that my job was to do as little as possible. And he loved the idea. (It meant that he wouldn't have to hire us to make changes every time he sold this application to a new customer.) So ... pick a project, go build it, learn and do it again. If you're building a company, though, you'll probably want to stop writing code at some point and run the company. [/QUOTE]

Verification

Reply to thread

Connect With Fastlane

Fastlane Toolbox

Join A Movement

GRAB THE DAILY DIGEST