Sorry Norman but it is. With a quality Management System following to IEC/DIN/ISO 9001 you CAN definitely measure your product quality. Something we do every day in development for example. There it starts. The need of measuring the quality parameters. And that Xojo is never doing. Without a QMS you have no chance to get informations like that. I am using mostly Systems which are covered by a quality Management System. Documented quality and stadards which are used. Like IEC 62304 for medical Software. Or the 25010 Standard. This standard allows you the quality measuring for your Software product. Or the 270001 Standard for Information security Management Systems. And many, many more. Not working following to the standards is a real problem. Even for Xojo.
Copying buttons from a tab panel to another tab panel
I love Go’s ‘compatibility promise’. Changes in the language shall not affect existing code. They’ve gone out of their way in several recent changes to ensure backwards compatibility yet keep moving the language forward.
Put another way, “First, do no harm.” No one wants to be stuck on a 5 year old version because the newer version breaks existing code. The security implications are staggering.
Xojo has failed miserably at this forever. I don’t see it changing - ever. This is why it’s not a professional (or serious) product.
Development and QMS is not a match made in heaven…
I got stuck being the Quality Director at my company (I was in R&D) and got us through 9001 and 13485 registration - we are biotech BTW…
Initially we were not doing product development only contract manufacturing. While getting the quality system up and getting certification was a lot of work, things mostly came together…
But then we decided to develop our own products… The person in charge of R&D sees the design and Development SOP as an unfortunate formality that is not needed. He tries to do the absolute minimum in terms of documentation and formal planning and the phase reviews… Doing and documenting just bearly enough to get through an audit with our register with an auditor that does not really understand the science (his expertise is in a different area).
- Karen
correct me IF I’m wrong but ISO certifications are “do you make a quality product” but “do you have a process that is well defined”
ie/ is the process well understood, documented, followed, etc
I could make the worst product on the planet and still be ISO certified
Iso 13485 is another animal while the certification is a hard process. Often developers are believing that documentation is not needed. Bad idea. Really bad idea. In case if medical products the process is needed to fulfill the standards beside the iso 13485 like 60601 for medical electrical devices. It is more complex and needs much more attention then iso 9001
Pretty much so for 9001.
13485 is a lot more stringent because it is meant for medical devices, which includes in-vitro diagnostics including reagents.
The R&D and commercialization process has a more controls and need to show data proving performance, as well as for process validation.
- Karen
I suppose if the standards include testing somehow then MAYBE they force you to get better at what you do
I just dont know them to know if that IS part of it
If not then its just a lot of documentation
And it may be about how to produce bad products
But theres a well defined process for it !
And that would NOT be the same as measuring the quality of something
Again quality isnt unit of measure like temperature, speed, mass, etc
Is Go of higher quality than Rust ?
Is Rust of higher quality than C# ?
Thats an assessment that I certainly cant say
Again it is part of the process itself. For a medical device it is for example needed that device software is tested by an external laboratory and not the programmer by self only. It results in better quality
OK so testing IS part of the process
That should, as you note, result in better quality & quality improvement
Xojo could do with that sort of thing
Back to our regularly scheduled topic 