A list of performance tweaks, especiallly relevant to large solutions would help (like mentioned at the end of the previous CAB meeting recording).
Also saving/building takes really long (depending on environment, multiple minutes). How can this be optimized? Maybe better solution/module setup?
It would be nice to have or build a best practices library. I know there are some videos on Servoy universtity but they are hard to find for our typical developer. They should be like really simple code snippets they can look at.Some examples :
How to setup and use modules
How to organize the work space
What are good code/naming conventions
OOP (classes and constructors, inheritance )
How to create abstract code and interfaces
Best way to loop foundsets
Handling big datasets
Best way to design forms in your app (baseforms, inheritance)
We are struggling also to keep our developers up to date with standards and new servoy features. Maybe show these randomly at (optional) tips at startup?
A common pitfall is writing code or create a specific approach that runs very fast on a local developers workspace, but tends to get slow on real client-server environments where network latency and server roundtrips come into place.
What is a best practice for database usage among a development team. Sometimes a central db is preferred, but a local database works a lot quicker and allows better sandboxing. Support for database seeds from developer could be nice. To be able to distribute them even nicer.
Examples and best practices of unit tests.
Speed up delivery of improvements for: continuous delivery/deployment strategy