How best can one argue towards a software developer to invest in maintaining maximum compatibility with Autohotkey?

Discuss Autohotkey related topics here. Not a place to share code.
Forum rules
Discuss Autohotkey related topics here. Not a place to share code.
DawOfTheDead
Posts: 8
Joined: 11 May 2019, 04:18

How best can one argue towards a software developer to invest in maintaining maximum compatibility with Autohotkey?

11 May 2019, 20:16

How best can one argue towards a software developer to invest in establishing and maintaining maximum compatibility with Autohotkey?
What kind of quality characteristic of a Software are raised by maximum compatibility with AHK?

Would it not make sense from a marketing perspective to elaborate on these questions and communicate the results to developers via the website?

:)
Last edited by DawOfTheDead on 12 May 2019, 14:22, edited 1 time in total.
DawOfTheDead
Posts: 8
Joined: 11 May 2019, 04:18

Re: How best can one argue towards a software manufacturer to invest in maintaining maximum compatibility with Autohotke

12 May 2019, 14:12

Ok here are some of my thoughts on the two questions. If you have any thoughts I would be so happy to hear them. :)

How best can one argue towards a software manufacturer to invest in establishing and maintaining maximum compatibility with Autohotkey? 
1. It can save money.
2. It raises the quality of your products. See answers to second question below.
3. It makes the products more manageable and maintainable and reduce costs
4. It can generate money if designed and marketed correctly.

Cyclomatic complexity is a software metric used to indicate the complexity of a program. It is a quantitative measure of the number of linearly independent paths through a program's source code. It was developed by Thomas J. McCabe, Sr. in 1976.

Essentially it is fair to say that each line of code that is committed to a source code cost money at the time of creation and even more after that as one has the challenge of evolving and maintaining the sourcecode.

By ensuring maximum scritpibility for your applications, you reduce the strain that new features would put on the source code by making it possible to manipulate the software without actually adding complexity to the source code.

Furthermore it is possible to outsource feature development and workflow tweaks to the community meaning that value is added to your product without you actually paying developers to code.

Unhappy customers with feature requests can in many cases be immidieatly pleased with scripts without them having to wait for release cycles with a high chance that there feature request will never be addressed anyway.

That said once all of the scriptable feature requests are not relevant to the planning of the application development anymore the paid engineers can focus on the things that cant be scripted and need actual implementation in the source code. This means that your application will evolve more efficient and that your engineers can focus on different aspects of the source code like refactoring and further improving scriptability.

What kind of quality characteristic of a Software are raised by maximum compatibility with AHK?
The international standard for software quality ISO 9126 defines the following characteristic for Software quality:
https en.wikipedia.org /wiki/ISO/IEC_9126#/media/File:ISO_9126_quality_(en).svg Broken Link for safety

Starting from the most evident towards the less obvious here are the quality characteristic that I thought where particularly prone to be raised by maximum scriptability.

1. Maintainability:
By making your software particularly scriptable you especially raise the quality of the characteristic maintainability and its sub characteristic analysabillity, changeability, testability and stability.

2. Usability:
By making your software particularly scriptable you especially raise your influence on the quality in the characteristic of uasabillity and its sub characteristic attractiveness, operability, learnability, understandability

An application can be made less complex for beginners and extended with more scripts for and by advanced users. This means that one can design the default first contact user interface for beginners in such a way that they are not overwhelmed by possibilities and guide them with carefully selected GUI elements towards quick results in order to make them fall in love with the experience of using the program. These young beginners will one day be paying customers and contributors to the applications community.

3. Functionality:
By making your software particularly scriptable you especially raise your influence on the quality in the characteristic of functionality and its sub characteristic Suitability. Note that other sub characteristic of functionality are challenged by scriptability like for instance interoperability and security.


:)

Return to “General Discussion”

Who is online

Users browsing this forum: No registered users and 3 guests