"If I’d played around with every piece of technology I should be using whether I felt like it or not, I’d never have got anywhere."
I feel like this all the time. Sometimes it's better to do a less-great job in a language you know backwards and skip the learning curve of a new tech.
The site works really well btw: after entering a handful of my favs it took my a while to get through all the games I already like to find new ones - so it's doing something right :)
Great, I'm glad to hear it's proving useful! I'll do a follow up with how well my NoDB implementation stood up to the pounding it's getting at the moment later in the week...
I actually LOL'd when I read that. Which is kind of embarrassing since it's really quiet in the office today :-)
Great post. I get analysis paralysis all the time when I think of new web apps. The idea that I won't have the perfectly scalable architecture (horizontally AND vertically) with all the cool infrastructure is enough to overwhelm.
That's because I also skip to the scenario of "What if my app gets real popular and then starts crashing all the time, and then everyone stops visiting while I try to learn how to set up nginx with memcached and ... ad nauseam."
Sometimes it gets me stuck and sometimes I remember to take baby steps like you wrote about.
Yeah, #players and playingtime are both on my list of things to optionally filter. Just need to find a nice way to do it without complicating the initial user experience.
I feel like this all the time. Sometimes it's better to do a less-great job in a language you know backwards and skip the learning curve of a new tech.
The site works really well btw: after entering a handful of my favs it took my a while to get through all the games I already like to find new ones - so it's doing something right :)
Thanks for the interesting read.