4 ms·
I'll just offer some counterpoint, as we didn't do this. We created accounts manually with a script for a long time. By the time we needed a panel (leads were
by wheels 17y ago
I'll just offer some counterpoint, as we didn't do this. We created accounts manually with a script for a long time. By the time we needed a panel (leads were starting to get out of hand), I knocked out a fugly one in Rails in one 20 hour coding marathon. Then I banged up an email parser in Perl to add all of our current accounts / correspondences. That was just a couple months back.
The biggest problem that I could see with building a panel up front is that you might be building it for the wrong product. In my eyes, testing your product to see if you get any traction would probably win.
- gyardley 17y agoDitto. When we needed to do a little admin, we just modified the database. (A little risky, I suppose, but we were doing regular backups.) We only wrote administrative tools when things got too complicated for the least-technically-sophisticated member of the team - me - to easily tweak things. As it turned out, some of the most common customer support issues we had weren't anticipated by us in advance, so building out an admin panel would've still only met part of our needs.
- MicahWedemeyer 17y agoYeah, the last line in the post is wrong, IMO: Make sure you build a real metrics dashboard and implement a real logger before you launch. Just launch it, then figure out how to instrument and admin it. Yeah, it will be painful, but at least you'll have some idea what you're trying to accomplish.