Dimitris Glezos

Best Practice for Development: Following Schedules

Gantt chart.

It’s been a rather long, slow, but at the end of the day a productive weekend. After talking about it for almost a week, we now have a solid schedule to work and measure ourselves against for the next month.

Why is a schedule important? ‘Cause it helps you remain focused, make positive progress without exhausting yourself, keep your calm when deadlines are approaching, monitor your progress, and see if you are moving towards your goal or away from it. It allows you to focus on the task at hand and at the same time avoid too much focus, something that tends to become a problem with the more pleasant tasks. Most importantly, when the workday comes to an end, it allows you to enjoy a bottle of Belgian beer or a glass of a fine malt Scotch whiskey 🙂

One could go on, but at the end of the day, a good schedule (or a project plan in… management speak) is a must-have tool to meet your goals and not just a convenient nice-to-have, enabling you to make progress in the long run rather than having short outbursts of productivity.

Of course making a schedule is the most easy thing to do. Keeping with it is what requires hard work and dedication, and this is going to be our focus from now on.

Localization Best Practices for Developers

Speaking of productivity while building … we know that a developer’s role in the localization and translation management process can be a difficult one if you don’t have the right workflows in place. To help, we’ve put together a guide highlighting the practices that the best development teams put into place to streamline the localization process — from integrating localization into build cycles to tricks for avoiding string freezes. Download the free guide to learn more.

Want to learn more about Transifex?

Give Transifex a try with our free 15 day trial, or connect with one of our team members for a personal demo.