Journal: Big end Development - What's the point?

So, I'm now involved with a large software development project. It's all very interesting and there's this guy who used to work for IBM who's some kind of systems engineering genius. He's using Rational Rose and MS-Project and tons of other nifty things to outline this huge framework of the software. But... it strikes me that some of the ideas being bandied about are fundamentally flawed. No point in going into it (indeed, I probably can't due to non-disclosure), but can you *really* do a large project in this way and get the same level of quality you once got with the skunk crew programming team and several months of Jolt Cola and Pizza? So far I'm sceptical.

I suppose that time will tell. The only problem with that mantra is that this software is probably going to be my job for the next little while (not writing it, of course, for the owners of the company wish the software to actually work) and I'd be sorely put out if I was getting led down the garden path by this software engineering type. I took several years of University towards a computer science degree and I have *some* clue as to the overall idea behind it. I still hold to the idea that if you haven't got the fundamentals unflawed, you have a biggus problemus.

Rant rant. Like anyone is EVER gonna read this. It's nice to get it on paper, as it were.

Let's one think.