6 tips to become better developer in OutSystems

The main point of development is not just delivering a stable working solution for the issue, but the same time developing “clean” code. It gives you and your team a couple of benefits:

So how you can achieve it?

1 . Follow one naming convention. If your team uses a camel-type naming convention follow it, if your team uses a Pascal one strictly follow the rule.

2. Add a description to all of your objects (tables, actions, modules, blocks, etc).

3. Divide the logic into smaller actions. Avoid creating complex, long logic where you can get easily lost.

In this case, it is recommended or merge into action a couple of logical actions or try to simplify your logic.

4. Add comments. Okay, you can’t simplify your logic, so add comments, and make readable and understandable comments.

5. Don’t add style changes to the widgets directly from the styles tab. In the future, it will be harder to find “that 3px from the bottom” and you can end up with a lot of hours of investigation. Instead, create a style and add it in the Style field.

6. Do not use two or more server actions inside on Client action. It will make slower your processes. Instead, call each Server Action in the Client action separately and merge them into one.

That’s all! Of course, there are more hints for clear coding. Share with them in the comment section =)

Related posts:

As the strategic application of sound and music to a brand to help form an identity. It’s a vital part of a consumer’s sensory experience, as sound, and music in particular, has a direct cognitive…

The Objectifier was designed by Bjørn Karmann a student at the Copenhagen Institute of Interaction Design. It was designed to empower “people to train objects in their daily environment to respond to…

This is a tale of 2 remote controls. It’s also an awesome lesson about effective UX and that newer doesn’t always make it better. Press on (see what I did there?) and learn something about building…