Why should Dartpad be part of your DevOps tools? To show and teach, obviously! It’s somewhat easier to report framework SDK issues in front-end SDKs by using a tool that runs the code so that the dev team can see the wrong behavior captured.

The other sets of reasons have to do with how we learn. Let me state some background and then get into why we need to cycle back-and-forth between tight-coupled feedback and loose feedback as DartPad is loose feedback to those not aware that it is.

Background

The problem is while Google does an excellent job at giving you an introduction to widgets; it’s not the techniques you really need to have mastered to develop a professional application and in a mature market. That is my self-assigned job in pushing out medium articles and my flutter design and development book series.

I am finding that by showing the cool visual and animation that I can get you guys and gals to do the boring DEVOPS and OOP and FP to get you to the point for flutter expert. Some subjects covered are:

DevOPS

Flutter Expert IDE Set Up  https://medium.com/geekculture/flutter-expert-ide-set-up-25791ce690c

Tuning A Cheap MS Windows Laptop for Flutter Development  https://medium.com/p/tuning-a-cheap-ms-windows-laptop-for-flutter-app-development-572d09cd4d19

Log Driven Learning Flutter  https://medium.com/codex/log-driven-learning-flutter-d76b49b75a8c

UML Coolness in Flutter  https://itnext.io/uml-coolness-in-flutter-6bb14217b5f2

#dart #devops #flutter #software-engineering