CodeCuriosity

That is too true Jason and really my point. Heavil...

2009-10-20T10:19:02.697-06:00

That is too true Jason and really my point. Heavily following process reduces everyone to the lowest common denominator, introduces resistance to any form of change and stifles innovation. It can also have a dire influence on your team because your best people feel unused and begin to under-perform or leave.

I really love that quote. Nothing kills your desire to get things done faster than a bunch of overhead work that you cannot see the point of.

This post reminded me of a clip from the TV show M...

2009-10-19T14:59:06.564-06:00

This post reminded me of a clip from the TV show Medium I watched a couple nights ago where an employer told his newly hired employee "You have ambition but I have no use for that."

For repetitive, high volume widget production you want to have interchangeable 'parts' (such as people) that do only a few things albeit it very well. When one breaks you can quickly install another and keeping producing. In some other industries, possibly the software industry, every problem that comes along is different in some small or large way. You want your team to take that problem and, building past experience and newly acquired knowledge, come up with a solution that exceeds the goals (timeline, budget, and a host of other metrics). Forcing everyone to be the same has essentially reduced your team’s productivity and creativity to the lowest common denominator (status quo). It’s probably much easier to predict the outcome but in no way does it challenge the team nor its members to strive to better themselves. Companies that resist change are destined to die.

Ctrl+F12 - member search

2009-09-02T12:59:34.695-06:00

Ctrl+F12 - member search

Overall this is a comparison of value vs. referenc...

2009-08-31T10:14:33.103-06:00

Overall this is a comparison of value vs. reference types.

As you mentioned, I think structs should only be used for small and immutable objects. Messages, depending on the implementation, should probably not be structs IMO.

One thing that you didn't talk about was value type) in a method or a wrapping object boxing/unboxing. Whenever you use the struct (a (e.g. array) that takes a reference type (object-derrived) the struct will be copied to the heap anyways. Also, if one is using any reference types within the struct (e.g. string, arrays, etc.) they are already using the heap and simply performing a shallow copy when replicating the struct.

Expression Studio 3 is out. I would assume they wi...

2009-08-25T16:47:31.216-06:00

Expression Studio 3 is out. I would assume they will update the terms.

Settings / Formatting / Convert line breaks Set t...

2009-08-25T16:32:05.094-06:00

Settings / Formatting / Convert line breaks

Set this to "No" or the code will be double/triple lines.

Hi Tyler..me Deen from Golden Sand, Malaysia. Lot ...

2009-08-25T15:44:55.009-06:00

Hi Tyler..me Deen from Golden Sand, Malaysia. Lot of information from your blog. Interesting.Op..greeting from Malaysia. Hope we can share some ideas here.

Deen

test

2009-08-25T10:57:26.617-06:00

test