Definitely a lot quicker.
1,208 karma · joined December 5, 2007
Definitely a lot quicker.
For me, it is more about the convenience of not having to shutdown IIS, Apache, Nginx, etc. every time the host operating system boots.
Further, since I am using a Windows host machine for most of my development, it is impossible to fully replicate the server setup on that OS - hence the virtualisation.
I hoped that the point of the article would be that once those relationships have been made, the funding itself can be (but isn't always) straightforward.
It would be interesting to hear others' stories on this point, if you want to share them?
Take a look at this Wiki article: http://en.wikipedia.org/wiki/H-alpha#Filter
Folks already pay for hosting now - so why not charge them for all the added value you provide? This will scale in proportion to your infrastructure demands.
I'm paying $20/month for a VPS slice that runs my blog. I'm sure there are plenty of people who'd be willing to pay at that price point for all of the added value that Djangy will provide, on top of hosting. There's no need to take my word for it though as this could be validated/tested quite easily.
The actual launch was flawless, however. Only 9 minutes to orbit - incredible that it was done on such a small budget compared to your average government mission.
However, I think it would be prudent to add your suggestions to the article and warn users who go and visit it now. I'll make those changes this evening.
I don't think I mentioned in the article to ask for their friends' email addresses though, did I? I'll have a re-read.
At the time, I seem to recall that we very specifically mentioned to our users that they would gain their high score ratings (over time) AND they would be notified of PopJam's launch, via email.
I'm very much a "white hat" guy - so if there's anything you think in there that may be considered grey/black, let me know and I'll remove it from the article. I'm all for best practices.
Although, I have two questions which HN may be able to answer for me:
1) What are the benefits of the Kinect over building a servo-driven IR bar with audio yourself out of cheap commodity hardware? Is the price far less when all components are integrated? Is the construction just that much simpler?
2) Presumably now that the "easier" task of reverse engineering the comms protocol has been achieved, the next step is to understand/replicate/replace the "proprietary" algorithms in use by Microsoft that run in the XBox in order to have some meaningful interaction with the device. Is it possible to use some FOSS such as OpenCV with Kinect? I know it's early days and many of you probably haven't had time to look at the protocol yet, but I am curious.
Given that you're a physics PhD, I'd love to hear your thoughts on how the post could be improved. I'm keen to expand it and "fill in the gaps" that others have suggested.
As it happens, Physics is not my main discipline. I did Maths, then Aero (CFD). I did get by with enough Cosmology/Quantum Mechanics at undergrad to be able to pick up some advanced undergrad/grad level texts however.
I can certainly agree that some of the more obscure aspects of compressible flow solvers would have been very difficult to grasp, if I hadn't been able to question my supervisor on the topic.
I visited the MadEvent/MadGraph wiki. I can see it is related to particle physics and symmetry models, but what does it do, out of interest?
Also, it depends on how much you really want to understand. If you want to be at the level of taking exam papers in all the material, then you would need to study a lot. If you just want a broad (but mathematical) introduction to the topics, you can go much faster.
To make things ultra-exciting, you can try and generate computer experiments around the material you're reading. Build a differential equation solver, use some Python libraries to visualise a pendulum swing, etc. It really makes it come alive and gives you a far better understanding of what is really happening.
I also agree that those two lists are excellent - thank you for bringing them to my attention.
One important aspect I have neglected is Statistical Mechanics. I'm not familiar with that area, being more of an applied maths guy.
Carroll's book looks interesting. I'll add it to the Amazon wishlist!
I did put some free resources at the bottom of the article, although admittedly I could have added more. If you look at the link in the first comment there are some great lectures in there.
Leonard Susskind's Stanford Modern Physics lectures are fantastic. If you search on YouTube for Stanford/Susskind/General Relativity etc, you should be able to dig them out.
This always confused me, as the fourth year of many undergrad MSc courses are rather tough. They are usually preceded by a third year with some 400 level prerequisites (also tough!). This is not the case for a 3 year BSc where students are generally taking whatever courses are available to bump up their grades.
I know a guy who has a dual processor Xeon machine, each with 4 cores, running MatLab. Once the code was parallelised it zipped along.
I don't agree with this mentality at all. In fact, I make use of Python almost exclusively for the work I do (in a small fund). My NumPy/SciPy is not good enough though to choose it over C++ when I need to perform some hefty number crunching.
How did you find using SAS/SPS? Is R not a good candidate for what you're doing?
In regards to the HN crowd, perhaps an article on how to use C++ for quant models may be more appropriate? How many of us on HN are interested/practicing financial analysts?
If you have any more suggestions (particularly about navigation improvement!) I'd be keen to hear them. I want to make the site as useful as possible.
I'm not going to pretend I know much about the implications of storing huge binary files in SVN, but at least they were in VC.
The main benefit to me of this was not backup (although that was highly useful!) but in the fact that I could write it up in the Uni office, at home or on my laptop on holiday. Just don't forget to SVN commit every now and then :-)
My real goal is for somebody with a background in mathematics (but no programming) to learn how to program FD, rather than just learn the theory. This is not really made clear by the current article and I will be adding an overview.
Thanks for the feedback though - I'd welcome any more, obviously I want the article(s) to be accessible to as many people as possible!