New direction of Continuous Coding

Monday, Jan 1, 0001| Tags:

What is continuous coding really?

  • feature flags / ab test / cleaning up
  • dark launching / shadowing/ mirror / teeing
  • branch by abstraction
  • multiple systems live / canary / service mesh/ proxies
    • traffic shifting
    • blue/ green
  • strangler pattern
  • always green
  • small changes
  • test isolation
  • write code to be observable
  • smart monitoring ( few metrics)
  • exception tracking - automate test creation
  • different logging patterns.
  • deploy vs release and deployment strategies
  • post release analysis / update code and alerts
  • contract testing
  • isolated integration testing
  • always support the previous configuration
  • chaos engineering - how to write code to survive a broken / overloaded dependency.
  • greenfield / small legacy / startup / mega corp

side topics

  • sustainability
  • 4hrs/day 6/days a week

SO WHAT DO YOU THINK ?

This site is a collaborative effort.
What do you want to see here?
Which articles are lacking or outdated?

Contribute