Tips to become a better junior developer

Variable names should indicate the type of data being manipulated.

Action names should describe their purpose and, ideally, their inputs and outputs.

No abbreviations! Contrary to what one might think, the length of names has no impact on performance or the application.

Example:
Use “LineNumber” instead of “LnNumber” for clarity.
Simple, organized logic
the secret to readable code

‍

If the logic becomes complex, comment on it to make it easier to understand.

Beware of repetition:
If you reuse an action, give it a suitable name for each use instead of just adding a “2.”

‍

Create folders to group actions that affect the same type of data.

Group screens that use the same entities to make navigation easier.

‍

Make sure all screens follow the same layout.

Use a common theme and explicit classes to standardize buttons, titles, etc.

‍

Less is more!

If a screen contains too many features, it becomes counterintuitive.

Limit the actions on a single screen to improve the user experience.

‍

Ask yourself:
“Will this feature be needed elsewhere in the application?”

Create reusable actions and use blocks to duplicate features or interfaces on different screens.

This saves valuable time for future developments.

‍

Don't get stuck on a problem for too long.

Ask a more experienced colleague for advice; this will help you learn faster and move forward efficiently.

‍

When I switched careers during COVID-19 to work in development after working in events, I wish I had known these points to consider from the start.

They will help you structure your approach and avoid common mistakes.

Take the time to apply these best practices from your very first projects!

‍