Ever heard "We can't do DevOps because of [insert excuse here]" ? This session will expose that lie with a trip back to the 1980’s complete with 8-bit assembly code, a Commodore 64 and bulletin boards. We will walk through an automated delivery pipeline using Azure and Azure DevOps to develop, build , approve and release native C64 code to a real C64. Along the way we’ll look at how to build your own Azure DevOps Extensions and leverage Azure services to help bridge a variety of technical barriers. Experience/relive the glory and horror of 80’s technology and learn to push DevOps even further. Inconceivable!

1. **** AZURE, DEVOPS AND THECOMMODORE 64****
10 PRINT “Todd Whitehead”
20 PRINT “https://github.com/toddwhitehead”
30 PRINT “towhit@microsoft.com”
SO WHAT’S YOUR EXCUSE?

2. People. Process. Products.
What is DevOps?
DevOps is the union of people, process, and
products to enable continuous delivery of value
to your end users.
DevOps is the combination of cultural philosophies, practices, and
tools that increases an organization’s ability to deliver applications
and services at high velocity: evolving and improving products at a
faster pace than organizations using traditional software development
and infrastructure management processes.
https://aws.amazon.com/devops/
https://docs.microsoft.com/en-us/azure/devops/learn/what-is-devops

3. Even if your project or deployment is no-code (like an Office or other SaaS deployment), DevOps practices and tools can help
improve the velocity, functionality and feedback loop for users
Azure DevOps For All
Azure DevOps
Azure Boards
Azure Repos
Azure Artifacts
Azure Pipelines
SaaS PaaS, CaaS & IaaS

4. People. Process. Products.
Why !DevOps?
1. Products
2. Process
3. People
 Our tools aren’t designed for it
 Connectivity is hard/complicated
 Our process is complex

5. CaaS
Container Platform
PaaS
Application Platform
FaaS
Serverless Platform
IaaS
Infrastructure Platform
What
More Control of execution environment
Less Agile development & deployment
Less Control of execution environment
More Agile development & deployment
Patching, Management, Deployment Management (Container & Pod) Limitations of Execution environment Cold start, long running process
Curated VM Hosting Curated Orchestration Curated Execution Environment Scale to ‘zero’
IT/Infra focused Value Prop Dev/App Admin focused Value Prop
Challenges
What you get
Technology decisions

7. Harwell DEKATRON 1947

10. No, not those 80’s

12.  Commodore 64
 Commodore VIC-20
 Commodore PET
 1541 Floppy Drive
 Apple I
 Apple II
 Atari 8-bit family
 Acorn Atom
 BBC Micro
 Ohio Scientific
 Oric
 Atari 2600
 Nintendo Entertainment
System
 Atari Lynx
 Tamagotchi

16. Hello world devops: 80’s style
Display Text | Colour Effects | Music

17. https://www.c64forever.com/
C64, PET 2001, CBM 3032, CBM 4032, CBM 8032, VIC 20, CBM
610, C16, Plus/4, C128 (40-column and 80-column) and more

18. https://ultimate64.com/Ultimate-64
https://shop.pixelwizard.eu

21. Composite
Video
RF
Luminance &
chrominance
svideo HDMI
Audio RCA

26. Dev Tool Chain
https://code.visualstudio.com/
IDE: Visual Studio Code
https://sourceforge.net/projects/acme-crossass/
Assembler: ACME Cross-Assembler
https://azure.microsoft.com/en-us/services/devops/
CI/CD: Azure DevOps

35. https://www.slideshare.net/esug/retrobjects-fun-with-c64-and-nes

38. POKE 1024,1

39. POKE 55296,11

40. https://usborne.com/browse-books/features/computer-and-coding-books/

41. https://usborne.com/browse-books/features/computer-and-coding-books/

48. Demo: Text with Colour Wash

49.  3 Tone Oscillators (Voices)
 4 Waveforms per voice
 Attack Rate
 Decay Rate
 Sustain level
 Release Rate
 Programmable Filter

51. https://www.8-bit-symphony.com/

53. Demo: Adding Sound

54. Assemble
code commit trigger
Compress
Launch

58.  New Azure Pipelines tasks that teams can use in their builds.
 Use dashboard widgets to get custom views within Azure DevOps Services.
 Extend the work item form with new tabs, sections, and actions.
 Create your own hub to embed new capabilities within our Agile, code,
build, and test experiences.

78. https://usborne.com/browse-books/features/computer-and-coding-books/

80. 21:4/100
bbs.castlerockbbs.com:23
21:4/159
bbs.retrodevops.com:23
21:4/109
bbs.foo.com:23
fsxNet

91. Demo: Deploy to Real C64

92. App Developer
Cloud Services
IDE
Data Scientist
[ { "cat": 0.99218,
"feline": 0.81242 }]
IDE
Apps
Edge Devices
Model Store
Consume Model
DevOps
Pipeline
Customize Model
Deploy Model
Predict
Validate&Flight
Model+App
Update
Application
Publish Model
Collect
Feedback
Deploy
Application
Model
Telemetry
Retrain Model
App Developers and Data Scientists

93. Azure IoT Edge Deployment

94. IoT Edge DevOps
VS VS Code VSTS Github Jenkins
Comprehensive DevOps workflow for IoT Edge solution
teams of any size
• Shorten cycle times and deliver IoT solution faster
• Improve quality and availability
• Can be easily adopted with essential tools
Dev tools for IoT Edge for all languages & platforms
• Visual Studio IoT Edge extension (coming soon)
• Visual Studio Code IoT Edge extension
(github.com/microsoft/vscode-azure-iot-edge)
• CLI dev tool (github.com/azure/iotedgedev)
• CI/CD in VSTS, Jenkins and etc.
IoT Edge CI/CD
• Check in IoT Edge deployment
• Distribute to test cluster, run tests
• Deploy to edge devices on successful tests
• Support single + multiple of devices

95. People. Process. Products.
Why !DevOps?
1. Products
2. Process
3. People
 Our tools aren’t designed for it
 Connectivity is hard/complicated
 Our process is complex
1. Products
2. Process
3. People
1. Products
2. Process
3. People