Have you read Thinking, Fast and Slow by Daniel Kahneman?
They gave him a Nobel for tackling decision problems. I guess that's one important problem to humanity in general.
Remember once again, AHP/ANP are not the most 'useful' ones, having advantages and drawbacks, but they are a good starting point on Multicriteria Decision Methods (MCDM).
You may want to check MAUT/MAVT, PROMETHEE, VIKOR, Best Worst Method, and TOPSIS (this one is quite simple to understand and use).
I'm sorry to say this, but, this is not so very good.
Having worked with other decision methods such as TOPSIS, AHP, and ANP, and note that those are the simplest and most commented on (and not about its features, but about its shortcomings), in your analysis/software, it is impossible to compare choices among them, which is a huge hindrance to the method.
It takes discipline and cerebral maturity to work at home, specially under distracting environments (e.g. Internet, games, kids).
Long commutes, long lunches, long coffees, long watercooler hours discussing movies, etc., maybe that's had to go anyway.
However, social interaction will always be key in any human endeavour, and that should not change whatsoever.
And Sir, you win the Internet for not mentioning GOL there. Kudos well deserved, Conway was a great mathematician (among other 'skills'). He'll be missed.
Every 10 years or so there is a 'catastrophic' event, so markets fluctuate, players are invited to get out, new players emerge and life goes on and on and on
Next one is around 2030 - see ya !
Getting late to the discussion, but people tackle this for a long time in software engineering, it's called Software Rejuvenation, with models of repairing systems, Markovian assumptions, applications in JVM, etc. Interesting topic. It was used to analyse Patriot missiles that needed the same approach to replenish its internal variables each time.
It's discussed that the eagles would not mingle in those affairs during the crisis, being unable to help in the most difficult times. I know it's hard to accept this and move on, but otherwise the movie would have like 2 or 3 pages, right
Yes. I do this. In Gdocs though, name is productivity, where I add the day in format [dd/mm/yyyy] followed by bullets points on things I thought and did during the day.
It also helps me to wrap my mind around in the following weeks, like, what was I thinking? then I go back to the log, and remember the trail of thought leading to my decisions. It is quite worth a while doing this I reckon.
What if someone created a service like "do I need a license for using this image?" - the system search by image somewhere and return its availability in the public domain (perhaps someone already thought of this though, it's too obvious...
I agree with you. More or less each one of those topics could become a treaty on the subject.
Thinking broadly, one could look at security from the programming point-of-view but also from applications point-of-view, where one understands the concepts behind each issue not necessarily having to know deeper software structures to work or handle security aspects.
It was Microsoft (or other company I don't recall) that every 5 years would lay off 5% of its work force (the least capable or productive people) - this would cause those that remain to work harder next year.
Then, they would open positions. Rinse and repeat.
Have you tried woodworking? Do a small project, let's say, a stool. Use only manual tools. Use a plane to square boards. Use only glued parts.
You'll calm tf down, plane something for two hours straight... :) best man
Despite what people may have told you, writing formal software is a quite mathematical task requiring people involved to really engage and write decent software specifications to begin with.