22/7 ?

First of all, establish exactly what it is they are asking you for. 'Strategy' has to be one of the most abused words in the modern world. Is it really strategy - ie setting goals without defining how they are acheived? Is it policy - ie setting the framework of rules to work within while achieving the strategy? Or is it tactical advice - the nuts and bolts of how you actually implement the strategy and policy?

Assuming it is strategy, then ...

Second, define what you want IT to achieve - in terms of benefits and abilities, and what you want IT not to do - in terms of drawbacks and liabilities.

Third - prioritise the importance of each of the individual results from point two above.

Now you have a list of things you want IT to do, and you understand how to allocate funds and time, based on their priority. The next steps are to decide the policy to run them, and tactical implementation.

You'll get a lot of folks here saying things like "allow FOSS...deny " These aren't direct strategies. A strategy would be to allow solutions to be developed/deployed based on fitness for purpose. The conseqent policy would be to allow multiple OS / applications to be deployed within a controlled framework. The following tactic would be to assess what the user needs and can afford, identify what potential market solutions are out there and how much they cost (capex and opex) and pick the best.

+1 to the above.

As they're offering you a range of experiences, it would be beneficial to learn functional programming, procedural programming, parallel programming. Oh and lisp. If you get a good understanding of the similarities and differences of func vs procedural, and teh thought processes on how to solve problems with them, you'll do just fine. Parallel programming (SIMD / MIMD) is only going to become more and more important as the number of cores in common use rises.

The actual implementation of each functional / procedural language is largely irrelevant - it's learning how to think and solve problems in their respective paradigms.

LISP is a great teacher - derided for the brackets, it is incredibly powerful and based on extremely fundamental maths. Using a handful of operators, you can do the most amazing things.

Even their own marketing calls it "fine tuning". Apple senior execs called it a refinement of Leopard, or words to that effect. It's a service pack.

It's a pro slot, used by pros, to connect pro kit - usually high end audio, video and storage. Remind me of the branding of this product again... oh yeah, pro!

In my case, after just over a year - and that following recommended charge/discharge practices. Apple kindly sent me a replacement, as the first was an explosion risk. It died a little over a year later. My experience is not unusual for a Powerbook battery. The lack of easy access to replace the cell cheaply with a non-oem part is a strong disincentive.

Apple is reducing the price of entry. It's arguable they are NOT improving the hardware (beyond normal Moore's Law) for the same price at the mid and high end prices. Cf express card loss, FW400 loss, discrete gfx loss. And even in their Pro line, they charging $30 for a lead to let you connect to any external display - not even a free HDMI slot. Last but not least, still offering only 2 USB slots, on the 15" models is a joke - especially as there's no express slot now. Use an external mouse, and now you can't plug in your external drive, as there's no spare slot for power. Use a mouse and a external card reader, and you're SOL to do anything else. I wanted to buy a MBP from this upgrade cycle. I won't - instead staying with a Powerbook G4 that's alot slower, but offers so much more in terms of usability. My hope is that APPL will correct some of these decisions in the next cycle. It's unlikely we'll go back to discrete batteries any time soon, but hopefully get what many users want - connectivity options.

tramiel's commodore?

hey, what have strippers ever done to deserve being classed with politicians?

In military purchasing, you'd barely get a washer for $20k, never mind an entire platform!

How much did they cost? When did you buy them? How much are they worth now. How much can you earn from using them? how much do they cost to run?

Add up all the costs, over 12 months, 24 months, 36 months. Add up all the potential revenue they'll earn.

  If the first is bigger than the second, you're losing money - sell them now for as much as you can, cut your losses. If the revenue is bigger, you might consider using Net Present Value (look up the NPV function in your favorite spreadsheet) to determine if it's really a profit. If the NPV is negative or zero, sell. Only if the NPV is postive , and by more than a fistfull of dollars, AND you're confident about the numbers should you hang on to them.

Or can you donate them to a charity, and write them off for tax?

Rant: given that performance / price ratio is constantly improving, why would anyone ever ever ever buy hardware a second before they absolutely have a proven need for it to earn a buck? That's like buying fuel, and letting it evaporate in the desert sun.