You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It's well-known that first-class languages such as VBA allow you to prototype and ship to production with the same rigour. But while prototyping every Enterprise™ developer must come across so many ultra disruptive ideas and when time is of the essence, sacrifices must be made. Currently, no language empowers developers in this way!
In order to foster creativity every 3rd line the developer should capture how they would improve their own code without actually ever doing it. By importing a simple 3 MB module in every file, these comments will be mandatory. Additionally their length must be shorter than 5 characters or at least 5 lines long to avoid unnecessary chatter on the codebase, eg:
// TODO fix
or
/* TODO The next person to touch this code should relief the non-disruptive load we are
* putting on our Enterprise™ Block™Chain™ or change the deployment to a Enterprise™
* Block™Chain™ Scalable™ version
* .
* /
Other ideas for the keyword are:
//TODO™
//PASSING-THE-TORCH
//ROOM-FOR-DISRUPTION
Last but not least, on the Premium™ version, these comments are scannable by JIRA so that the Product Owner always has ultimate visibility over the tasks to perform, and with the Platinum™ version, changes of assignees and further comments on the task are written back directly on the source code for the developer to always be aware of the vision the management has for the product.
The text was updated successfully, but these errors were encountered:
It's well-known that first-class languages such as VBA allow you to prototype and ship to production with the same rigour. But while prototyping every Enterprise™ developer must come across so many ultra disruptive ideas and when time is of the essence, sacrifices must be made. Currently, no language empowers developers in this way!
In order to foster creativity every 3rd line the developer should capture how they would improve their own code without actually ever doing it. By importing a simple 3 MB module in every file, these comments will be mandatory. Additionally their length must be shorter than 5 characters or at least 5 lines long to avoid unnecessary chatter on the codebase, eg:
or
Other ideas for the keyword are:
//TODO™
//PASSING-THE-TORCH
//ROOM-FOR-DISRUPTION
Last but not least, on the Premium™ version, these comments are scannable by JIRA so that the Product Owner always has ultimate visibility over the tasks to perform, and with the Platinum™ version, changes of assignees and further comments on the task are written back directly on the source code for the developer to always be aware of the vision the management has for the product.
The text was updated successfully, but these errors were encountered: