Nick Flink Lead Dev Tools Engineer

In tuenti we are constantly running scripts. We run them to change the configuration of the site, to update the code on the site and even to check out our current working branch. Having a good scripting framework is obviously important when it comes to automating manual tasks.

Andrzej Tucholka Lead Code Architect

Last Friday, we've had another HackMeUp event in Tuenti. During the day we've had our Engineers twisting their minds around a lot of projects which included (ordered by number of votes). When looking at awesomeness of those, have in mind that all of those projects are one day stunts!

Andrzej Tuchołka Lead Code Architect

A coding standard for PHP that we use in Tuenti. Enjoy.

Sergio Cinos Architecture Engineer

In the previous article, we discussed how to keep our application state saved in the History, so when the user goes back to a visited page, we can load and display the state the application was in. In most browsers, you can use document.location.hash="#your-state-encoded-as-string" and everything works ok. However, in Internet Explorer 6 and Interner Explorer 7 (IE) this doesn't work. You need to use an IFRAME to save application state in their URL. As we previously saw, in IE, you need to perform a new request if you want to save state in history. You can 'fake' that request using the technique displayed in the previous article, but it doesn't work if you are using 'document.location' to enable cross-domain access (i.e.: iframes from different subdomains).