Navigate/Search

Archive for the 'Software Engineering' Category

2 C# Geeks I’ve actually talked to

Tuesday, May 5th, 2009

Not that either would remember of course, I’m just saying…

Before my mental breakdown they helped tremendously on a few projects by helping me wrap my feeble mind around a few ideas in the C# Usetnet groups.

Anyway…

Peter Ritchie

Jon Skeet

I often forget that an idea should start on paper

Monday, May 4th, 2009

Seriously, there is simply no comparing typing a bunch of text into an editor as opposed to sketching it out on paper first.

Related Links:

Good testing starts with a good strategy

Self-Generating Code

Friday, February 13th, 2009

I didn’t call this one a gem for a couple reasons.

  1. It’s really stupid to do this — especially compared against other more modern and secure techniques.
  2. I don’t use C/C++ at the moment.
  3. The code is ugly.  Most C++ is though.

Another Gem from The Code Project – A flexible charting library for .NET

Friday, February 13th, 2009

A flexible charting library for .NET

Put dependencies under source control

Thursday, February 12th, 2009

Another Stack Overflow gem in “How to use Office from Visual Studio C#?“  The question was exhausting but one of those who responded had some sagely advice:

The answer is to “Copy Local” whatever assembly dll you get for the interop. Once you have the assembly dll in your output folder, add a reference to it, and check it into source control.

Now everyone has the referenced assembly dll.

—anonymousstackoverflow

Now I’m sure to some that may sound like kindergarten learning but it never dawned on me to put external dependencies under source control.

In this fashion a set of legacy developers can maintain legacy code while emerging standards developers can maintain the latest emergent standard — both separated from the other one’s development.

I’ve had a light bulb and it’s warm.

Great tips about Structuring Solutions in Visual Studio

Wednesday, February 11th, 2009

The Elder” is apparently a freaking genius.  Tip #2 changed my life although apparently I was already doing this.

I freaked out at first — I thought I was guilty of it. Rather, in the IDE I use for PHP code I group similar projects in same name spaces or work spaces. I got to thinking though, and I NEVER plan to develop any PHP for deployment into executable bytecode or encoded somehow. So grouping projects under one general solution label is fine.

Brainsick Solutions for example is a namespace in most of my C# and PHP code. That’s where:

  • blog.* WordPress widgets and blog development takes place.
  • portfolio.* modifications to the portfolio gallery and development of separate galleries.
  • …several more app.*s in development.