Tuesday, January 22, 2008
Well, if not gone at least transformed into a concurrency blogger. Steve Teixeira, who speaks and blogs on C++ topics and has a wicked sense of humour, has joined the Parallel Computing Platform team. On the one hand, this is great news, because concurrency is hugely important to me and having Steve there will be good for it. But on the other hand, who is blogging C++ things now? Sigh.
Monday, January 21, 2008
I decided to add a Concurrency Category, and to go back in time and add things to it. I hope it helps you find my posts on this increasingly important topic. I enjoyed reading some of what I've been writing about concurrency for the last two years.
Sunday, December 23, 2007
You know something is mainstream when it starts to get named. I've been talking about concurrency matters for over two years now. And now it seems almost every day somebody comes out with something you just have to read or watch on this matter. An attendee at Tech Ed Developers in Barcelona asked me "isn't it confusing and wrong that people are doing such different things in this space?" I don't think it is. Some folks are trying things with libraries, with compiler directives, with new language keywords, with whole new languages, with frameworks, with the operating system, with the hardware, ... with everything you can think of. And I don't know which things will work out and how the various things will work with each other. None of us do! But it sure is fun to watch it happen, and it's probably the only way to do it.
So, some links for you, accumulated over the fall:
Herb's advice is good. He says "Expect at least dozens of major product announcements and releases across the industry, before the toolset expansion phase is fully underway and approaching some maturity. We the industry have undertaken to bring concurrency to the mainstream, and as with OO and GUIs it will take multiple years, and multiple major releases, across the industry on all platforms." Bring it on!
Saturday, December 22, 2007
The screen on my Dell laptop was very very broken earlier this year:
The nice Dell people came out and fixed it under warranty, but they were missing a part in the stuff they sent to the repair tech. The missing part was sent to me to install myself (don't worry, it's self-adhesive.) A box arrived roughly the size of those MSDN CD shipments - about 4" x 6" x an inch or more thick. Inside there was a lot of foam and other padding, and these (I added the penny for scale):
That's six little black dots on their self adhesive backing. Turned the six screw heads around the edge of my laptop from uncovered to covered:
I like the look, but why couldn't they have trusted the tech with them as part of the first repair?
Friday, December 21, 2007
Raymond Chen asked why QuickEdit mode isn't always on for command prompts. Then he gives a cogent explanation of why, but he left me wondering what QuickEdit mode is and why I never knew about it. I copy things out of command prompts (or DOS boxes as I usually call them) all the time - usually file names, but sometimes results from things I ran or commands that I am pasting into instruction manuals. As you may know, this generally involves getting into "mark mode" first:
But there is such a thing as QuickEdit for a command prompt, and it basically means you're always in Mark mode. You can change the properties for the shortcut (on my Vista machine, the Visual Studio 2005 command prompt is in C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Microsoft Visual Studio 2005\Visual Studio Tools and that's probably where it is on yours too.) Here's the option:
You have to consent to using your admin powers when you save this change, and then that command prompt is in quick edit mode every time you launch it.
It may not save much time but it saves so much frustration! Hope it helps you too.
Thursday, December 20, 2007
Long ago I blogged about a motto of ours: Fail Fast. Some people replied with comments like "why fail at all?" but that misses the point. Mottos are short and pithy; a more accurate version of the motto would be "if you're going to fail at all, get it over with at the beginning." Here's another take on the concept ... how a week's stall while a decision gets made can cost a company thousands of dollars in hard costs. It's my experience it costs far more in reduced morale and productivity over time.
Wednesday, December 19, 2007
Are you going to Mix? Still trying to decide? Maybe The Signal can help you decide ... or get you warmed up if you're already committed to attending.
Tuesday, December 18, 2007
Soma blogged this before Tech Ed Developers and I actually snagged a few bullet points to add to my slides, but I never posted a pointer to the original. It's nice to see some firm numbers and as always nice to see "higher ups" remembering C++.
© Copyright 2020 Kate Gregory
Theme design by Bryan Bell
newtelligence dasBlog 2.3.9074.18820
| Page rendered at Sunday, January 19, 2020 3:42:00 AM (Eastern Standard Time, UTC-05:00)
On this page....
Pluralsight Free Trial
Click Start a FREE 10-Day trial