Slides for my session on the Microsoft Hacks Hackathon on How to code efficiently. Session on 2017 March 25.

1. Bruno Capuano
@elbruno
#MSFTHacks

2. Bruno Capuano
Innovation Manager
@elbruno
http://www.elbruno.com

3. 0#

9. You probably don’t know
how to tie laces

10. 1#

11. Most popular technologies
http://stackoverflow.com/research/developer-survey-2016#technology-most-popular-technologies

12. Most loved technologies
http://stackoverflow.com/research/developer-survey-2016#technology-most-loved-dreaded-and-wanted

13. Changing our tune…
Run on Windows
.NET as system component
Run on VM (CLR)
Black box compilers
Edit in Visual Studio
Proprietary
Run everywhere
Deploy with app
Compile to native
Open compiler APIs
Use your favorite editor
Open source

14. Get the Tools https://www.visualstudio.com/

15. 2#

16. Code process flow … :D
Developer does this #40 times a day
(Linker)

18. 3#

19. Stay in the zone

20. Code process flow … :D
Developer does this #40 times a day
(Linker)
http://roslyn.io
@roslyn

22. Write new features faster
1

23. Tuples
Easily pass around groups of values

24. Pattern matching
Test the shape and content of expressions

25. Local functions
Clean up classes by nesting helpers

26. Provide open source API
2

27. Analyzers identify errors and
provide fixes in your code as
you type, i.e. without having to
wait for a build.

29. Teach new language features/concepts
Introduce best practices for SDK
Enforce code style rules
Identify errors before build

30. Analyzer Ecosystem
FxCopAnalyzers (MSFT):
https://www.nuget.org/packages/Microsoft.CodeAnalysis.FxCopAnalyzers/
SonarLint http://www.sonarlint.org/visualstudio/rules/index.html
StyleCopAnalyzers:
https://github.com/DotNetAnalyzers/StyleCopAnalyzers
CodeCracker https://github.com/code-cracker/code-cracker
Roslynator https://github.com/JosefPihrt/Roslynator
VS Refactoring Essentials: http://vsrefactoringessentials.com/
GCop: https://visualstudiogallery.msdn.microsoft.com/f082f20e-5123-4c0d-
975a-0a17995d858b

31. Productivity
Refactoring support
Navigation/search
Style enforcement
Testing
Better IntelliSense

33. 4#

34. “Yet another” defintion …
Among programmers, yet another (often
abbreviated ya, Ya or YA in the initial part of an acronym)
is an idiomatic qualifier in the name of a computer
program, organisation, or event that is confessedly
unoriginal.[1]
Stephen C. Johnson is credited with establishing the
naming convention in the late 1970s when he named
his compiler-compiler yacc (Yet Another Compiler-
Compiler), since he felt there were already numerous
compiler-compilers in circulation at the time.
https://en.wikipedia.org/wiki/Yet_another
As in "Yet Another AI Group" or "Yet Another Simulated
Annealing Algorithm". If used of others' work, it describes
something of which there are already far too many. In
hackish acronyms the "YA" prefix almost invariably
expands to Yet Another, e.g. YABA, YAUN.
http://www.dictionary.com/browse/yet-another
YAAF – Yet Another Application Framework
Yabasic – Yet Another BASIC
Yabause – Yet Another Broken and
Uncomplete Saturn Emulator
Yacc – Yet another compiler compiler
Yacas – Yet another computer algebra system
YACT – Yet another capture the flag team
YACTA – Yet Another CT Analyzer
YaDICs – Yet another Digital Image Correlation Software
YADIFA – Yet Another DNS Implementation For All
YafaRay – Yet another free Ray tracer
Yafc – Yet another FTP client
YAFFS – Yet Another Flash File System
Yafra – Yet Another Framework
YAGO – Yet Another Great Ontology
Yahoo! – Yet another hierarchical, officious oracle[2]
Yakuake – Yet Another Kuake
YAM – Yet Another Mailer, an email client
YAML – Yet Another Markup Language. Later redefined to
YAML Ain't Markup Language, making a recursive

35. Demo  UWP Community
Toolkit 1.3

36. 5#

37. Plan
1 Monitor + Learn
ReleaseDevelop + Test
2
Development Production
4
3
DevOps

38. It starts with an idea – and a plan
how to turn this idea into reality …
Manage work
Develop + Test 1
Plan
Project starts
PlanTrack progress

39. Write Code
Unit Testing
2
Build
Version Control
Build Verification
Release
Once the iteration starts, developers
turn great ideas into features …
Develop +Test

40. Continuous Integration
cspkg

41. Cloud
Load Testing
Integration testing
environment
Automated functional
testing environment
3
Pre-production
environment
Staging
environment
Monitor + Learn
When all tests pass, the build is deployed to testing
environments for each stage in the release process
Release

42. Release Management

43. Learn and understand how users use your app, how it reacts
and quickly fix issues and bugs
Monitor + Learn
4
Monitor
Feedback
Plan the next iteration

44. Monitor and Learn

45. TFS
Develop
Developer Workstation
Team Collaboration
Build&Test
Build/CI
Test
Deploy
Release
Monitor&Learn
Monitor
Microsoft
Ecosystem
Workstations - On-Premises| Hybrid | Cloud Monitoring- On-Premises | Hybrid | CloudALMServices - On-Premises| Hybrid | Cloud
DEV TEST QA
Environments - On-Premises| Hybrid | Cloud

46. Develop
Developer Workstation
Team Collaboration
Build&Test
Build/CI
Test
Deploy
Configuration
Monitor&Learn
Monitor
This graphic shows OSS and partner products that are
integrated with the Microsoft DevOps solution
Mixed
Ecosystem
Release

47. Hackathon Continuous Integration
 It’s just a simple ASP.NET or Node.js web api!
 Considerations:
• CI for dependent services that you own that are
called by the bot
• LUIS, Databases, external APIs
• Put bot configs in Environment Variables or Release
definition to share the same build
cspkg

48. Hackathon Testing
 How do you test a bot?
 Considerations, forget about:
• Auth
• Mocking connector, mocking LUIS calls
• Unit/Functional/Load testing
 https://www.microsoft.com/developerblog/real-life-code/2017/01/20/Bot-Framework-Unit-Testing.html
 https://github.com/Microsoft/BotBuilder/blob/master/CSharp/Tests/Microsoft.Bot.Sample.Tests/AlarmBotTests.cs#L91
 https://github.com/Microsoft/BotBuilder/tree/master/CSharp/Tests/Microsoft.Bot.Builder.Tests/Scripts

49. Hackathon Cont. Deployment
 It’s just an ASP.NET or Node.js web api!
 Considerations:
• CD for dependent services that you own that are called by
the bot
• Updates and retraining of LUIS models and other
intelligent systems
• Bot state
• Functional/performance tests

50. Thiago Almeida & Donovan Brown
(18 min video on Channel 9)
https://channel9.msdn.com/Series/DevOps-for-the-Bot-
Framework/Continuous-Deployment-and-Release-Management-for-
the-Bot-Framework

51. 1. Visual Studio 2017 & Visual Studio Code
2. Interactive Window
3. Get the most of Visual Studio 2017!
4. Don’t do a “Yet another …”
5. Think on DevOps for Bots

52. Q&A

53. Bruno Capuano
Innovation Manager
@elbruno
http://www.elbruno.com