Write Great Code

Linda Nichols

@lynnaloo

JavaScript

^

What is Serverless?*

* "Serverless" is a catchy, made-up, marketing term.

Kind of like, "Cloud."

What is Serverless?

• Fully-managed services

• Event-driven architectures

• Pay for only what you use

• Focus on applications

• Fewer wasted resources

• Less time writing redundant code

• Support for all* programming languages

• Less concern about infrastructure

• Built-in services and libraries means less code

• FaaS map to microservices

• Faster time to production

It's for Developers!

But there are servers?

Let's Talk About Serverless

and developers

^

Developers Have Lots of Opinions

JavaScript

^

They Love Process and Best Practices

• Favorite editor

• Favorite language

• Favorite frameworks

• Code formatting tool

• Formatting tool for code prettiness

• Real-time static code analysis

• Consistent rules and formatting

Developers Want (need):

Vim

VS Code

Emacs

Atom

IntelliJ

Visual Studio

Eclipse

Notepad

Lint

Prettier

EditorConfig

pylint

eslint

Mechanical Keyboard

Stack Overflow

Java

.Net

npm

nuget

Ruby

CoffeeScript

Python

Rust

TypeScript

yarn

• Pair-programming
• Your opinionated testing framework
• Unit tests
• Integration tests
• Code coverage up to 90%

You Must Test the Code:

Wait, should we have written the tests before the code?!?

• Use opinionated revision control system
• Current popular branching strategy
• Squash those insignificant commits
• Very detailed commit messages
• Branch names match the task

Then Commit the Code:

Github

Gitlab

Visual Source Safe

Bitbucket

Gitflow

Github Flow

Subversion

CodeCommit

GitOps

• Pre-commit hook

• Push the code to a dev branch

• Issue a pull request

• Code analysis and builds are passing

• Make sure all of the tests are passing

• Request a code review

Merge the Code into Master:

Your branch isn't up to date??

Why aren't the tests passing?

Why did you use tabs and not spaces?

Squash those commits!

The linter is failing!

Sometimes, reviewers can be tough.

OK, LGTM. Merged.

Cue the CI/CD Tool:

Travis CI

Azure Pipelines

Gitlab CI

Jenkins

Circle CI

Bamboo

CodeDeploy

Flux

Github Actions

LaunchDarkly

CodeBuild

What about code written for the cloud?

Pre-recorded Demo Time

Unfortunately, no service is fully-managed enough to format, test, and debug your messy code.

So, why do those who hold process so dear, throw it all away when they write code for the cloud?

Because cloud development is new and can be a little scary.

But all of the development practices that we love, still apply in the cloud.

and there are many, many new tools and services to support your process.

My (highly opinionated) Toolset

• Static Code Analysis:  Eslint
• Enforcing Style:  EditorConfig
• Pre-commit Style:  Prettier
• Revision Control:  Github
• Testing:  Mocha
• CI:  Github Actions
• Editor:  VS Code
• Language:  JavaScript
• Cloud:  Azure*

Demo

https://www.github.com/lynnaloo/only-zuul

Who is the best Ghostbuster?

Conclusion

• No-ops does not mean no DevOps
• Online editors != revision control
• Love your linter
• Put your editor to work
• Testing in prod is not testing
• Abstraction is not CI/CD
• Don't abandon what's important

Thank you

Credits

Travis Webb

YOLO Programmer