I wish I could mod you up. Spot on
I wish I could mod you up. Spot on
I very seriously agree
So, the choice is - do we choose a single hybrid framework and learn that, or do we develop for IOS / Android / Windows phones natively and learn three things?
In terms of frameworks etc..
I think it is important enough to have atleast one 'skunk-works' type project that every developer needs to work on, just to keep up with what will be boring a year or two down the road.
I avoided "not boring" for a couple of years and for the last month, while I look at hybrid mobile apps, I am stunned by my lack of knowledge and the abundance of terms, concepts and technologies that mean nothing to me
Every organisation needs a "not boring" slot of time for their developers. Not for product that needs to ship NOW.. but for stuff that may need to ship next year.
May I suggest that you go back in time (or go into the future) and look for a video called "EPIC" or "Googlezon".
A lot of this is possible with crowdsourcing, but use machine driven processes for the basics - far too many agendas out there once your site / service becomes popular. Look at text / sentiment analysis engines and mashups with larger public databases to drive facts.
Not just "sounds like"... they've got nothing other than speculation which confirms earlier speculation.
Tschauner’s description of bridgmanite gives us no such insights about the inside of the Earth, other than to confirm what scientists believed to have been true for quite some time: The mineral exists, and it can occur naturally under highly pressurized conditions.
Seems like submissions from certain accounts (MojoKid is one of them) get approved, regardless of the value to the community. I'd speculate that sites like hothardware do advertorials which they then promote through various "social networks".
I seriously recommend this blog from Rackspace to those who are so caught up in cloudy-cluster-off-premises-corporate talk.
This rising complexity and cost on the multi-tenant cloud is hitting customers in four main ways:
- They spend more on engineering time and talent to architect for failure on the multi-tenant cloud, which is complex and hard.
- They also spend more on engineering to deal with inconsistent performance, which is even harder.
- They spend more on infrastructure, because over-provisioning is one of the major ways to compensate for inconsistent performance.
- They spend more through the virtualization tax, which can diminish disk and network performance by 5 percent to 20 percent.
KEEP your existing hardware as a live back up for when it starts raining in the cloud. Better yet, build in cost for new hardware on your rack over the next year to lower costs / maintenance and get some experience in building and operating your own in-house cloudy thing.
To be technically correct, the character would be called, "Wonder Peroffspring"
Thank you. Now that summary would have given me a lot more incentive to read the linked article. Was a bit put of by the nail polish bit -- simply because as much as I know that IBM maintains a very diverse range of research teams, nail polish would not have been something their geeks or PR department would have highlighted.
Starting off with
But the real application is
Most people are consumers of tweets. They follow people, click through their links / updates etc. If you look at forums and other community media, you'll see that getting >10% of users to contribute is actually VERY good.
Cannot find the original post
The analogy is incorrect. The builder is often the business owner and it is the business that is paying to remedy the defects. If the mechanic at a car dealer got something wrong, it would be the car dealership's problem, not the employee's problem (he could get fired
Costs of bugs / fixes etc are built into the product development cycle.
Would be another story if you came into office drunk and added a whole lot of code that then needed to get fixed. i.e. You were personally negligent and should be held liable for your actions (in my opinion).
>> Slashdot has many faults, but editing and deleting posts that don't agree with the editors doesn't seem to be one of them.
And this discussion is a testament to that.
What i meant was, you own the resources / IP, bring together a few volunteers.