Why Everyone else writes bad code

31
ColdFusion Summit 2016

Transcript of Why Everyone else writes bad code

Page 1: Why Everyone else writes bad code

ColdFusion Summit 2016

Page 2: Why Everyone else writes bad code

Dan Wilson…

I’ve done lots of: • Open source• Start ups• Troubleshooting• Project Rescue

Currently:• Product Marketing for NativeScript• NCDevCon• Various conference boards

Page 3: Why Everyone else writes bad code

What is NativeScript?

Page 4: Why Everyone else writes bad code

https://www.nativescript.org/

https://www.nativescript.org/

Open source framework for building truly native mobile apps with Angular, TypeScript or JavaScript.

@nativescript

Page 5: Why Everyone else writes bad code

For Example:

MeWatt

MeWatt™ is a revolutionary ‘appliance to mobile’ device that provides near real-time energy monitoring and analysis of your home appliances’ energy usage. It’s simple and fast to install.

Your MeWatt™ continuously collects and analyzes the energy usage, providing you with actionable recommendations and alerts so you can take control of your home’s energy consumption, reduce your carbon footprint, and save money.

Page 6: Why Everyone else writes bad code

Let’s define the problem

Page 7: Why Everyone else writes bad code

I don't write bad code, my co-workers do!

Page 8: Why Everyone else writes bad code

Misunderstanding the problem

Surfing – You are doing it wrong

Page 9: Why Everyone else writes bad code

Misunderstanding the solution

Page 10: Why Everyone else writes bad code

Misunderstanding the tools

Bluetooth – You are doing it wrong

Page 11: Why Everyone else writes bad code

Common approaches to writing code

Page 12: Why Everyone else writes bad code

One approach to writing code

Eating – you are doing it wrong

Page 13: Why Everyone else writes bad code

One approach to writing code

Page 14: Why Everyone else writes bad code

One approach to writing code

Page 15: Why Everyone else writes bad code

One approach to writing code

Page 16: Why Everyone else writes bad code

One approach to writing code

Page 17: Why Everyone else writes bad code

What can the world of construction teach us?

Page 18: Why Everyone else writes bad code

Proper communication is key

Page 19: Why Everyone else writes bad code

Just get it done

Page 20: Why Everyone else writes bad code

Of course it’s secure

Page 21: Why Everyone else writes bad code

But why do we do these things?

Page 22: Why Everyone else writes bad code

Distracted

Page 23: Why Everyone else writes bad code

Cognitive Overload

Page 24: Why Everyone else writes bad code

Cognitive Overload

Page 25: Why Everyone else writes bad code

Tunnel Vision

Page 26: Why Everyone else writes bad code

Bad code example, in English

Quick ROIImplementing a physical activity intervention in the work-site including goal setting, public tracking of performance data, weekly meetings, educational tools, and incentives increased physical activity 113% by week 12.

Page 27: Why Everyone else writes bad code

Bad code example, in English

Quick ROI

Physical activity intervention tools show payoffs in as early as 3 months.

Page 28: Why Everyone else writes bad code

Show the code

Page 29: Why Everyone else writes bad code

Thank you!

Page 30: Why Everyone else writes bad code

Thanks! Fill out your surveys!

Twitter: @DanWilson

Web: Nodans.com

Work: NativeScript.org

Conference: ncdevcon.com

Page 31: Why Everyone else writes bad code

Thank you!