1,353 karma · joined August 15, 2007
Other than that, you are right, there's a time and place for every technique.
My comment was more a reaction to all the different kinds of diets, and how they're supposedly a better way to lose weight than the previous diet. If you want to lose weight, and you already have a varied diet that meets your body's daily intake requirements, it can be useful to calculate your calorie consumption and burn rate and try to tweak both of those so that you end up with a caloric deficit.
Of course this only directly affects your weight, and you need to also take care of your body's general health. I would hope it's obvious to most that you shouldn't start a wood chip diet.
caloric intake > caloric burn -> weight gain
caloric intake = caloric burn -> weight stabilises
caloric intake < caloric burn -> weight loss
You can alter your caloric intake by changing the amount and type of food you eat. You can alter your caloric burn by changing the amount of exercise / labor you perform.
I don't think this is a claim you can really make right now though. When you send a device back to Apple for recycling, there's no way to find out what their recycling standards are.
Subscribing to EPEAT objectifies this, and makes it easier to know what happens when an EPEAT device is recycled.
Currently focusing on iOS / Rails development, but I've also worked with Android, Backbone.js, Coffeescript and a whole bunch of other technologies.
I'm a good communicator and enjoy finding an optimal solution to a given problem. Firm believer that good code should be simple, succinct and contain the least amount of surprises possible, so this is something I strive for.
Contact details are in my profile.
It might have been less expensive to get a new car seat ?
The main reason for me to give it up is because I could not get it to work smoothly with rvm.
I've gotten quite used to zsh by now, and I have to say, I don't feel much for having another go at fish just to run into the same limitations again.
By now I'm sure everyone has seen the WAT talk (https://www.destroyallsoftware.com/talks/wat) which illustrates some of the more obscure (and funny) coercions.
It's ok to say that JS's type coercion is a misfeature, good programmers learn to not throw out the baby with the bathwater.
I would probably pick the data. It's what can be monetized and it's impossible to regenerate.
Having to recreate the software might even be beneficial in the long term if your engineers are careful enough to avoid second system syndrome.
While I believe there's room for other companies to develop self-driving navigation systems, I think the Android example is pretty apt.
It's interesting to think about when self-driving cars will actually be in stores. By then, all navigation systems will meet strict safety guidelines and some standardised tests.
If all self-drivers are equally safe, the AI's driving style will become a differentiating factor. It seems to me like Google has an advantage in this type of development, although the future can certainly prove me wrong.
As a nice bonus, AFNetworking doesn't require you to implement delegates but instead allows you to use blocks, which simplifies things somewhat.
The nice thing about the Stanford course is that it covers a lot of ground, ranging from good code design, to all the major Cocoa components, to details about most of the important ios lifecycles.
In the article, one of the doctors mentions that the process of growing meat in a lab needs to be more efficient than in a cow or pig.
I'd say the process needs to be AS efficient, and could even be slightly less efficient to be economically viable.
There's a large and growing market of people who do not eat meat for ethical reasons. I've been a vegetarian for about 17 years now, and can't wait to take a bite out of a lab grown steak with some nice seasoning.
It's simple really, if you're not cooking, cleaning, waiting, providing the building, providing money, marketing or anything BUT providing ideas, you shouldn't be surprised if people find your ideas worthless.
At first glance, his simple ad looks like part of the content, the fancy ad just looks like an ad and is filtered out subconsciously.
Definitely a factor to take into account when you're targeting gamers I'd think.
Measuring memory usage causes engineers to focus on it.
Making the data available piques the curiosity of geeks who historically drive change (in a "you should use this browser" way).
Having a few charts comparing with other browsers (chrome in particular) would be a good idea too, especially once they start beating chrome (if ever obviously).
Also, http status codes perfectly solve the problem of needing to know wether an object was sent to the server successfully. No need to reinvent the wheel and mess with guids imo.
A rewrite can be the best thing to happen to a code base, but it is not a panacea for all code quality problems. Sometimes a refactoring is simply a better option.
There are various reasons that factor into this decision, a good one being, as you mentioned, the assumption that you're still working on the codebase in question.
One should always have a "fools rush in" attitude when contemplating rewriting a piece of code he did not write himself.
Always.