Menu
News
All News
Dungeons & Dragons
Level Up: Advanced 5th Edition
Pathfinder
Starfinder
Warhammer
2d20 System
Year Zero Engine
Industry News
Reviews
Dragon Reflections
White Dwarf Reflections
Columns
Weekly Digests
Weekly News Digest
Freebies, Sales & Bundles
RPG Print News
RPG Crowdfunding News
Game Content
ENterplanetary DimENsions
Mythological Figures
Opinion
Worlds of Design
Peregrine's Nest
RPG Evolution
Other Columns
From the Freelancing Frontline
Monster ENcyclopedia
WotC/TSR Alumni Look Back
4 Hours w/RSD (Ryan Dancey)
The Road to 3E (Jonathan Tweet)
Greenwood's Realms (Ed Greenwood)
Drawmij's TSR (Jim Ward)
Community
Forums & Topics
Forum List
Latest Posts
Forum list
*Dungeons & Dragons
Level Up: Advanced 5th Edition
D&D Older Editions, OSR, & D&D Variants
*TTRPGs General
*Pathfinder & Starfinder
EN Publishing
*Geek Talk & Media
Search forums
Chat/Discord
Resources
Wiki
Pages
Latest activity
Media
New media
New comments
Search media
Downloads
Latest reviews
Search resources
EN Publishing
Store
EN5ider
Adventures in ZEITGEIST
Awfully Cheerful Engine
What's OLD is NEW
Judge Dredd & The Worlds Of 2000AD
War of the Burning Sky
Level Up: Advanced 5E
Events & Releases
Upcoming Events
Private Events
Featured Events
Socials!
EN Publishing
Twitter
BlueSky
Facebook
Instagram
EN World
BlueSky
YouTube
Facebook
Twitter
Twitch
Podcast
Features
Top 5 RPGs Compiled Charts 2004-Present
Adventure Game Industry Market Research Summary (RPGs) V1.0
Ryan Dancey: Acquiring TSR
Q&A With Gary Gygax
D&D Rules FAQs
TSR, WotC, & Paizo: A Comparative History
D&D Pronunciation Guide
Million Dollar TTRPG Kickstarters
Tabletop RPG Podcast Hall of Fame
Eric Noah's Unofficial D&D 3rd Edition News
D&D in the Mainstream
D&D & RPG History
About Morrus
Log in
Register
What's new
Search
Search
Search titles only
By:
Forums & Topics
Forum List
Latest Posts
Forum list
*Dungeons & Dragons
Level Up: Advanced 5th Edition
D&D Older Editions, OSR, & D&D Variants
*TTRPGs General
*Pathfinder & Starfinder
EN Publishing
*Geek Talk & Media
Search forums
Chat/Discord
Menu
Log in
Register
Install the app
Install
NOW LIVE! Today's the day you meet your new best friend. You don’t have to leave Wolfy behind... In 'Pets & Sidekicks' your companions level up with you!
Community
General Tabletop Discussion
*Pathfinder & Starfinder
Unhappy about the VT Announcement.
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="AbdulAlhazred" data-source="post: 5382596" data-attributes="member: 82106"><p>Actually, being somewhat of an expert on this subject, I'm afraid I have to tell you that your notions of what is and isn't possible in the software world are not in line with the actual facts of the situation. There are various ways of defining the complexity of software. Regardless of which measures you use what you will find is that said complexity grows in a geometric fashion as any software incorporates more functionality. Beyond that even the 'simplest' seeming user applications incorporate vast amounts of code indirectly. For instance the Linux kernel includes several MILLION lines of source code. That makes it easily larger than the largest textual works ever written by man. Nobody fully understands these large bulks of code or all of the interactions that can happen. Many of these interactions are extremely rare and cannot feasibly be produced on demand by any testing framework.</p><p></p><p>The upshot is that bugs ALWAYS exist. No piece of software ever written is bug free. In fact there is no known way by analysis to demonstrate that software IS bug free nor to identify where these bugs are. Various practices and processes can improve the reliability of software. All of them are very labor intensive and costly. The general result is that you can reduce and eliminate bugs pretty easily when there are lots of them, but the more work you do the less improvement you get per unit of work. At some point you establish a cutoff where you're say fixing a bug for every N hours of work. You can predict statistically at that point how often errors will show up in use, but you can't predict where they will show up or what they will be.</p><p></p><p>Ergo software will be buggy in proportion both to its complexity and to the amount of money spent on SQA. For a commercial enterprise like WotC the question is only how much is the budget for this activity. </p><p></p><p>Honestly, in my not at all humble because I know about this stuff opinion, the software WotC has produced so far looks pretty much like other fairly young applications which are produced for limited commercial use. They work, they generally do what they are supposed to, and they have a certain number of issues. Nobody LIKES bugs, but they are not something that is a sign of bad development processes. They are simply a result of the finite ability of human beings to understand and test very complex application logic.</p></blockquote><p></p>
[QUOTE="AbdulAlhazred, post: 5382596, member: 82106"] Actually, being somewhat of an expert on this subject, I'm afraid I have to tell you that your notions of what is and isn't possible in the software world are not in line with the actual facts of the situation. There are various ways of defining the complexity of software. Regardless of which measures you use what you will find is that said complexity grows in a geometric fashion as any software incorporates more functionality. Beyond that even the 'simplest' seeming user applications incorporate vast amounts of code indirectly. For instance the Linux kernel includes several MILLION lines of source code. That makes it easily larger than the largest textual works ever written by man. Nobody fully understands these large bulks of code or all of the interactions that can happen. Many of these interactions are extremely rare and cannot feasibly be produced on demand by any testing framework. The upshot is that bugs ALWAYS exist. No piece of software ever written is bug free. In fact there is no known way by analysis to demonstrate that software IS bug free nor to identify where these bugs are. Various practices and processes can improve the reliability of software. All of them are very labor intensive and costly. The general result is that you can reduce and eliminate bugs pretty easily when there are lots of them, but the more work you do the less improvement you get per unit of work. At some point you establish a cutoff where you're say fixing a bug for every N hours of work. You can predict statistically at that point how often errors will show up in use, but you can't predict where they will show up or what they will be. Ergo software will be buggy in proportion both to its complexity and to the amount of money spent on SQA. For a commercial enterprise like WotC the question is only how much is the budget for this activity. Honestly, in my not at all humble because I know about this stuff opinion, the software WotC has produced so far looks pretty much like other fairly young applications which are produced for limited commercial use. They work, they generally do what they are supposed to, and they have a certain number of issues. Nobody LIKES bugs, but they are not something that is a sign of bad development processes. They are simply a result of the finite ability of human beings to understand and test very complex application logic. [/QUOTE]
Insert quotes…
Verification
Post reply
Community
General Tabletop Discussion
*Pathfinder & Starfinder
Unhappy about the VT Announcement.
Top