FTP over WWW

Ever had the problem of sitting behind a firewall and no being able to connect to a server via FTP to upload/download something or to update your private site from work? Maybe you should give www2ftp.de a chance, an FTP program via Internet.
And at least they say that they are not interested in any files/passwords and that everything gets deleted immediately after your logout.
I haven't tried it yet, but its nice to know about it. Anyone got already experience with it?

Posted by Karsten at 16:35 | Comments (0) | TrackBack


Longest StackTrace ever on TSS

It seams like TheServerSide.com had a problem but recovered already. It is the longest stack trace I have ever seen in a webpage. It is far too long and I copied it, so you can see it here:
It tells a lot of interesting things about TSS.com. So they use:
Kodo from solarmetric.com

And you can even see the Table structure they have.
Seams like no good errormessage delivered to customers, or?

Posted by Karsten at 22:24 | Comments (4) | TrackBack


Best bug tracker?

What kind of bugtracker do you use in your project?
At Skex/MojoKnows we used Bugzilla and I was very happy with it. The reporting functionality and the integration with CVSMail was great. And I miss it already.
Now at Jato Consulting they had
Mantis, a PHP solution, which looks a bit fancier but lacks some functionality like sendmail integration, CVS integration, etc.
But it might be nicer for clients to report bugs.
And since all the opensource projects can use it, I got a bit in contact with JIRA from Atlassian. I must admit that after getting used to bugzilla that much it is different to use JIRA and I like buzilla better merely for the reason of lazyness.
Do I miss any other good bugtracker?
What are your experiences? What do you prefer/like/dislike?
I already ordered a vserver to play a bit around on a machine with bugtrackers.

Posted by Karsten at 14:35 | Comments (6) | TrackBack


W-JAX: Key lessons day 1

The key lessons at W-JAX Management day have been:

Customers are like girls and therefore they need individual consulting and development in an iterative way.

If there isn’t a SW for a business process but building a SW for the process is to expensiv a lot of companies adjust their business processes to fit a standard as SAP.

Software development is a craft and therefore needs tools. Automated Test, Profiling are some of them.

Posted by Karsten at 18:22 | Comments (0) | TrackBack

W-Jax: Planen, schätzen, korrigieren

Endlich komme ich dazu etwas über die Vorträge der W-JAX​ zu schreiben ( wie angekündigt).
Der Vortrag (Planen, schätzen, korrigieren in agilen Prozessen) von Jutta Eckstein war sehr gut und ich möchte daher hier ein paar der Stichwort wiedergeben:

was kann man messen?
Ein lauffähiges Programm, daher sollte man immer ein lauffähiges Programm haben!

„The larger the team, the shorter the cycles.“

Kunden sind wie Frauen.
Sie haben beide eine vage Vorstellung dessen, was sie wollen. Sie wollen sich erst das Produkt anschauen, probieren und dann ggf doch ganz anders haben.
Wenn eine Frau einen roten Pulli mit V-Ausschnitt haben will, und sie bekommt einen ist sie unzufrieden. Wenn die Frau einkaufen geht, dann kommt sie wieder mit einer roten Bluse und einem schwarzen Pulli sowie zwei CDs.
Wenn ein Kunde ein spezifiziertes SW-System haben will und bekommt es genau so, ist er unzufrieden. Er möchte hier was ändern, dort was umstellen, etc.
Daher ist es für beide Seiten – Kunde und Dienstleister – schlecht einen Festpreis auszumachen. Iteratives, agiles Vorgehen ist gerade für den Kunden besser.

„Plans are worthless. Planning is essential.“ D. Eisenhower

Gold Card: Auszeit für eine Iteration, um sich etwas zu vertiefen und zu lernen.
Aber: Man muss das gelernte am Ende presentieren und alle lernen dadurch.

Posted by Karsten at 18:12 | Comments (0) | TrackBack