|
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 #regions are very valid.
However, #regions 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....
|
|
|
|
|
Arduino co-creator releases blueprints for a do-it-yourself phone. Not compatible with Angry Birds
|
|
|
|
|
We're all used to getting touchy-feely with our phones and tablets, but it's only in the past few months that touchscreen laptops have really gained any ground. A report by NPD DisplaySearch states that by the end of 2013, touchscreen devices will account for 11 percent of all notebook shipments -- that's around 19.8 million notebooks with touchscreens -- and there has been a steady increase in market share since the beginning of the year. The fingerprints on the screen identify the machine as mine
|
|
|
|
|
Why is right my friend.
|
|
|
|
|
Why? Simple answer: Missing education. Haven't your parents taught you not to touch the TV screen with your fingers?
|
|
|
|
|
Phones? OK. Tablets? OK. But Notebooks? I don't see any benefit in having a touchscreen in a Notebook unless it's one of those hybrid machines. A Notebook PC serves a specific kind of task/application: typing. The keyboard is the important thing and what differentiates it from a Tablet. It might be a nice gimmick to have a touchscreen, but I wouldn't miss it either. To get something done (write text or code), I wouldn't use it 99% of the time anyways.
That's for now. But in a few years, I guess we won't discuss this anymore as touchscreens will be a given on any device whether it's useful or not. "Wait a second - a screen without touch? Seriously?" Remember CRT displays, anyone? 
|
|
|
|
|
The RTM version of the Visual Studio 2013 ALM virtual machine and hands-on-labs / demo scripts are now available! No fuss, no muss, just bits
|
|
|
|
|
The comet made of primordial ice could provide a spectacular Thanksgiving show for earthlings. Or don't watch: you don't want to be blind when the triffids come.
|
|
|
|
|
Start menu 'solutions' have divided the Microsoft faithful in a battle that could be avoided if users are given a simple choice. We just want a start button, is that so wrong?
|
|
|
|
|
I agree that it should be about choices. Windows 8 killed the Start button with no option to bring it back, 8.1 just did the opposite - instead of providing a choice they enforce their decision whether there is a visible button or not. No middle-way. Not very user-friendly. Personally, I didn't miss the Start button in Windows 8 and I find the reintroduced one in 8.1 a joke. Unfortunately, I can't turn it on or off. Thankfully, there is a little tool that does the job. No Start button for me anymore.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
