Will Auran trainz 2011 ever come out?

[Timbu]

Just asking, will "Auran Trainz 2011" ever come out?

If it comes, I have some ideas too.

 

[tardis626]

It may not be called 2011 (When they announced 2010 they also announced Trainz Simulator X), but there will be a new one commming either this year or next year.


Regards,
phil

 

[Timbu]

Okay, I think they are calling it "Trainz Extreme".

My idea post isn't in Suggestions Boxcar and it was a post. :'(

 

[danny5]

Will i hope they wait tell 2014 then maybe they will get it right the first time without any patches.
Danny5

 

[NikkiA]

Will i hope they wait tell 2014 then maybe they will get it right the first time without any patches.
Danny5

Impossible, software doesn't work like that, bug-free code is (rightly) considered impossible...

As Wikipedia would say:

http://awurl.com/a3agIAf2G

Note that even NASA, who spend a great deal more on methodologies in order to lower bug counts than Auran could even think about spending, cannot achieve bug-free code, and have to settle for around 0.1 defects per 1000 loc.


So no, you won't see a bug-free version of trainz, or any other software, anytime soon.

(*takes off software dev hat*)

 

[NICKEL]

Besides Trainz also does not run on top of a bug free platform either. First you need the base platform to perform flawlessly before what you run will have a chance.

Never Happen !!!!!!!!!!!!!

 

[durhamlass]

So no, you won't see a bug-free version of trainz, or any other software, anytime soon.

(*takes off software dev hat*)

I'm glad to see it's not just me. :wave:

One thing that is often overlooked is that there are now processes and techniques (TDD, Lean etc.) organisations can use to mitigate the impact of defects quite dramatically. Unfortunately they are not practiced by most organisations (and when they are, it's often lip service).

I had my eyes opened several years ago when I started attending one of the software conferences frequented by some rather well known people in our industry, and it's taught me a lot about what you can do to make software development easier and more productive. Believe me it's a breath of fresh air from the more usual industry approach of building a Gantt chart, crossing your fingers and praying!

Personally I don't espouse a rigid approach to quality; more a set of principles with the flexibility to adapt rapidly to changes in requirements etc. The end result is that in the company I work for we maintain a far larger codebase per developer than any I've ever worked in, and with a lower defect count. We don't get zero defects, but we get far less - and fewer regressions - than we did when we were doing things the "conventional" way.

But I digress...