Why are there so many surfaces on a toilet? Depending on where in the world you live toilets look different but as far as I can recall they all have too many surfaces to clean.

Lift the seat off the floor and hide the pipes and tubes. Make the seat go in the washing machine.

The Visual studio editor still doesn’t give the opportunity to highlight the row where the cursor is.

There is no gratis addin solution I am aware of either.

Please make this happen.

Update:
There are extensions that does this.

In my editor I spend too much time looking for the cursor; up, down, left, right.

Why not have the cursor in the same line, like 30% from the top, and instead move the text behind it?

This will make it possible to always write the code/text at the most comfortable place.

Sometimes one wants to write at the top (see code below) or vice verse and one could move the cursor to a new base position then.

(Finding the cursor is easier with a highlighted line where the cursor is.)

(copied from the old site)

There is no need for vacuum cleaners to be as noisy as they are.  It is probably both easier to design and create a noisy vacuum cleaner that a quiet one.  But there is no law of nature stating that a vacuum cleaner has to sound more than a 100kW car.

There is a good dataset visualiser in Visual studio.

But if one uses lists one is out of luck. I have tried creating one, but failed either of lack of competence or lack of time.

There might be a way to export a list to a datatable and work from there but strange enough I haven’t tried.

Create a debug visualiser for generic lists in Visual studio.

SQL queries easily get hard to read; and then even harder to debug.

With a “debugger” I don’t mean a step-by-step debugger like when debugging a normal imperative program but something that can handle and visualise sets.
What such a debugger would look like I don’t know. Yet. Please tell.

In most (all?) object oriented programming languages it is possible to have a reference to an object and have this reference be null/nothing/nil.  There are many cases this isn’t a good idea; like for instance method signatures.

AddCustomer( Customer customer )

and customer is null.  Not very common…

It would be nice to have a reference type that cannot be null.  Ever.  The compiler should also know about this and break if the code flow allows the reference being null.

When developing Winforms (and Webforms and Aspnet) in Microsoft Visual Studio there is no aid to stop me from entering overlapping shortcuts.

For example I have a menu with 5 items which have shortcuts alt-F, alt-E, alt-V, alt-T and alt-H.  It is then important that my buttons don’t have the same shortcuts.  There is nothing in Visual Studio signalling a shortcut used in more than one place.

Technically this could be solved through recursing through the controls of a form.  It can be done in the OnLoad event and only in debug mode.  The controls could then be highlighted and maybe reported since it isn’t possible to statically change shortcut while debugging and at least I forget which two controls should be changed to what.
One could take it further to show up already in the designer, that would be the nicest solution.

It is more complex for MDI interfaces.  There is no static linking between a parent and child forms.  One could have a settings file describing the relations.

Ditto tab controls.

Then we have rules like that alt-S should be Save and alt-E should be used for Seek throughout the application.  Without thinking one could use alt-S for Seek in a form somewhere which could fool the user into believing he has saved when he have not.
The technical solution to this could be to have a common settings file.  Controls using one of the regulated short cuts then flag that they are approved for this by a flag.  A developer might accidentally set a short cut but not a flag at the same time.

Every electrical coffee grinder I have hear has been noisy with an irritating sound.  There is no need for this.

I once took my manual coffee grinder and my cordless drill.  Not noisy at all and it managed coffe for a table of 12.  It was maybe not as fast as a professional machine and absolutely more complex to use.  But it *was quiet*.

A 1000€ machine in a coffee shop really shouldn’t sound more than the guests.