So we have decided to take the Whiskey Developer Podcast (The Speakeasy) in a new direction. In the upcoming podcasts (and related blog posts) we'll be talking more about code and the tools and tricks we're using to help us build our sites. Along with each podcast, we'll be publishing code snippets and examples to help listeners follow along and hopefully use/discuss the code we're releasing. The goal being, to give the community a deeper understanding of the technology we use to build our sites and to help budding developers grow
DEVELOPER PODCAST: How Do We Set Up Our Sites
So we have decided to take the Whiskey Developer Podcast (The Speakeasy) in a new direction. In the upcoming podcasts (and related blog posts) we'll be talking more about code and the tools and tricks we're using to help us build our sites. Along with each podcast, we'll be publishing code snippets and examples to help listeners follow along and hopefully use/discuss the code we're releasing. The goal being, to give the community a deeper understanding of the technology we use to build our sites and to help budding developers grow
Hey buddy, pretty cool podcast! Maybe you taking notes on the Giant Bombcast has been paying off? Hahah.
Glad you guys are pissed off with Django's lack of a migration framework. I can't tell you how much that annoys me, and the fact that they're not even thinking about implementing one frustrates me even more. Hopefully we'll hear about something when 1.1 is finally behind us.
"Will that achievement thing work with trophies for PS3? "Nay. They said on the GiantBomb podcast no - purely because Sony haven't made the tools available to make it possible.
However, Dave confirmed that the moment Sony sort out that side of trophies (which you have to assume they are working on) - then it will be implemented.
"Ahh, so it was PIL that you used after all. I love PIL and quite a lot of the programs I make use it in one way or another. You guys mention Ruby on Rails... why didn't you choose it instead of Django?"We went back and forth between whether or not we were going to build our framework (and the sites) in Rails or Django (we actually tossed around the idea of building our own web framework in PHP, since we were all familiar with it) - and we eventually decided that Django was the way we wanted to go. Andy knew Python and really liked coding in it - we just followed his lead.... and I must say that I personally love it. Python is such a powerful language and Django is an awesome web framework. It does a lot of the heavy lifting for you (as does Rails), and it does a great job of keeping your projects organized and maintainable.
"Glad you guys are pissed off with Django's lack of a migration framework. I can't tell you how much that annoys me, and the fact that they're not even thinking about implementing one frustrates me even more. Hopefully we'll hear about something when 1.1 is finally behind us.We're still trying to figure out what we're going to discuss on the next podcast (as well as the direction we want to take it) - but I'm sure Andy would have no problem talking about how we encode and push videos on our sites. Short answer: We try to automate as much of the encoding process as we can. Yes, we use s3 to host them. And yes, it is damn expensive.... its not nearly as expensive as using Akamai or some other storage and delivery service, but we do get a large bill at the end of every month.Could you guys talk about your video encoding process? Do you transcode on a server? Is it done by hand? Is all media on S3? Does S3 kill your budget with +1 million pages view?"
Thanks for the answer. I really like the "more technical" direction the podcast is taking, and love the code examples, too. I was wondering about the database model for your sites, as I think I will have to imitate it somewhat for one of my programs (that uses both the API and web scraping for things I can't get through the API), but using sqlalchemy. Maybe in the summer I can actually work on that part. ^_^;
New sites are mentioned... and I was thinking: aren't you guys afraid of "spreading yourselves too thin"? How much more "attention" is needed from you guys when a new site comes up (I mean after the initial launch phase)? The code base is the same, but each site has its differences that may require bug fixing from time to time, and new major features may be needed (such as the Achievements, I guess) than don't work well (or at all) on multiple sites. The "editorial staff" will handle the content side, I guess, but the editorial staff is small, too, so things like deleting wiki pages (that only the staff can make) take a long time (it is really bad at AV). Are delegating these kind of things to mods being considered or is this the editorial staff's decision to make?
I don't know how in the world I didn't notice this when it came out, but I'm downloading the two podcasts right now...this should be good.
Also, since this happened quite a bit ago, I guess Sean nipped it in the bud. Thats too bad, info on what goes on behind the doors of my favorite website is always a plus.
Wow, I've never heard these. I've never used python or any of those languages. It would be interesting to hear more. COONCE!
Should be interesting for a beginner programmer like myself. Also, I know this probably isn't the right place to ask but have you guys checked out the bug reporting forums? There's lots of stuff that needs fixing...
" I don't know how in the world I didn't notice this when it came out, but I'm downloading the two podcasts right now...this should be good. Also, since this happened quite a bit ago, I guess Sean nipped it in the bud. Thats too bad, info on what goes on behind the doors of my favorite website is always a plus. "yeah man, why the hell wasn't this more noticed, I am listening to it now,
Cheers guys, It would be cool if you could talk about your ideas behind screened and tested,
actually, I have no idea what you guys are talking about, but there are big words, it sounds interesting, so, yeah, i'm going to go with cool, and interesting but waaaaay over my head.
thanks anyway. awesome.
" @coonce: Thanks for these anyway. :) How much has the general site structure changed since you put this up? "it has and it hasn't. we're always tweaking performance/fixing bugs/adding new features/etc...... but the overall architecture and framework has been consistent since we built comicvine.
Please Log In to post.
Log in to comment