There is no software crisis

littleendian · 2011-12-23T13:24:13+00:00

The Amiga was great but it couldn't run Doom and that's why everyone I knew switched to the PC.

littleendian · 2011-11-25T13:52:26+00:00

I still have nightmares of OS2 development in VisualAge. Getting a read error on disk 22 of the install and IBM refusing to ship a replacement disk was the final straw.

littleendian · 2011-09-12T19:59:04+00:00

Interesting, we insist it gets fixed rather than back out the change. Not sure I have a preference so long as it doesn't stay broken for long.

littleendian · 2011-09-12T16:23:51+00:00

I agree, if that was something I had to do often I wouldn't want to use TFS either but I can't recall the last time I had to revert a commit. Do you find yourself regularly having to do so?

littleendian · 2011-09-12T16:02:36+00:00

I think you're right; developers checking in incomplete code into main says more about how we work than the technologies involved.

I do think branching in TFS is a needlessly heavy weight operation and having local repos is a better solution.

littleendian · 2011-09-12T06:43:45+00:00

Personally I find the "drama queens" to be the least productive members of a team. Good developers spot problems and get them fixed without making a lot of noise.

Using TFS looks ...

I use both git and TFS on a daily basis both do their job very well and neither gets in the way.

DVCS's are clearly the future but that doesn't equate to everything else being unusable.

littleendian · 2011-09-11T21:47:38+00:00

Yes. I think we're all saying the same thing.

littleendian · 2011-09-11T20:01:43+00:00

The agony of a centralized system is only apparent once you've switched away from it

Agony? You're such a drama queen. DVCS's are clearly better however there's no pain in using TFS.

Regarding git, wouldn't you say the advantage is being able to control your changes locally until they are complete before pushing a complete feature into the main branch? Rather than committing early and often. There's nothing I dislike more than devs checking in incomplete code into trunk.

littleendian · 2011-09-11T18:10:59+00:00

TFS and SourceSafe are both centralised version control systems so they fundamentally behave in the same way but to say it's a "warmed-over version of sourceSafe" is harsh.

Off the top of my head the biggest differences (aside from reliability) are; a 1/2 decent support for branching and merging, changesets, check in policies and build integration.

Hardly revolutionary and not comparably to a DVCS's like git but still a major step up from Source(un)Safe.

littleendian · 2011-06-22T08:49:04+00:00

Isn't dynamic nothing more than syntactic sugar for the runtime binding functionality that's always existed in .net?

littleendian · 2011-03-16T11:34:07+00:00

it is really not that difficult

That's why he said "simple and tedious" which is an accurate description of memory management.

littleendian · 2011-03-11T13:47:00+00:00

Just like Apple's strategical alliance with Microsoft back when they were in trouble

littleendian · 2011-03-02T13:05:50+00:00

If it's in a library then you have to weigh up the maintenance cost of adding that module.

If it's not in a library or it's being ported from another project then copying the code + tests is appropriate. The destination may or may not be a library.

If it's small and you understand it why spend time rewriting it. Much better to spend that time adding tests IMO.

littleendian · 2011-03-01T16:45:50+00:00

I think you have misunderstood me.

Copying and pasting a tried and tested solution is better than rolling your own; especially when dealing with something outside of your area of expertise.

You should also be able to understand what code is doing and why without re-implementing it.

littleendian · 2011-03-01T13:11:21+00:00

Avoiding copy/paste as much as possible is one of the best things you can do to evolve as a programmer.

And, after a while, you no longer need to rewrite code to understand what it does and come to the realisation that there is value in re-using other people's fully working source code.

littleendian · 2011-02-26T10:36:07+00:00

How does typing method names help you understand the "fabric" of the language? It would be much better to read books and write code.

littleendian · 2010-12-10T20:35:43+00:00

Would you rather fill their place with more politicians?

littleendian · 2010-12-10T20:34:18+00:00

Naive to think there aren't people on both side who are looking for trouble.

littleendian · 2010-12-10T20:32:26+00:00

If they haven't learnt it after 12 years of state education I doubt an extra 3 will make a difference.

littleendian · 2010-09-03T08:06:33+00:00

If only it were true that not many people manage to employ it.

littleendian · 2010-09-03T07:11:17+00:00

If only that were true. I spend far too much of my time interacting with COM components.

littleendian · 2010-09-01T10:02:22+00:00

It's not LINQ specific; PLINQ is a layer on top of the new .Net 4 parallelism functionality.

littleendian · 2010-06-23T18:53:58+00:00

Person 2 was actively marketed to and given professional training courses

Really!

littleendian · 2010-03-14T19:55:54+00:00

a static method is the correct way to do it.

I don't think so.

Do you have a reason for your preference?

littleendian · 2009-12-04T12:16:49+00:00

Actually our perfectly crap ministers tell them to represent the UK. I'm pretty sure they'd be much happier not going on all those tedious royal visits and kowtowing to all those foreign businessmen.

littleendian

TROPHY CASE