8. September 2010, 09:42, by Silvan Mühlemann
Recently a friend of mine had his first day of work with a new employer. The company was famous to be very employer-friendly. Surprisingly, my friend experienced the opposite: When he came, his boss was not around. No one told him what he had to do. An initial training was not announced. And when he wanted to go to lunch, he found himself alone in the office. He just felt lost at his new workplace. Bad start.
(more…)
13. October 2009, 16:33, by Steven Varco
Wieder mal ein Tipp aus der Linux-Admin Trickkiste. 
In diesem Fall ging es darum ein System komplett auf ein anderes zu klonen. Sind die beiden Systeme baugleich, ist das mit dd und ssh relativ einfach einfach möglich.
Dazu müssen zuerst beide Systeme mit einer Linux-BootCD (z.B. sysrescuecd) gebootet- und das Netzwerk konfiguriert werden.
Dann gibt man auf dem Quell-System einfach:
quelle~ # dd if=/dev/sda | ssh root@zielsystem "dd of=/dev/sda"
ein und wartet bis der Vorgang abgeschlossen ist. Wer sich noch einen Status des Kopiervorganges anzeigen lassen möchte:
ziel~ # kill -USR1 $(pgrep '^dd$')
-Die Ausgabe erfolgt dabei auf der Konsole vom Quellsystem.
Nach dem Kopiervorgang sollte man das System mounten und die Netzwerk-, sowie Hostname noch anpassen; sonst gibt es danach einen IP-Adresskonflikt im Netzwerk.
Achtung: Dass das ganze klappt sollten beide Systeme (zumindest die Disks) relativ baugleich sein – Und natürlich gehen die Daten auf dem Zielsystem unwiderruflich verloren.
Erweiterungen
Komprimieren: Es wäre nun noch Möglich die Daten durch gzip zu pipen um Bandbreite zu sparen.
Erweiterter Status: Mit pv kann man sich erweiterte Statusinformationen über den Kopiervorgang zusammenbasteln.
22. May 2009, 14:09, by Leo Büttiker
I recently spent some time writing JavaScript code and do reviews of JavaScript features. JavaScript has some nice language features that make it easy to write short and readable code. (On the other hand it is also quite easy to write horrible code with it.) In this article I try to show you how you can refactor your code to something more readable.
We may start with this non-fictional example:
/**
* Returns array of uids of selected items
*/
getSelected:function() {
var returnArray = new Array();
var modelFriendListItems = this.modelFriendListItems.getSelected();
for (var index = 0 ; index < modelFriendListItems.length ; ++index) {
if(!modelFriendListItems[index].isFacebookUser)
returnArray.push(modelFriendListItems[index].id);
}
return returnArray;
},
It’s just one function out of a class that does quite something typical. This function goes over a list of items (iterate) and builds an array out of some of this items (filter). A friend of mine does some ruby coding and in ruby this would look something like this:
this.modelFriendListItems.getSelected().select{|item| !item.isFacebookUser}.collect {|item| item[:id]}
This is quite short and still yet readable. In JavaScript you can go as well in the direction of more functional programming. So let us refactor the JavaScript example above over some iterations. The following examples use prototype.js because this framework extends the JavaScript array with some fancy functions.
(more…)
18. May 2009, 19:39, by Silvan Mühlemann
Because I did not plan to post this article in this blog, it is in German. This should be an exception. Sorry for the English readers.
Die letzte Woche habe ich im Silicon Valley verbracht. Mit einer Gruppe von 12 Leuten haben wir verschiedene Firmen und Organisationen besucht. Hier zähle ich ein paar wild zusammengewürfelte persönliche Eindrücke auf:
- Die zwei heissesten Themen in US-Firmen sind Cloud Computing und Green IT.
- Trotz Green IT ist die durchschnittliche Temperatur im Sitzungszimmer nie höher als 18°. Warme Kleidung ist empfohlen.
- Je niedriger die Temperatur im Sitzungszimmer, desto grösser das Unternehmen.
- Die NASA arbeitet mit Original-Anlagen aus den 50er-Jahren. Gut amortisiert!
- Google ist jene Firma, welche am häufigsten unsere Fragen mit “I cannot comment on that” beantwortet hat.
(more…)
23. April 2009, 10:34, by Riv-Alain Vakili
Regarding the topic “optimizing page-loading-times” too many people still set the focus only on the server-side, ignoring the fact that most of the loading time is spent getting all the components of the page(CSS, JavaScript, images, ads).
The
yahoo performance-team proved this very well.
Also, pages (like tilllate.com) more often make heavy use of JavaScript with the goal of providing a better user experience. The problem is, that most developers work on modern hardware and develop on their favourite web browser – which is usually a recent one. They forget that a big amount of visitors still
surf with their first computer bought 7 years ago at Interdiscount and is mostly surfing on the developers least favourite browser (like IE 6). As a result, those visitors often do not get the optimal user-experience and the website loses traffic (=money).
The conclusion out of this is:
- We have to optimize our page following yahoo’s findings.
- We have to optimize our JavaScript-execution.
Where to start?
Most of our traffic is generated through the photo album. We analyzed and improved following use-case in terms of loading-speed and responsiveness:
User comes to homepage…
…goes to the a photoalbum…
…clicks through the photos
Tweaks
We then did the following things:
- Reduced HTTP requests needed to load the JavaScript files: from 45 to 1-2 requests by merging the multiple files into a single one.
- reduced file sizes of CSS- and JavaScript files by using yui-compressor
- reduced amount of external scripts (like Google Analytics) or load them after everything else to reduce the dependency on third party hosts
Also with the photo album being a JavaScript app we went through the code and implemented the following improvements:
- reduced DOM-operations
- reduced amount of written code by refactoring
- found and removed some common memory leak-patterns
- removed fancy fading-effects as they were useless and took a lot of CPU time
The results
For example on IE7
(50% of our users are using it) we had following improvements:
- time loading and set up the photoalbum decreased from 4.8 to 2.9 seconds
- time switching between thumbnailpages decreased from 1.3 to 0.3 seconds
- the general loading/parsing-time of JavaScript decreased from 1,2 to 0.6 respectively 0.5 to 0.3 seconds (Firefox).
Once we released the tweaks, the pageviews per visit increased by 20%.
a video of someone having a babyare you ready to have a baby
pregnant, How do you get baby must haveswhen you get pregnant
31. March 2009, 21:41, by Silvan Mühlemann
Are you enthusiastic about web technologies? Do you have strong PHP, Javascript and SQL skills? Would you like to work with a team of smart and passionate people? Are you open to advanced development methodologies like Scrum or Test Driven Development? Would you like help further develop one of the biggest Swiss website?
Then you should apply for a job at tilllate.com: Our team is looking for dedicated web developers. You’ll find more information in our job ad:
17. March 2009, 23:33, by Silvan Mühlemann
Four weeks have passed since the last sprint planning meeting. Sprint number two has come to an end. It’s time for the sprint retrospective.
The motivation for the sprint retrospective is:
- Visualize the accomplishment – important for the team morale
- Review any impediments and discuss measures on how to avoid them in the next sprint
Here’s how we are structuring the sprint retrospecives:
The set up
The team and the product owner are allocating one hour in the meeting room. We’re looking at the wall with the task board showing the user stories, the burn down chart and the impediment backlog. This is a big paper with a post it for every impediment encountered during the sprint. We collected the impediments during the bi-weekly scrum meetings (aka daily scrum).
Visualize the achievements
First, I go through all done user stories and say a few words about every story. Time for praising the team. Developers often think “we haven’t achieved anything”. So it’s important to visualize the finished user stories.
(more…)
1. March 2009, 13:43, by Silvan Mühlemann
I recently had to take over an unfinished project. It was an AJAX control to select multiple friends as you can find it on Facebook.
“It’s 99% complete”, I was told. Yeah, right. I counted 2 story points (without looking at the code). Soon I knew I was too optimistic: Classes calling other classes without logic. Randomly named variables. Data, creation of DOM elements, AJAX calls spread all over the place:
Architecture before refactoring (dramatized)
That’s not going to be easy. To make things worse: I am a Javascript beginner. What I did up to now was procedural Javascript code.
(more…)
16. February 2009, 23:14, by Silvan Mühlemann
The first sprint is done! Yes we finally started doing Scrum at tilllate.com*. Well, it’s not exactly how Schwaber and Sutherland would expect it. But our way fits our team. And the acceptance in both the IT team and the rest of the organization is high. It improves motivation and therewith the performance of the team. And that’s what matters.
Sprint planning meeting
(more…)
