2,058 karma · joined May 9, 2010
Our companies site uses a mix of static/dynamic javascript which can cause as many as 100+ requests to be made and we're able to keep page load time < 2secs for the heaviest of pages. # of request doesn't automatically equal a slow website. Add the fact that this gov't site was likely mandated to support some ungodly old version of IE and you can easily see why there are so many js files.
[1]: http://www.webpagetest.org/result/131007_5J_T8/ [2]: http://gtmetrix.com/reports/www.healthcare.gov/1mQBgaqI
The likely culprit here is lowest bid != best product
I'm with a startup called PetroFeed and we're looking to tap into the huge potential in the industry[1]. Most startups in the O&G industry are concerned with building better drilling technologies, or finding new resource pockets; leaving lots of room for companies like ours. ;)
[1]http://en.wikipedia.org/wiki/List_of_largest_oil_and_gas_com...
ref: http://blog.getbootstrap.com/2012/12/10/bootstrap-3-plans/
My plan was to port an existing application over to RubyMotion so that I could iterate faster on it. After a few days of work, the conclusion I came to was that it wasn't worth porting an existing application over. I didn't try to piece meal it (if someone demonstrates this, it will attract my attention), just a full re-write.
For me the biggest hurdles were debugging. When something goes wrong it has to be relatively easy to debug. I was in on the early days of RubyMotion and found that their debug facilities were not sufficient enough for me (I think I'm more towards the end of the early adopters curve.) It's also my understanding that this has improved drastically since the early days.
With all that said, the number of success stories that are coming out of RubyMotion has my attention (especially 37Signals). I will most certainly consider RubyMotion for any upcoming pet projets. I still won't use it in my business since you need someone versed in Ruby and partially in iOS, so until I have more developers with that skillset it's not worth going with something so esoteric since developers are so hard to come by as is.
For those who want to get started, but don't know how checkout Nerd Fitness: http://www.nerdfitness.com/blog/ I have no ties, only that it's a great place to start learning about how to take care of yourself.
So... Heroku's CTO acknowledged there was a problem with their stack, and offered to help RapGenius modernize and optimize it. And RapGenius quibbles on the word "yesterday"?
While I do appreciate RapGenius raising the issue publicly to bring better accountability to Heroku. Their response to Heroku's response ought to have been along the lines of: "Hurray! Everyone's boat is rising with the tide." Not this.
If you want to work remotely you're fighting an uphill battle. Most managers/employers know how to manage face-to-face. Remote management is a skill that many haven't learned yet. It is possible as you mention, however both of those work places are VERY progressive.
If you want to work remotely, sell the benefits of remote working to your employer. Make them confident that you're able and capable of doing remote work. Sell it! I contracted a best friend this summer to work remotely. I had confidence in the outcome because I trusted him. If you can sell that to an employer - how much more likely are you to get what you want?
Really? You'd rather security patches not occur and instead be issued via large batch releases? If that's truly the case, you could achieve the same end by not patching and upgrading to the next major version release. However, that seems truly more dangerous than the inconvenience of incremental patching.
I'm a better iOS developer today, because I learned how awesome blocks can be from Ruby. Same goes for meta-programming.
Languages usually have features that span everything you do in that language. Getting comfortable with blocks in a language that uses them as a primary/native data type shows me how useful they can be in a language that uses them more cumbersomely.
That's how I've benefitted from learning multiple languages. As well as the fact that I will avoid Java/.NET because they and I don't agree! :D
One's own conception of God could be any of those things I listed. Personally, I have spent nearly 4 years in an AA group. So rest assured, I have read the steps.
As to what is taught - God referring to Allah, The Flying Spaghetti Monster, Jesus, Mohammed, etc. - depends on the group/person/persons you've received your information from. There is no governing body for AA, and every group is completely self sustaining. Individual traditions, teachings, and cultures grow naturally in each group providing slight variance from group to group. However the core will always come back to God being whatever you choose God to be.