How to keep yourself up to date with changes in the technology world.
More details: http://trishagee.github.io/presentation/staying_ahead_of_the_curve/
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
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)
Developer
Not consultant or contractor
Haven’t written a book
What I’m going to tell them
Live coding, turning existing code into (more complicated) Java 8 code
30 lines of code
Show a performance test of using parallel vs not using it
New != better
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
There’s a problem that can’t be solved (or not easy) with your existing tech/methods
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
Two problems:
- Testing more than one thing (not structured)
- Maps are ugly in Java
Test frameworks help enforce better practice
Pretty much sam as bus
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?
Joy
Fear
You have the most choices in this area
IoT - fun, cool, applicable?
Reactive, docker, Microservices
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
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
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;
Your up skilled developers up and leave
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
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
Live code example of the new lambdas (in this case, it means NOT using them)