Become a fan of Slashdot on Facebook

 



Forgot your password?
typodupeerror
×

Comment Re:Object lesson from the stock market (Score 1) 198

Cancer is a tough disease and, sometimes, the treatments are rougher on the patient than the cure. Chemotherapy impairs your ability to think coherently. You're like the dog in the movie "Up!" ('Next quarter we'll release the Uber Widget to prepare out markets for... SQUIRREL!!!'), I don't know if Steve Jobs availed himself of chemotherapy toward the end, but you can rest assured that he laid out his vision for the management team before he shuffled off this mortal coil; he was too much of a control freak (in the great sense) not to.

Comment Re:It's too bad Intel killed netbooks for this. (Score 1) 513

You want the 11" MacBook Air. My 2010 model is still humming along fine, vastly outperforming all netbooks while taking up almost the same physical space. However, the Asus Transformer series would probably also meet your requirements - for less money. It's a 10" Android tablet with detachable keyboard/trackpad.

Comment Re:What they are actually reporting an Issue. (Score 1) 320

Not exclusively. (And in this case not at all since the Intel driver is open)

Bug-reporting is extremely important if you actually want to provide a high-quality product. Bug-reports can be seen along two axes.


  1.  
  2. Whether your product is understandable to the user. If people consistently make mistakes , you've got a design issue somewhere. The usage of the product is obviously not sufficiently clear, or the documentation is not sufficient etc etc etc.
  3. Whether your product has bugs. In this case, getting a clear description of how you can reproduce the bug is key. These "submit error" pop-ups are popular for a reason - they can submit log files and stack traces, core dumps etc etc.

And some bugs are just plain hard to fix. They may also be a manifestation of a design issue, and those are rarely trivial to fix. I hope Ubuntu gets this sorted soon.

Comment Anyone can be a programmer, but ... (Score 1) 767

Anyone can become a programmer at some level. Simple programming is like coming up with a recipe for a meal - you have some ingredients and combine these to create a hopefully desirable outcome. It's skill, but it can be learned. I mean, I was able to move the turtle using LOGO when I was .. 10? 11?

It does however take both experience and raw intelligence to become a really good programmer. Fully understanding trade-offs takes experience. If you go all-out on even small scripts, you'll waste time. If you just hack away at large projects without design and methodology, your lack of a coherent design will bite you in the gonads. Learning how to communicate effectively with end-users and non-technical team members is also something that takes practice and a certain mind-set. I've seen many, many bad solutions chosen by bright people. I've done some myself, also recently. And I'll make some more mistakes in the future. Why? Because communication is hard. Also for the other party.

Comment Re:AMD64 != Intel64 (Score 4, Informative) 101

x64 is misleading. The x86_64 still uses the underlying architecture and instruction set of the original Intel 8086.. Changing the name to x64 would imply the instruction set is different from that of x86 - and while the instruction set has been extended it still (as far as I know) still support the instructions designed in the 70s.

I personally find x86_64 the most descriptive designation for a 64-bit x86-processor.

Comment Re:Before someone is accepted, it's not accepted, (Score 0) 635

Windows market share is about 80%. Linux market share is about 1.5%. Politics is not the reason behind the lack of games for Linux - market analysis is.

If we want games for Linux, then we gotta systematically buy all good games that are ported to Linux. Otherwise, there will be no business case to port games to Linux.

Comment Some Simple Rules (Score 1) 1127

I worked at Apple as a contractor and as an employee for thirteen years, and it was--hands-down--THE BEST at administering diversity. And I say that as one of the few black people who worked there. The top-to-bottom attitude that over-arched everything was that if you're not thinking about our customers, you aren't doing your job. Management decided that it wanted a diverse, welcoming, vibrant workplace and put policies in place that made the goal attainable. If you were there, it was because you had something to contribute and sexuality, gender, race, religion, and physical or emotional challenges were secondary to your ability to get the job done the way Apple's customers expected it to be done. The policy was enforced strictly. Orientation and performance review targets reinforced the culture. As with the secrecy policy after Steve Jobs's return, all an employee had to do was stick with the guidelines, and they could expect an exciting, fulfilling experience.

That's not to say that things at Apple were perfect. One manager decided to release a pictorial chart of his organization. His diversity problems were apparent to everyone but him. Workplace romances are not unheard of. Still, the things I learned from the experience of working at Apple have stood me in good stead.

  Your co-worker as a fellow human being ALWAYS comes first;
  If you're thinking about anything other than doing your job while you're at work, you might be setting yourself up for a fall;
  Don't do anything that might distract your co-workers from achieving their goals and objectives.

Comment Re:Wifi (Score 4, Insightful) 230

After upgrading to Lion, my 2008 iMac suddenly started dropping the wifi connection periodically, while my 2010 MacBook Air is rock stable. Anyhow, that's my experience. Anyhow, we'll need a bigger sample in order to determine if Macs really have more wifi-issues than Windows computers. Statistics matters.

Slashdot Top Deals

He has not acquired a fortune; the fortune has acquired him. -- Bion

Working...