Standalone Automation

Questions of the week:?Why are we not using Probench to create scorecard automation but instead using standalone JavaScript pages?

I write this article based on the insight of my conversation with my team in our monthly 1-on-1 call. I speak with each one of my team members. This article is to share the question of this week and our method to work on it. You can subscribe to the Building Our Team newsletter (2800+ subscribers)

Photo by LinkedIn Designer

Why are we not using Probench to create scorecard automation but instead using standalone JavaScript pages?

The primary reason is the constraints of rapid development & getting automation done in under 4 hours. Scripting is the best tool for that. Javascript is the most popular language, too.?

Here are some other reasons:-

1) Experiments happen with quick iteration; if the development and testing cycle takes longer, it's a speed bump. So instead of testing ten ideas in a day, we end up testing only 5

2) The red tape of source control and deployments: Source control is best for teams in big companies with 100 people working on the same 10 million lines of code. It is a bureaucratic trap for a small team, and an idea with 100 lines of code makes deployment a multi-step, multi-person and multi-time task. We have yet to become a million-dollar company.?

3) Impacting the client deliverables if the automation code is alongside the client code, the accidental bugs can disrupt business as usual, and it's a bad service for our existing client

4) Leveraging libraries of JavaScript: We have already used Jquery and Excel, but there are many yet to be used,?like math.js, Simple Statistics, jStat,?stats.js, Papa Parse, Handsontable, Data-Forge, Lodash?etc

5) ChatGPT works fantastic to suggest code in JavaScript and code manipulations?

6) Debugging and testing code in javascript using Developer mode is the most accessible tool ever

7) The JavaScript page doesn't need any login, and it is lightweight & fast-loading (Every minute counts)

8) Because of the flexibility, if we have to change the code or upgrade, it is much easier to do in the current setting

9) Labs where experiments and ideas happen are always messy, and that's the nature of the job. Bureaucratic structure and red tape don't create new products.

10) We can still create the entire scorecard using automation for the starter scorecard in under 5 minutes using existing automation architecture. The output will be many files, including HTML, XML, SQL Scripts, text, etc.?

Innovation?doesn't?look proper?or?fancy at the germination stage.

Its job is to blow your mind when the results happen, and the method will always be different from business as usual. Get used to it.? ?

We will use Probench for integration automation because most?configuration data for Survey, Scoring and Scorecard is loaded, and the data only needs to be moved or reorganised.?

If you liked this, why not share it?