Working at Transifex
For all those interested in coming to Transifex, this post is a spoiler of how things are done around here, by sharing my experience working at the joint (Transifex). This post is sharing alot of ground with this, since my last post is referring to the early days working on the joint.
For a developer, some of the most challenging task is to involve with new intriguing technologies. Currently at Transifex, we are quite full with new technologies (and challenges). Some of the cool technologies explored so far (at least by me) can be enumerated briefly into the following list:
- cloud computing
- message passing services (in contrast to the traditional message passing systems/architectures)
- payment systems (paypal, google checkout etc)
- intergration of high availability/performance software (memcached, haproxy, postgresql (replication, mirroring, etc) ) to the existing software infrastructure
Besides the new technologies that usually are researched, every fexian developer is involved to a joint that all of its structures are opensource. No closed source decisions, or decisions, based on pride or other non well-thought-of cause (Of course there are exception to this rule. For instance fex uses mercurial instead of git).
**Full teamplay (Collaboration).
One other important aspect of developer’s life is the provisions of team-play in decision making. In general such collaboration can be defined as “coming together to work toward a common vision.” Such process is intended to move participants away from the traditional definition of power as control or domination and towards a definition that allows for shared authority. This results in greater achievements than would be attained by one man/woman working alone.
Because no company operates in a vacuum, engaging think-tank procedures, like the one described before, in decision making helps eliminating barriers, increasing opportunities for success, enriches the change process, educates related communities about the joint and creates a shared vision that supports systemic change efforts.
Meeting (online or in rl) cool people.
all the time, or never depending on your mentality. Usually a lot of ppl online, fewer in real life.
It’s not an act of randomness the fact that ‘el jefe’** is calling himself chef (:P) ninja in his business card.**
Localization Best Practices for Developers
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.