Great Example
Great example on what not to do.
I found myself stuck on this when creating a firebase auth account. Im sure you get stuck here too.
This question was asked, what would you like to Project public-facing name to be? Please enter a project name:
Mind you it also says, that whatever you choose will be shown publicly. Like when you signup to MailChimp and they send you an Authentication Email to verifiy accounts. But what if this project is to act as part of my portfolio. What then? Firebase or your momma cant help you here.
So I spent 22min staring at this 1 problem like a deer stuck looking at a cars headlights.
So many questions arised instantly after:
What if I wanted to change it?
How hard would it be to switch or rename?
Is it really this important to have a good name?
Why is this so hard?!
LMAO
It isnt.
I realized that my end goal is to complete a sustainable MVP, good enough to show the neccessary skillz needed for recuiters and potential clients to see. So does it REALLY matter if its JUST a portfolio product demo?
Then this happens:
Thats right! I made a break through.
Why not call it portfolio-product-demo or better yet Portfolio Product Demo
Even better why not K.I.S.S. ( Keep It Super Simple )
So I decided on JasonCruz.Dev Sign-Up Confirmation
I know what your thinking..
Could it have been that easy!? YES! It could have.. But since this is my first real use-case application on Firebase, you can imagine how stuck someone can get when anything new appears.
FYI: When writing this blog post, I literally didnt have a friggin clue what to name it. But I persisted. As I start blogging this post for the purpose of helping others decide and figure out what not to do and in the mist of it all, discovered what name I will be using.
Thanks Dev.To for your continue support! One day when I become big and strong, I'll be making a blog app for my own blogs and others! Plus I already have an idea on what it will look like! I can not wait!
So heres to you newbie developers! Cheers!
Top comments (0)