11/14: Software Engineer, db-central GmbH 09/11 - 10/11: Research Assistant, Mobile Human-Computer Interaction Group, Universität Duisburg-Essen 06/11 - 09/11: Research Associate, Computing Department, Lancaster University 11/10 - 05/11: Research Assistant, Pervasive Computing and User Interface Engineering Group, Universität Duisburg-Essen 05/11 - 05/11: Visiting Researcher, Telekom Innovation Labs, Technische Universität Berlin Alexander Müller - Wer ist das? (Auszug) 2
processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan
to satisfy the customer through early and continuous delivery of valuable software. Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage. Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale. Business people and developers must work together daily throughout the project. Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done. The most efficient and effective method of conveying information to and within a development team is face-to-face conversation. Working software is the primary measure of progress. Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely. Continuous attention to technical excellence and good design enhances agility. Simplicity--the art of maximizing the amount of work not done--is essential. The best architectures, requirements, and designs emerge from self-organizing teams. At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.
presentation has been shutdown to prevent damage to your mind. The problems seems to be caused by sleeping audience. WAKE_UP_OR_YOU_MISS_THE_GOOD_PARTS If this is the first time you’ve seen this Stop error screen, reopen your eyes. If this screen appears again, follow these steps: Check to make sure any previous slide is properly understood. If there is new information, ask your speaker for any information you are struggling with. If problems continue, disable or remove any outdated knowledge. Disable special memory options such as alcohol or sleep deprivation. Technical information: *** STOP: 0xDEADBEEF (0xCAFEBABE, 0xBADC0DED, 0xC001D00D) Bessere Software
Es wird ein gescheites Versionskontrollsystem benötigt. (Git und Mercurial eignen sich besonders gut.) Der Branch wird zurückgeführt, sobald die Entwicklung an dem Feature abgeschlossen ist. Schritt 2: Branching
die Verantwortung für die Qualitätssicherung. Voraussetzung für den Merge von Branches (Teil 2): Code muss von anderen Mitgliedern des Teams geprüft worden sein.
alexandermueller
muehara
sonoda_mj
hponka
zozotech
morshoto
yosshi_
kuniteru
layerx
techtver
vividtone
codmoninc
honyanya
kneath
akademiya2063
asonas
michielstock
keavy
danielanewman
techseoconnect
panda_program
aleyda
codingconduct
holman
bermonpainter
