|
I certainly get where you're coming from. I'm still using an old MS Internet Keyboard from way back. Both of the legs have broken over time and I've epoxied them back on. Of course I have to use a PS2 to USB converter. It's the bulk and robustness of the keyboard I like - most of the ones today are so cheap and skimpy (at least the ones that come with new PCs).
|
|
|
|
|
Recently, i switched from a Microsoft mouse to a Logitech Gaming one (a G300S if you're interested), which is both inexpensive and pretty useful as it has a lot of programmable buttons, unfortunately, to program them you need Logitech drivers, but once you do so, and the profile is stored in the mouse itself you shouldn't need them.
"Science fiction is any idea that occurs in the head and doesn’t exist yet, but soon will, and will change everything for everybody, and nothing will ever be the same again." Ray Bradbury
|
|
|
|
|
I'm gonna rain on your parade. Don't take it the wrong way, just expression my own personal view.
This is exactly the type of mouse I started purchasing after my last IntelliMouse died - I thought the extra buttons would come in handy, but instead over time I realized the fancier the mouse, the less useful the extra features tend to be - I'd often find myself accidentally hitting the extra buttons for example. I had one that had a button on top dedicated to changing the DPI setting on the fly - who needs to change that after it's been set once? (I didn't buy it for that reason)... Just as can happen with software, to me these were always cases of packing in extra features, at the cost of usability.
I could even do without my IntelliMouse's extra two buttons on its left side (mapped to the browser's Back/Forward buttons) - but fortunately they're not positioned in such a way that I ever hit them accidentally.
Of course YMMV, and it's perfectly reasonable for you to swear by yours. That's why there's different models. And that's why I'm happy "my" simpler model has made a comeback.
|
|
|
|
|
Don't worry, it's raining season here, so my parade is ready for it .
I actually purchased it for all the extra buttons (and they're mapped to a lot of navigation shortcuts in Visual Studio), my previous mouse (a Microsoft Comfort Optical Mouse 3000) had an extra "zoom" button, that at first though it was was a fancy gimmick, but proved pretty useful as i could remap it to do something more useful, so when it started to fail i look for another one or something similar, but all the ones i could find where wireless, which i didn't like, so i waited until i found one wired and with more buttons.
However, i still miss the solid feeling of that Microsoft mouse, as the Logitech one feels too light for my tastes.
"Science fiction is any idea that occurs in the head and doesn’t exist yet, but soon will, and will change everything for everybody, and nothing will ever be the same again." Ray Bradbury
|
|
|
|
|
I loved the Intellimouse, and then the Logitech MX510. But - for the last three years, I've been using a Steelseries Sensei RAW (which now has been superseded by the Sensei 310). I love the Sensei as it is perfect for ambidextrous use. It has two programmable side buttons on each side, and a sensitivity change switch on top - which allows you to switch between two distinct "speed" settings. Handy when you are pixel fiddling with images.
|
|
|
|
|
...it's the sign of a junior programmer when they put #region tags inside methods. Because that method then becomes a 10,000 line monster, "neatly organized" by #region tags rather than being broken out into multiple methods.
|
|
|
|
|
Hey!
I've done that like once maybe, to encapsule error handling I think.
In my infix-to-postfix method?
|
|
|
|
|
Congratulations, you've now probably just given a lot of them that idea...
Sometimes things should just be left alone, never to be discussed. This probably qualifies.
|
|
|
|
|
Where I work it's not infrequent to hear someone say "Think about Uncle Bobbing that" or "Uncle Bob the hell out of that method" as I recently heard.
Nowadays every junior programmer would benefit from meeting Uncle Bob early in their programming career.
“That which can be asserted without evidence, can be dismissed without evidence.”
― Christopher Hitchens
|
|
|
|
|
"Clean code? What, like with a cloth?"
"Never attribute to malice that which can be explained by stupidity."
- Hanlon's Razor
|
|
|
|
|
Of course, some Sr Developers will see 10,000 lines of things that need to be relocated to external methods and will #Regionalize it with a comment of ToDo.... and send it back to junior
Director of Transmogrification Services
Shinobi of Query Language
Master of Yoda Conditional
|
|
|
|
|
I started using .NET 1.0 (whatever it was).
We honestly developed an in-house Web App using .NET 1.1 and from what I remember by the time .NET 2.0 released Microsoft was even decrying the use of #Region telling others not to use it.
I am always amazed (and righteously annoyed!) when I find it in code.
EDIT
Here's a rant on #regions by CodingHorror that dates back to 2008:
The Problem With Code Folding[^]
|
|
|
|
|
Regions are like any other tools - use as appropriate and when needed. I like them because I am OCD and they are the very epitome of neat and tidy - I can hide the code I have no current interest in. Besides, spaces are a far worse crime than regions - they are evil incarnate and I ALWAYS reformat to tabs - what sane person wouldn't?
Keep your friends close. Keep Kill your enemies closer.
The End
|
|
|
|
|
|
Well, C# 1 didn't allow partial classes (WTE!!!) so regions kinda filled the gap.
|
|
|
|
|
PIEBALDconsult wrote: C# 1 didn't allow partial classes (WTE!!!) so regions kinda filled the gap.
That's a good point and I wonder if that is why the Bozos at VSTudio invented them? Then they couldn't remove them later because they created an entire industry behind them.
Also, if I tweet a #region how do I #hashtag it? ##Region?!?
|
|
|
|
|
|
I was tweeting #figuratively.
|
|
|
|
|
PIEBALDconsult wrote: Real men don't tweet.
And there you have it: the slogan for the Democratic presidential campaign!
|
|
|
|
|
|
|
raddevus wrote: We honestly developed an in-house Web App using .NET 1.1 and from what I remember by the time .NET 2.0 released Microsoft was even decrying the use of #Region telling others not to use it.
Regions are purely an editor thing. Is it fair to talk about them in terms of .NET runtime versions?
|
|
|
|
|
dandy72 wrote: Regions are purely an editor thing.
Just referencing the time period via the .NET versions.
I couldn't remember what Studio was called before they called it Visual Studio YYYY.
I remember Visual C++. I remember Visual InterDev. I remember Visual Studio 2000. I think it may have been called Visual.NET or Visual Studio.NET or some such.
|
|
|
|
|
raddevus wrote: Just referencing the time period via the .NET versions
The actual VS names would've been the better reference if you were trying to put things into age perspective: .NET 1.0 shipped with VS 2002, and 1.1 shipped with VS 2003.
I'm looking at the installers right now in my archives folder.
|
|
|
|
|
VisualStudio.net 2002 was what I first used for C#.
|
|
|
|