tjpick

Navigation is pretty handy, but the thing I really love about a smartphone is having a decent portable camera always with me. To quickly take a snap to share with family (mms, email or social media), when you otherwise would have missed that is pretty cool.

it's probably safer to just remember to use mv instead, because there's a very high chance that you'll do the wrong thing on a terminal that doesn't have that alias available.

why don't you set your default search engine to wikipedia?

realistically, at 27 one is a long way away from senior.

> how do you prevent yourself from wasting hours on Facebook/Twitter/HackerNews/YouTube

Have kids.

Well, the classical engineering domains are all pretty different anyway (electrical, structural, civil, etc). I remember my grandfather saying he thought it was ludicrous that they were all covered by a single qualification.

Building software with an engineering approach is a real thing. Not everyone subscribes to it, but doesn't mean it isn't a real thing.

For the record, I do a lot of gardening too, and building software has fuck all to do with that.

I also don't get how everyone who argues against software-as-engineering talk like buildings and bridges never fall over. They do.

> When you're pissing your diapers in an old people's home, what good is your retirement money?

As I've understood, the point is to blow all your retirement money between the age of 65(standard retirement age), and as you so eloquently put it, the age when you are pissing yourself in an old folks home. With a little luck, you've got about 30 years there.

> Stuff.co.nz (Fairfax Media) is a more credible news source IMO.

If you are interested in the most credible celebrity gossip news source, that is. Stuff is terrible.

> Building something interesting requires a surplus of time and money. Salaried jobs provide neither.

Standard negatory bullshit. You should be able to achieve building something interesting, using someone elses time and money. If you can't, maybe you've got an attitude problem, not a job problem.

Original source FOR the "orders of magnitude" claim seem to usually point back to Fred Brooks Mythical Man Month (5-10x) or Robert Glass (Facts and Fallacies of Software Engineering) 28x. I don't think either of these multipliers are accurately expressed as "orders of magnitude", regardless of them being supported by evidence.

There is some discussion of the topic in "Making Software: What Really Works, and Why We Believe It."

No.

They are part of the curriculum in a good SE degree. There is a SWEBOK. http://www.computer.org/portal/web/swebok

> who have every interest in making the higher cost phones more attractive by not updating the Android version on lower cost phones

You'd be better to attribute that to them being under-resourced to deliver software updates to all models of phones immediately. They focus on shipping to the high end phones first -- those customers have paid more for that support. Some low end devices just never get to the top of the priority list.

If you want upgrades, buy the best phone you can. If you are buying low end, you have to realise that it's essentially locked to the version that it ships with.

That's my take on it anyway. I don't have any inside information.

about:blank

and then he jumped in his flying suit and flew around the city beating people up under his own sense of vigilante justice, all powered by the rubics cube sized nuclear reactor he has instead of a heart...

But you're worried about the influence of the talk of patent has on your kids?

Do scrum. You have the vision and the budget. You are the product owner.

Hire a scrum master and a team. Pay them handsomely and treat them kindly.

I got the N9 here in New Zealand a couple of months ago. It is absolutely brilliant.

By absolutely brilliant, I mean $200 cheaper than the Lumia 800 (which I also got for my wife); A mile better than the crappy samsung gio I previously had; beautiful hardware design; very hand front facing camera and auto adjusts screen brightness to ambient light; very good account management/integration.

The thing that lets it down is app availability.

Jolt award winners, and Martin Fowler's signature series

Kiwi?

[edit: read your profile. Actually Aus]

was going to comment that neither python nor ruby are that great if you are looking for jobs in NZ. There are more options with php, and if you are good at what you do it won't be that hard to destroy the other candidates. Java and .net will give you a lot more, better paying options.

In some situations, giving developers direct access to remote [production] servers is unacceptable. (Areas like healthcare, banking.)

Not everything in life is about developer efficiency.

Why is it a problem?

I personally get a Macbook because it's a good balance -- I can run all the unix/dev tools I want, and my wife can plug in the digital camera or printer and I can plug in my iPod and have it do something sensible.

She's much happier on OSX than on FreeBSD. I'm much happier on OSX than windows.

Eat well, get exercise, sleep properly, drink lots of water.

Vitamin tablets are a symptom not a cure.

the NHS couch-to-5k podcasts are pretty good motivation for running. (Background music + an encouraging human voice that speaks up every now and then with things like "you're doing great, just 10 minutes to go, keep going... " etc)

No you don't. You take the whole thing, with the husk on, and microwave it. Then you give it to the kid, and they pull the husk off, eat it, and throw the husk and cob into the compost bucket.

If you are worried about healthy meals, you probably don't put butter on it at all.

> Preparing and cooking fresh food requires much, much more effort than prepared packaged foods. Microwavable or similarly low/zero-prep food products.

Microwaving corn on the cob is pretty much as low effort as it gets.

It sounds like you have only worked with arseholes. We need less arseholes in the industry, and more civil, caring, and talented engineers.

I've worked with very good engineers, of both sexes.

the five thousand lines factory class is the real problem.

Not really.

But if any, Apple, because I'm a paying customer in my own country.

Like anything: quite well, if you are good at it.

never had the call to do it myself. Just something I keep in the back of my mind for a rainy day. The benefits would be application specific, I don't think it's something that you balance against POST to the collection in the general case and do one approach exclusively. I have used POST to collection extensively and PUT for create never. One example I can think of is you are making one of those sign up forms that does AJAX to check that the username is free or not. You could use a PUT in a case like that because you've already done the extra server trip as part of a usability improvement.

> since the client now needs to know how to address a particular resource

for creates, it's still possible that the client has previously queried the server and been allocated an appropriate address that the new resource should be PUT to (eg been advised of the next free auto-id, or creating using client generated GUIDs). PUT seems appropriate in these cases.