Staying Ahead of the Curve
Download as PPTX, PDF3 likes1,644 views
Trisha Gee discusses the importance of staying updated with new technologies and the risks associated with technological advancements. She outlines various approaches for developers, including creating prototypes, using internal tools, and engaging in user groups to remain competitive in their field. The document emphasizes proactive strategies to avoid premature implementation while ensuring developers are ready to adopt suitable technologies at the appropriate time.
![{
"openStreetMapId": "20980098",
"location": {
"coordinates": [151.2728552, -33.8931988],
"type": "Point"
},
"amenity": "cafe",
"cuisine": "coffee_shop",
"name": "Gloria Jean's"
},
{
"openStreetMapId": "21554712",
"location": {
"coordinates": [151.9519968, -27.5601496],
"type": "Point"
},
"amenity": "cafe",
"created_by": "JOSM",
"cuisine": "coffee_shop",
"description": "The only place in Toowoomba that roasts its own coffee",
"name": "Chipiron Cafe"
},
{
"openStreetMapId": "27653001",
"location": {
"coordinates": [-1.6937433, 53.9043868],
"type": "Point"
},
"addr:city": "Otley",
"addr:country": "GB",
"addr:housenumber": "9",
"addr:postcode": "LS21 3HE",
"addr:street": "Mercury Row",
"amenity": "cafe",
"cuisine": "coffee_shop",
"gluten_free": "yes",](https://image.slidesharecdn.com/stayingahead-150921084446-lva1-app6892/85/Staying-Ahead-of-the-Curve-16-320.jpg)
Staying Ahead of the Curve
- 1. Trisha Gee (@trisha_gee) Developer & Technical Advocate, JetBrains Staying Ahead of the Curve
- 2. or: New Technology is Dangerous, mmmkay
- 6. erm…
- 10. Wait a minute…
- 11. Why?
- 12. For The Business
- 13. Why? •Customisable dashboards •A new market squeezes your downtime window •You’re adding new products to your inventory that don’t fit into your current model
- 15. Now What? •Identify possible technology options, e.g: • HTML5 / JavaScript / JavaFX • DevOps tools / Containers • NoSQL
- 16. { "openStreetMapId": "20980098", "location": { "coordinates": [151.2728552, -33.8931988], "type": "Point" }, "amenity": "cafe", "cuisine": "coffee_shop", "name": "Gloria Jean's" }, { "openStreetMapId": "21554712", "location": { "coordinates": [151.9519968, -27.5601496], "type": "Point" }, "amenity": "cafe", "created_by": "JOSM", "cuisine": "coffee_shop", "description": "The only place in Toowoomba that roasts its own coffee", "name": "Chipiron Cafe" }, { "openStreetMapId": "27653001", "location": { "coordinates": [-1.6937433, 53.9043868], "type": "Point" }, "addr:city": "Otley", "addr:country": "GB", "addr:housenumber": "9", "addr:postcode": "LS21 3HE", "addr:street": "Mercury Row", "amenity": "cafe", "cuisine": "coffee_shop", "gluten_free": "yes",
- 17. Approaches • Spikes / prototypes • Use in non-production code • Build / Deploy / Continuous Delivery Pipeline • Tests • Use in internal tools • Use on a new project or service • Get the experts in (remember to share)
- 18. For The Team
- 19. Why? •Mixed team used to different programming styles •Releases are painful •Databases schema changes take ages •Testing is hard and inconsistent
- 21. Now What? •Identify possible technology / process options, e.g: • Java 8, Groovy • DevOps • NoSQL • Modern Test Frameworks (e.g. Spock, Lambda Behave)
- 23. Approaches •Spikes / prototypes •Use in non-production code • Build / Deploy / Continuous Delivery Pipeline • Tests •Use in internal tools •Skunkworks projects / hack days
- 24. For You
- 25. Why? •I want to have fun •I want a new job •I want to be a Technology Guru in this job •I don’t want to be left behind
- 26. Now What? •Any technology that looks awesome •Buzz words from job adverts •Any technology that is currently (or soon to be) used at work
- 29. Approaches •User Groups •Online courses •Pet project •Join an open source project •Find a project at work •Get a new job!
- 30. Why? • Because you want to
- 31. Being Proactive
- 32. Preventing Premature Implementation •Brown Bags •User Groups •Hack days •Skunkworks •20% time •Conferences
- 33. Risks
- 34. Benefits •Skilled Developers •Ready to adopt the right technology at the right time •Happy Developers
- 36. So What Can I Do?
- 37. Don’t Panic!
Editor's Notes
- #2: Developer Not consultant or contractor Haven’t written a book
- #3: What I’m going to tell them
- #4: Live coding, turning existing code into (more complicated) Java 8 code
- #5: 30 lines of code
- #8: Show a performance test of using parallel vs not using it
- #11: New != better
- #12: Step back for a minute to think why we want to learn new technologies Three main motivations for learning or wanting to implement new technologies
- #13: There’s a problem that can’t be solved (or not easy) with your existing tech/methods
- #19: Identify a problem that’s hurting the team productivity (e.g. testing) Rarely gets prioritised in the backlog, rarely get the time but it saves you time
- #21: Two problems: - Testing more than one thing (not structured) - Maps are ugly in Java
- #22: Test frameworks help enforce better practice
- #24: Pretty much sam as bus
- #25: Most interesting for us Hear about something and you want to play with it Antipatterns - CV-driven-development; mortgage-driven-development; lets turn this into a framework What do you want?
- #26: Joy Fear
- #27: You have the most choices in this area IoT - fun, cool, applicable? Reactive, docker, Microservices
- #30: If you’re learning for you, or for your career, you’ll have to invest your own time Many people have a single pet project they re-implement So many options, so many directions
- #31: Not fear Not because work wants you to And if it’s because you want a better job, that’s still down to your desires
- #32: Why can’t businesses be more like us? If your company wants to make sure the right technologies are chosen at the right time, try up-skilling the team before the problems Hackdays/skunkworks; 20% time; conferences; user groups; brown bags;
- #35: Your up skilled developers up and leave
- #38: Identify why you want to learn it. If it’s for you, play, don’t work If you think it’s useful for work, identity what for and select appropriate approaches Don’t get attached to a technology If it’s not right, move along
- #40: Selecting is beyond the scope of this talk Have given examples of some safe, non-production ways to learn & trial technologies No - Don’t be afraid to try another. Not a waste. Is learning. Is preventing mistakes Yes - Try some other approaches and gradually spread learning/adoption
- #41: Live code example of the new lambdas (in this case, it means NOT using them)