3 ms·

I'd go with 1) what works for you, 2) at that time, 3) with an eye toward future expansion. What #3 means is if you go with a simple solution per #1, make sure

I'd go with 1) what works for you, 2) at that time, 3) with an eye toward future expansion. What #3 means is if you go with a simple solution per #1, make sure you can migrate your data. For example, I've seen many companies grow from using Excel to Access to SQL Server. This path seems quite natural, and despite the issues associated with Access databases designed by non-DBAs (ahem), the process generally works (with the assistance of those of us who get paid to help). Company B's problem is they don't realize they've outgrown their system, and need to evolve to the next step. However, I think their solution (spreadsheets) should work perfectly fine for your two-man shop. I duplicate this lifecycle in my own personal projects. I might start off tracking fitness in vim, and decide I want sums so I migrate to Calc, etc. I recommend using simple tools, well. Do you think if you try to adopt a larger package before you're ready you might end up spending most of your time playing with the system instead of working (like a writer who procrastinates writing)?

wheels 19y ago
I think it's more like having a first kid. We know we've got 3-6 months before it starts breathing and there's a tendency to over-prepare because We Want Everything To Be Right. We're still not to the point of no-return (haven't quit our jobs yet), but I'm trying to learn everything possible and have everything in place so that when and if that happens we can give it our best shot. #3 is something I'd really thought about, and is probably pretty in sync with what should in fact happen. There unfortunately don't seem to be a lot of smooth migration paths out there, which is what I think tempted me to start looking at some of the more comprehensive systems. There's some overly systematic twitch in me that says, "Get this figured out now, or it's going to bite you in the ass later." But in reality, going with the analogy above, that's probably like planning for a kids teenage years before they're born.

wheels 19y ago

I think it's more like having a first kid. We know we've got 3-6 months before it starts breathing and there's a tendency to over-prepare because We Want Everything To Be Right. We're still not to the point of no-return (haven't quit our jobs yet), but I'm trying to learn everything possible and have everything in place so that when and if that happens we can give it our best shot. #3 is something I'd really thought about, and is probably pretty in sync with what should in fact happen. There unfortunately don't seem to be a lot of smooth migration paths out there, which is what I think tempted me to start looking at some of the more comprehensive systems. There's some overly systematic twitch in me that says, "Get this figured out now, or it's going to bite you in the ass later." But in reality, going with the analogy above, that's probably like planning for a kids teenage years before they're born.