Marcin Hoppe - All Comments

re: Jon Skeet writes a book: "C# in Depth"

farnlyduck — Fri, 30 Apr 2010 08:34:22 GMT

brightness average precipitation comments national

Viagra.

Generic viagra. — Wed, 01 Apr 2009 18:36:57 GMT

Impulse female viagra. Viagra buy.

re: Jon Skeet writes a book: "C# in Depth"

Dmitry Lyalin — Fri, 25 Jan 2008 21:10:37 GMT

Jon's written work is by far very excellent and has been featured on my blog as well.

I plan to purchase his book when it finally arrives in a few months.

re: MSDN Tester Center

David Hogue — Fri, 26 Oct 2007 16:57:21 GMT

Nice. More acknowledgment of how important testing is to software development is always good.

Looks like they are having some issues or ironically didn't test the site in Firefox. The Silverlight control is blank and I get JavaScript errors. The videos look like there are two guys at a whiteboard which I think is great, but I haven't been able to get any of them to play.

re: Visual Studio as an editor. Only an editor

Jason Meridth — Tue, 02 Oct 2007 17:54:00 GMT

They also got Phil Haack for the ASP.NET MVC Team.

re: Visual Studio as an editor. Only an editor

Scott — Tue, 02 Oct 2007 16:20:13 GMT

For a while, I got so sick of Visual Studio 2003 that I switched completely to NAnt and EditPlus. It worked great. Eventually I got to the point where I needed intellisense in order to explore all the new namespaces and classes. But it is possible to work on .NET code without using anything but the compiler.

re: Hanselman - I went to his geek dinner in Redmond.

re: Visual Studio as an editor. Only an editor

Joe — Tue, 02 Oct 2007 15:13:36 GMT

Im not dismissing it, but Im a little skeptical of this approach. What does a single project get you? And how does it make automated testing and deployment easier? And why the dislike (from everywhere) of Visual Studio? Do we really want to go back to 1993 where nothing is integrated (I'm looking at you Clipper/Blinker).

Having said that, I have a tremendous amount of respect for JP, the CodeBetter guys and your co-bloggers on devlicio.us who all seem to advocate similar ideas., So what am I missing?

re: Jon Skeet writes a book: "C# in Depth"

mumtaz — Fri, 21 Sep 2007 20:26:15 GMT

I actually read the C# 2.0 spec "cover to cover" two times. The degree of C# mastery gained from reading the spec is exceptionally high. Your coding mistakes become very rare. I recommend reading the C# 3.0 spec cover to cover ( i plan to do it myself ). Trust me....its a very rewarding endevour.

re: How to keep List sorted?

Marcin Hoppe — Mon, 21 May 2007 10:02:01 GMT

I feel a little bit uncomfortable with storing twice as much data as needed. This might be an issue in my scenario.

re: How to keep List sorted?

dwvisser — Fri, 18 May 2007 16:39:24 GMT

I would actually have taken a different approach. I'm lazy by nature, and would have just taken advantage of the existing SortedList class in .Net 2.0:

public class Set

{

SortedList<int, int> sortedList = new SortedList<int, int>();

public void Add(int i)

{

sortedList.Add(i, i);

}

public int this[int index]

{

get

{

return sortedList.Keys[index];

}

It's annoying that the only SortedList implementation they give uses KeyValue pairs as the type, but oh well. Also, .Net's SortedList requires unique keys, but since you're calling your class Set, that's probably not an issue in this case.

re: How to keep List sorted?

Marcin Hoppe — Wed, 16 May 2007 08:35:36 GMT

@krECik:

This is indeed an easy optimization. It didn't come to my mind as in my scenario (during the initialization of the program) I am always adding new items in ascending order, so new items always end up at the end of the list.

@Keith:

This is a good suggestion. Reflector tells me that Add is a little bit simpler than Insert. I will update the entry.

re: How to keep List sorted?

Keith Nicholas — Wed, 16 May 2007 03:26:59 GMT

The first two inserts should be Add, it won't make any difference to the performance (other than probably eliminating one check) but it simplifies the code a bit

re: How to keep List sorted?

krECik — Tue, 15 May 2007 21:17:39 GMT

You could optimize it more in similar way adding after second if block another one.

if( sortedList[0] > i ) {

sortedList.Insert(0, i);

return;

}

re: TDD Tip: Leave a Broken Test

Billy McCafferty — Thu, 05 Apr 2007 20:59:11 GMT

That reminds me of a presentation I was giving last year. As I often do, I had left a broken test for the exact reason you've stated. I was giving a presentation, using my project work as examples and emphasizing the point that you should never have a broken unit test when you check all your code in. To show this, I confidently opened NUnit, ran the tests, and...wham...red bar. A couple of chuckles later, I let them all know that it was broken intentionally for when I got back to work. I think they inferred that I was trying to pass a bug off as a "feature."

re: TDD Tip: Leave a Broken Test

Derik Whittaker — Thu, 05 Apr 2007 11:11:40 GMT

Marcin,

This is a very good suggestion. I know I leave notes for my self every day on where to start back up the following morning (of course i have to do my daily moring surfing first :)).

Derik