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.

Transcript

1. Full Skill Developer Was ein Entwickler außer Coden noch können sollte Konstantin Diener konstantin.diener@cosee.biz | @onkelkodi
2. @MSFTImagine „Being a good programmer is 3% talent 97% not being distracted by the internet“
3. #coding „Truth can only be found in one place: the code.“ Robert C. Martin Clean Code: A Handbook of Agile Software Craftsmanship
4. Abelson and Sussman „Programs must be written for people to read, and only incidentally for machines to execute.“
5. // Collects all nodes and extrapolates // the tipping point calc();
6. Martin Fowler „When you feel the need to write a comment, first try to refactor the code so that any comment becomes superfluous.“
7. Steve McConnell „Good code is its own best documentation.“
8. Schreibt Code, der keine Dokumentation braucht!
9. 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.“
10. 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
11. @DocOnDev „Boyscout rule for coders - leave the code in the better state than you found it.“
12. @sarahmei „Asking permission to refactor is like asking your homeowner’s association if you can vacuum your living room.“
13. Refactorings
14. // model.addAttribute(„originalFilename“, m.getFn()); // model.addAttribute(„createdAt“, m.getCa()); model.addAttribute("endDate", m.getSearchJobs())); // model.addAttribute(„foundImages“, fn()); model.addAttribute(„markedImageDownloadUrl", getUrl());
15. Bram Cohen „The mark of a mature programmer is willingness to throw out code you spent time on when you realize it's pointless."
16. @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.
17. Ken Thompson „One of my most productive days was throwing away 1000 lines of code.“
18. Wegwerfen lernen
19. Dan Luu „For reliable systems, error handling is more work than the happy path.“
20. Doug Linder „A good programmer is someone who looks both ways before crossing a one-way street.“
21. Fehlerszenerien bedenken
22. #technology „...because Google/Spotify/Netflix does it" is not a valid reason for new tech strategy. Understand situation and context.“ @matthewpskelton
23. @sheysewani "update <filename>" is not a reasonable commit message. It's 2017 folks.“
24. Umgang mit git & Co
25. Ron Jeffries „When we use a language, we should commit ourselves to knowing it, being able to read it, and writing it idiomatically.“
26. Jedes neue Framework bringt nicht weniger Probleme, sondern neue. Für die alten Probleme kenne ich allerdings schon eine Lösung.
27. „Kosten“ von Technologie
28. gemeinsame Technologieentscheidungen
29. Open-Source-Lizenzen kennen
30. #testing „Testing leads to failure, and failure leads to understanding.“ Burt Rutan
32. Martin Fowler „Whenever you are tempted to type something into a print statement or a debugger expression, write it as a test instead.“
33. @maaretp „As a tester I don't break your code, I break your illusions about your code"
34. @DocOnDev „If you've skipped unit tests because you plan to refactor the code soon, you might not understand refactoring (or unit tests).“
35. Test Driven Development TDD: All code is guilty until proven innocent @weiss2go
36. #craftsmanship „Programming is not a science. Programming is a craft.“ Richard Stallman
37. T-shaped T
38. View Business Logic Persistence (ORM) Database
39. 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
40. Katherine Johnson „Know how to learn. Then, want to learn.”
41. 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.“
42. lebenslanges Lernen
43. @ceejbot „A very tiny percentage of our industry works on genuinely hard algorithmic problems & on research. Most of us concatenate strings all day.“
44. 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."
45. Es gibt nicht nur Rocket Science!
46. „If it hurts, do it more often"
47. Continuous Integration
48. Kent Beck "Do it right and you won't have to do it over". Yeah, until "right" changes. And it always changes.
49. Embrace change!
50. Getting Real „It’a problem when it’s a problem“
51. Antoine de Saint-Exupéry „Perfektion ist nicht dann erreicht, wenn es nichts mehr hinzuzufügen gibt, sondern wenn man nichts mehr weglassen kann.“
52. kleine Lösungen bauen
53. 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.“
54. Andrew Hunt & David Thomas, The Pragmatic Programmer „All software becomes legacy as soon as it's written.“
55. Andrew Hunt & David Thomas, The Pragmatic Programmer „Great software today is often preferable to perfect software tomorrow.“
56. keine Software für die Ewigkeit
57. Paul Graham „In programming the hard part isn’t solving problems, but deciding what problems to solve.“
58. Fokus! Fokus! Fokus!
59. Albert Einstein „Planung ersetzt Zufall durch Irrtum.“
60. Planen und Schätzen
61. Kent Beck „Autonomy without accountability is just vacation"
62. Alan Perlis „Don't have good ideas if you aren't willing to be responsible for them.“
63. Uncle Bob Martin „We don’t ship shit!“
64. Verantwortung übernehmen
65. Patrick McKenzie „Every great developer you know got there by solving problems they were unqualified to solve until they actually did it.“
66. Mut!
68. 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.“
69. 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.
70. 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.
71. #devops „DevOps ist eine Haltung. Keine Berufsbezeichnung.“ via @AndreasGnyp
72. @techDonaldTrump „I will build a great, great wall between dev and ops. I will make ops pay for that wall!“
73. Werner Vogels „You build it, you run it!“
74. @mipsytipsy "If you have commit rights, you should know how to deploy to production."
75. @noidi „Having a dedicated DevOps person who does all the DevOpsing is like having a dedicated collaboration person who does all the collaborating.“
76. Ops Tools • Shell • Linux/Unix Operating Systems • Database • Network • Cloud Platforms • Container Technologies (Docker etc.) • Cluster (Kubernetes etc.)
77. #teamwork „To be a computer programmer does not mean to live in isolation and solitude, but rather the exact opposite.“ Kathryn Barrett
78. @caradoxical „It's like the old Indian saying: If you want to go fast, go alone. If you want to go far, go together.“
79. @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“
80. Lasst euch helfen!
81. @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.“
82. @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.“
83. Pair Programming
84. Wissen verteilen
85. Seymour Cray „The trouble with programmers is that you can never tell what a programmer is doing until it’s too late.“
86. @mark_barbs „Individuals and interactions over assigning someone a jira ticket without speaking to them“
87. Marissa Mayer „Beyond basic mathematical aptitude, the difference between good programmers and great programmers is verbal ability.“
88. Kommunikation & Transparenz
89. @listrophy „The two hardest things in Computer Science are: People, and convincing others that "People" is the hardest thing in Computer Science.“
90. Feeback geben und annehmen
91. Kent Beck „The craft of programming begins with empathy, not formatting or languages or tools or algorithms or data structures.“
92. Empathie
93. @jasongorman „The most important language a software developer can learn is the one the customer speaks"
94. @flowchainsensei „Almost nothing in software development is as useful as developers that empathise with the users’ pains and jobs to be done.“
95. Sprich die Sprache des Kunden!
96. #agile
97. http://www.globalnerdy.com/2007/11/28/dilbert-on-extreme-and-agile-programming/
98. Individuals and interactions over processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan
99. agiles Mindset
100. @tottinge „If your "agile team" has individual work assignments, I suspect it is neither "agile" nor „team“."
101. Output vs. Outcome
102. Steve Smith „Software developers fail in two ways: either we build the thing wrong or we build the wrong thing.“
103. Denken in Experimenten
104. 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.“
105. Take it, change it or leave it!
106. @neil_killick „The best way to have potentially shippable, working software at Sprint end is to *continuously* have potentially shippable, working software“
107. Continuous Delivery
108. Müssen wir das alles direkt drauf haben?
109. 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
111. Nächster Talk … Lightning Talks 30. November 2017 > blog.cosee.biz > talks.cosee.biz > @coseeaner > #coseetechtalks
112. Richard E. Pattis „Programming languages, like pizzas, come in only too sizes; too big and too small.“