Production of the required quantity of seaweed is still a challenge, however the diet is not 100%. The seaweed only needs to be added a supplement to the existing diet. >2% to <10% has been found to be effective in eliminating methane emissions.

[1]https://futurefeednews.com/the-science-behind-futurefeed-asp... [2]https://www.researchgate.net/publication/293800275_The_red_m...

I dunno fella bombing the shit out of people on the basis of their data trails seems pretty dystopian to me

Yeah I couldn't really understand the objection here. If it was meant to be an example of sloppy thinking it is a poor choice.

Do you ask people if you can record it before hand? How do they take it, if you do?

Good question - I do, always, and so far no-one has had a problem with it.

Of course, there's an element of judgement in deciding what meetings are worth recording or not. I'm doing a PhD, so typically I only record meetings where information is being presented (of which I have a lot), but not those which exist exclusively for making decisions or whatever.

Thanks for the insight - I've wanted to do this with corporate meetings but haven't got past the first step of actually asking. Maybe people won't have as much of a problem as I think they would - only answer is to try, really.

This should be the OED definition.

Did you learn how to do it properly? How?

Read "Software Estimation: Demystifying the Black Art" by Steve McConnell [1].

[1] http://www.stevemcconnell.com/est.htm

Well, just from skimming some of the pages on Amazon, it seems to back up a lot of the original article's points.

eg. on p25 McConnell lists project outcomes by project size:

   1000 LOC -> 81% on time, 4% late, 2% cancelled
   10,000,000 LOC -> 14% on time, 21% late, 65% cancelled

Smaller project, better estimates.

Also notice that McConnell uses terms like "Approved Product Definition" and "Requirements Complete". It's a rare project, particularly in the consulting world, that can nail down requirements to the degree that you get really accurate estimates. For packaged software products it's doable, for other things, not so much.

Yes, I can and do estimate accurately, as can many others. Estimation is a basic engineering skill.

McConnell's book, linked to by the other contributor, is a sensible introduction to doing reasonably accurate estimates for projects that aren't incredibly huge (10MLOC+). Very accurate estimates (within 5-10%) and estimates of incredibly huge projects are also possible but require specialist estimators with extensive training and practice.

Could perhaps managers accquire this basic engineering skill? Or is there some actual work involved in this and they can't be bothered?

"The Better Angels of our Nature" by Steven Pinker shows that this is the least violent time in history.

http://www.amazon.com/The-Better-Angels-Our-Nature/dp/014312...

From Jason Cohen

"This is always how the conversation would go:

PM: What kind of discount are you offering?

Me: We don’t discount; instead we put our pricing on our website so there’s no misunderstanding.

PM: Well I’m going to need some kind of discount. How about 30%?

Me: As it says on our website, we don’t discount.

PM: But I’m buying 400 seats!"

http://blog.asmartbear.com/startups-emotionally-draining.htm...

Looks like a great tool and I'm looking forward to putting it in action.

But, what's with the robot and spaceships blowing up a city in the background of your site?

I think that people in Burnie in the middle of Tasmania would probably receive the greatest benefits from having fast and reliable internet access. With online education and MOOCs opening up education to those who want it, giving isolated and rural communities access increases the opportunities available to them at a far greater rate than giving the innner city the same benefit.