Just had a Richard Hendricks spaces vs tabs moment
I built my database with each table generating a unique id using a "-" delimiter and then, upon implementing GetStream (Feed Management), realized that this unique id is ideal for passing hashtags in posts; only to realize that a hashtag can't include "-" character. So I just restructured everything using a "_" instead of the "-" character.
Yeah, I know, no big deal because the id not the actual hashtag and I could substitute other characters before passing the API call. But, as I'm creating a new solution indie style, I want to avoid choices that limit my options down the line. If "-" delimiters won't work in this situation then maybe they won't work in another situation either. So, in an instant, I become an "_" guy just like Richard Hendricks is a tab guy.
As an independent entrepreneur, we have to wear every hat and be an expert at every discipline (e.g. engineering, sales, marketing, design, etc.). But, in reality, we learn along the way and develop best practices as we go.
So what best practices have you learned the hard way?
This comment was deleted 8 years ago
But lets be honest tabs is always the wrong decision.
They did invest in a whole team to build a new php VM because they found it was limiting then developed a new language to replace PHP. The choice ultimately didn't stop them because they had enough money to afford the extra servers and programmers doing the above. But that is not to say that it didn't matter or have a negative impact on the business. Just that they were still able to be successful despite the issues.
That is unless you're all about compression then tabs probably are better than spaces. ;)