I honestly don't know perhaps instinct. I see a need and I feel that if I set out to solve that need, people would want it. Who knows, but I need to believe that what I am doing is going to work. I will validate it soon with an MVP and we will revisit this question again when that time comes. I hope you and I can have that discussion again then.
Soon enough, my friend. I'll be back in another month. I'm going commando (the Vietcong style, not the nude style of course) for the next month hopefully. When that time comes, I would love to get your support.
Once again, thank you for your kind words and encouragements.
I think the word "ever" denotes too much absolution. Sure, never say never (arrgh! Beiber); Obama definitely isn't a hacker in software, but he definitely hacked the ways presidential campaign are done for a long time. Now that I think about it, most elected officials ARE Hacker in some way as they have:
1) build a product (their image)
2) build a product (themselves)
3) deal with competitors
4) innovate with new messages
5) change the ways certain things are done
etc.
Also, might be elected, but probably never "electerd" :)
What kind of programming languages/stack are you more familiar with? Usually, Wordpress should really fit all your blogging needs. It's easy and has a lot of SEO tools to go with it.
But as I am not at all comfortable with Wordpress' issues that surfaced a while back: upgrade, security etc., so I plan to use one of the Django blog platform. But that means I'm not blogging at all, but worrying more about how to have the blog installed.
There seems to always be a trade off. But one thing is for sure, you should choose to install Wordpress or any chosen bloggin platform on your domain rather than having it redirect to another domain... like blogger, wordpress.com etc.
I actually have this debate with myself every time I think that I am close to the point of deploying my work (heh, that's another story). But every time I do the calculation, I just don't get how AWS would be more beneficial to me vs sticking with Linode. AWS' pricing would be much more than Linode's model. So for a while, I think I am set on this resolve:
Using Linode for my app and host static files on S3 and maybe another cloud provider like Rackspace for failover in case the clouds go down.
I am hoping that I would have a luxury problem once my app is doing well. When I have that kind of traction, it's a different story. But until then, it's more logical to stick with a VPS.
By the way, are you making updates to your production site frequently? Your carousel isn't working correctly yet.
I know you use django (from another post I think). Have you thought about using social network login? I used django-allauth and it has been working very well for me. Good luck!
We push to production 3-4 times a day.
You mean the carrousel on the home page ? I'll take a look. That page hasn't really been touched since we started developing and needs a complete makeover. Thanks for the heads up !
We currently our own LinkedIn login to create account as we use their API to match candidates and jobs. Next step is to add Facebook and Twitter as alternative login.
Thank you for sharing. I really appreciate your story. Reading it reminds me a lot about some of the "wild" decisions I've made along the way.
I was also my family's black sheep. My story is different I suppose (briefly): I left full time scholarship to study arts--I went to Florida with $500 my brother lent me. I didn't have money for food so I ate Starbuck's left over pastries for the first 2 weeks. I ended up taking 6 courses that first semester and worked 2 jobs to support myself. It was tough time but it was the most lucid time in my life.
While I did well at the arts school, I didn't end up doing arts after all. I am a web developer now--happy hacking my after-hours projects and chasing dreams. Taking good care of my family is also one of my dreams!
I usually think to myself, people should have ambitions and dreams. But only a real man/woman is willing to lay his/her life down for those dreams.
Same with me here. I switched from using CakePHP to Django and haven't touched any PHP since. I would highly recommend Django.
With that being said, I think while development without a framework "might" feel more lightweight, you will pay for it later when you're maintaining your app. As they always say, you build it once but you have to maintain it forever. I think investing in a framework will most likely pay off in the future even if there is an overhead usually associated with framework.
