Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Full Skill Developer - Was ein Entwickler außer Coden noch können sollte

Full Skill Developer - Was ein Entwickler außer Coden noch können sollte

Fast alle von uns haben im Studium oder in der Ausbildung mal Programmieren und die Grundlagen der Informatik gelernt. Damit hat die Reise begonnen. Es gibt ständig neue Programmiersprachen, Paradigmen, Frameworks usw. Aber das ist bei weitem nicht alles. Was brauche ich als Entwickler in einem agilen Team oder einem DevOps-Team? Welche Methodiken muss ich drauf haben? Was bedeutet es, ingenieurmäßig Software zu bauen? Wie baut man ein Produkt?

Konstantin versorgt seine Kollegen seit Jahren mit Antworten auf diese Fragen und wird sie auch vor euch ausbreiten.

Konstantin Diener

October 26, 2017

More Decks by Konstantin Diener

Other Decks in Programming


  1. #coding „Truth can only be found in one place: the

    code.“ Robert C. Martin Clean Code: A Handbook of Agile Software Craftsmanship
  2. Abelson and Sussman „Programs must be written for people to

    read, and only incidentally for machines to execute.“
  3. Martin Fowler „When you feel the need to write a

    comment, first try to refactor the code so that any comment becomes superfluous.“
  4. Eagleson's Law „Any code of your own that you haven't

    looked at for six or more months might as well have been written by someone else.“
  5. Clean Code „No matter how slow you are writing clean

    code, you will always be slower if you make a mess.“ Uncle Bob Martin http://www.informit.com/ShowCover.aspx?isbn=0132350882
  6. @DocOnDev „Boyscout rule for coders - leave the code in

    the better state than you found it.“
  7. @sarahmei „Asking permission to refactor is like asking your homeowner’s

    association if you can vacuum your living room.“
  8. Bram Cohen „The mark of a mature programmer is willingness

    to throw out code you spent time on when you realize it's pointless."
  9. @BenNadel “Write code that’s easy to delete, not easy to

    extend.” … is one of the best pieces of programming advice I’ve ever read.
  10. Doug Linder „A good programmer is someone who looks both

    ways before crossing a one-way street.“
  11. #technology „...because Google/Spotify/Netflix does it" is not a valid reason

    for new tech strategy. Understand situation and context.“ @matthewpskelton
  12. Ron Jeffries „When we use a language, we should commit

    ourselves to knowing it, being able to read it, and writing it idiomatically.“
  13. Jedes neue Framework bringt nicht weniger Probleme, sondern neue. Für

    die alten Probleme kenne ich allerdings schon eine Lösung.
  14. Martin Fowler „Whenever you are tempted to type something into

    a print statement or a debugger expression, write it as a test instead.“
  15. @maaretp „As a tester I don't break your code, I

    break your illusions about your code"
  16. @DocOnDev „If you've skipped unit tests because you plan to

    refactor the code soon, you might not understand refactoring (or unit tests).“
  17. nach meinem Studium • Java 1.2 • Struts 1 •

    EJB 2.1 • XDoclet • Spring 1! • Applets • Blackberry API • JBoss 3 • JAXB • RMI • Borland JBuilder • Borland Delphi • Lotus Script • aspektorientierte Programmierung
  18. hinkley on Hacker News „I tell all the junior Devs:

    if you aren't horrified by something you wrote a year ago, you aren't learning fast enough. 20 years in and I still find things I wrote 8 months ago that I would not do again.“
  19. @ceejbot „A very tiny percentage of our industry works on

    genuinely hard algorithmic problems & on research. Most of us concatenate strings all day.“
  20. Jacques Tati „Wer sich zu groß fühlt, um kleine Aufgaben

    zu erfüllen, ist zu klein, um mit großen Aufgaben betraut zu werden."
  21. Kent Beck "Do it right and you won't have to

    do it over". Yeah, until "right" changes. And it always changes.
  22. Antoine de Saint-Exupéry „Perfektion ist nicht dann erreicht, wenn es

    nichts mehr hinzuzufügen gibt, sondern wenn man nichts mehr weglassen kann.“
  23. Andy Hunt „No one in the brief history of computing

    has ever written a piece of perfect software. It's unlikely that you'll be the first.“
  24. Andrew Hunt & David Thomas, The Pragmatic Programmer „Great software

    today is often preferable to perfect software tomorrow.“
  25. Patrick McKenzie „Every great developer you know got there by

    solving problems they were unqualified to solve until they actually did it.“
  26. Steve Yegge „Programmers have no idea how good (or bad)

    they are at programming. In fact, we all think we're pretty darn good at it.“
  27. The Ten Commandments of Egoless Programming 1. Understand and accept

    that you will make mistakes. 2. You are not your code. 3. No matter how much “karate” you know, someone else will always know more. 4. Don’t rewrite code without consultation. 5. Treat people who know less than you with respect, deference, and patience.
  28. The Ten Commandments of Egoless Programming 6. The only constant

    in the world is change. 7. The only true authority stems from knowledge, not from position. 8. Fight for what you believe, but gracefully accept defeat. 9. Don’t be “the coder in the corner.” 10. Critique code instead of people – be kind to the coder, not to the code.
  29. @techDonaldTrump „I will build a great, great wall between dev

    and ops. I will make ops pay for that wall!“
  30. @noidi „Having a dedicated DevOps person who does all the

    DevOpsing is like having a dedicated collaboration person who does all the collaborating.“
  31. Ops Tools • Shell • Linux/Unix Operating Systems • Database

    • Network • Cloud Platforms • Container Technologies (Docker etc.) • Cluster (Kubernetes etc.)
  32. #teamwork „To be a computer programmer does not mean to

    live in isolation and solitude, but rather the exact opposite.“ Kathryn Barrett
  33. @caradoxical „It's like the old Indian saying: If you want

    to go fast, go alone. If you want to go far, go together.“
  34. @math_rachel „15 min rule: when stuck, you HAVE to try

    on your own for 15 min; after 15 min, you HAVE to ask for help.- Brain AMA“
  35. @jasongorman „Don't think of pair programming as 2 people doing

    the work of one. Think of it as 2 people avoiding the rework of 7.“
  36. @johanneslink Traditional Pairing: „I have an idea. Give me the

    keyboard“. Strong Pairing: „I have an idea. Here, take the keyboard“ Will try next time.“
  37. Seymour Cray „The trouble with programmers is that you can

    never tell what a programmer is doing until it’s too late.“
  38. Marissa Mayer „Beyond basic mathematical aptitude, the difference between good

    programmers and great programmers is verbal ability.“
  39. @listrophy „The two hardest things in Computer Science are: People,

    and convincing others that "People" is the hardest thing in Computer Science.“
  40. Kent Beck „The craft of programming begins with empathy, not

    formatting or languages or tools or algorithms or data structures.“
  41. @flowchainsensei „Almost nothing in software development is as useful as

    developers that empathise with the users’ pains and jobs to be done.“
  42. Individuals and interactions over processes and tools Working software over

    comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan
  43. @tottinge „If your "agile team" has individual work assignments, I

    suspect it is neither "agile" nor „team“."
  44. Steve Smith „Software developers fail in two ways: either we

    build the thing wrong or we build the wrong thing.“
  45. John Cutler „Here’s some advice to developers. Take continuous improvement

    into your own hands. Don’t rely on a manager or a Scrum Master. Take pride in doing it right.“
  46. @neil_killick „The best way to have potentially shippable, working software

    at Sprint end is to *continuously* have potentially shippable, working software“
  47. Du bist Student und hast Lust, mal bei uns reinzuschauen?

    #AgileStudentsDay Dann komm vorbei zum #AgileStudentsDay und lerne uns und unsere Arbeit kennen! 9. November ab 14 Uhr bei cosee
  48. Nächster Talk … Lightning Talks 30. November 2017 > blog.cosee.biz

    > talks.cosee.biz > @coseeaner > #coseetechtalks