|
They already do we're the dummies!
|
|
|
|
|
Why would they consider an outsider?
.-.
|o,o|
,| _\=/_ .-""-.
||/_/_\_\ /[] _ _\
|_/|(_)|\\ _|_o_LII|_
\._. |\_/|"` |_| ==== |_|
|_|_| ||" || ||
|-|-| ||LI o ||
|_|_| ||'----'||
/_/ \_\ /__| |__\
|
|
|
|
|
He's apparently good friends with Ballmer.
Which I would think is one of the many reasons to disqualify him.
--------------
TTFN - Kent
|
|
|
|
|
Because Ballmer fired all the competent insiders.
|
|
|
|
|
Wow. That's like making Sculley CEO of Apple. That went well, didn't it?
|
|
|
|
|
Next thing you know, Microsoft will ship their new "Windows Newton"
--------------
TTFN - Kent
|
|
|
|
|
Microsoft's new head of operating systems group, Terry Myerson, gets it. But will he have the fortitude -- and backing -- to build a better Windows? "I am prepared for the worst, but hope for the best."
|
|
|
|
|
Aw we can hope but really it's just the musings and complaining of the aging mouse wielding, touch typing peasants.
"Oh there's no bread, let 'em eat cake. There's no end to what they'll take"
|
|
|
|
|
As Bitcoin hit $1,000 dollars on Wednesday morning, a lot of early adopters saw their Bitcoin, bought or mined for cheap years ago, turn into a high-return investment. And some forgot they bought Bitcoin years ago, only to realize they were suddenly rich. Ohnosecond: The fraction of time between making a mistake and realizing it.
|
|
|
|
|
New Linux worm targets routers, cameras, “Internet of things” devices. And here I thought Linux was immune to viruses...
|
|
|
|
|
Executives discuss new initiatives following reports that government agency breached networks at Google and Yahoo. That doesn't help much if you just give them the keys
|
|
|
|
|
Once bitten, ten times shy - at least until I can compile my own Windows.
Bastard Programmer from Hell
If you can't read my code, try converting it here[^]
|
|
|
|
|
As large IT systems scale to unforeseen levels of complexity, new laws of effective management come into play. Spoiler alert! With more computers.
|
|
|
|
|
Agile development is no longer an alternative way to develop software. With the pace of technology adoption accelerating at a frenetic pace, agile is increasingly the only way to develop software. That is, if you want to stay in business. When I finish the next volume of the requirements document, I'm so going to prove this wrong
|
|
|
|
|
"Make every release a non-event."
Bingo.
/ravi
|
|
|
|
|
The Anti-#region Legion is a community for people that believe that the C# #region is a unfortunate language construct. Free yourself from the tyranny! (For some silly reason or another)
|
|
|
|
|
I agree that #region does not belong to a language itself. It's a code folding[^] delimiter and should be a feature of Visual Studio.
|
|
|
|
|
#region is not a language construct. It's a C# pre-processor directive.
The author's comments regarding the abuse of #region s are very valid.
However, #region s provide a very convenient way to separate constructors, methods, properties and fields in the same file. Relegating these items to different files would lower a developer's productivity.
/ravi
|
|
|
|
|
Yes, let's focus all of our attention on something utterly trivial.
"If you think it's expensive to hire a professional to do the job, wait until you hire an amateur." Red Adair.
Those who seek perfection will only find imperfection
nils illegitimus carborundum
me, me, me
me, in pictures
|
|
|
|
|
I'm not a big fan of them, but I'm not anti either. As they really only affect Visual Studio, and I don't usually use Visual Studio for "real" code (I do a lot of SSIS on my job), they really don't apply to me. I do have some in code I write (most commonly around the "header" portion of my C# files, some times separating groups of overloaded methods).
But really, the guy who wrote that just comes off as a wanker -- as do most bloggers I suppose.
If you don't like a feature, just don't use it -- just as I don't use Linq. I also remove all the using directives from generated code; no big deal, that's just me.
One thing I'd like in a C/C# pre-processor is the ability for it to leave unrecognized directives alone. For instance when I pass a C# file through a C pre-processor I have to protect the C#-specific directives (# region) so it succeeds.
|
|
|
|
|
"One thing I'd like in a C/C# pre-processor is the ability for it to leave unrecognized directives alone. For instance when I pass a C# file through a C pre-processor I have to protect the C#-specific directives (# region) so it succeeds."
Good god no - that's no longer a C preprocessor.
C already provides #pragma for extension - anything in there is ignored if unrecognised.
"If you don't fail at least 90 percent of the time, you're not aiming high enough."
Alan Kay.
|
|
|
|
|
That doesn't do what I want.
|
|
|
|
|
So write one, but don't call it a C preprocessor as that is defined by a standard.
"If you don't fail at least 90 percent of the time, you're not aiming high enough."
Alan Kay.
|
|
|
|
|
There's a good addon for Visual Studio for this[^] , it basically disappears the region tags.
It means my colleagues can #region away if that makes them happy, and I don't see/get affected by it. Everybody wins!
|
|
|
|
|
Some constructors or Init function with several hundred lines of code, structured into a few dozen #regions... They are so practical: if you need the same code somewhere else, just copy the whole region. No, do not eleminate them by creating functions! What do you need a function for when you can use #regions? Gaahhh....
|
|
|
|