www.codesync.global/media/working-with-legacy-code-gabor-olah

Preview meta tags from the www.codesync.global website.

Linked Hostnames

7

Thumbnail

Search Engine Appearance

Google

https://www.codesync.global/media/working-with-legacy-code-gabor-olah

Working with legacy code

In a world driven by software, sooner or later, everyone needs to develop code left behind by somebody else. In this talk, we discuss what is legacy code, how to understand it, and the required mindset needed to tackle it. Since dealing with legacy is mostly about understanding the code, we provide some ideas of what tools to use on the BEAM platform to ease grokking the legacy system. Through battle stories, we provide examples which challenge the job of future developers, suggesting how to avoid them.



Bing

Working with legacy code

https://www.codesync.global/media/working-with-legacy-code-gabor-olah

In a world driven by software, sooner or later, everyone needs to develop code left behind by somebody else. In this talk, we discuss what is legacy code, how to understand it, and the required mindset needed to tackle it. Since dealing with legacy is mostly about understanding the code, we provide some ideas of what tools to use on the BEAM platform to ease grokking the legacy system. Through battle stories, we provide examples which challenge the job of future developers, suggesting how to avoid them.



DuckDuckGo

https://www.codesync.global/media/working-with-legacy-code-gabor-olah

Working with legacy code

In a world driven by software, sooner or later, everyone needs to develop code left behind by somebody else. In this talk, we discuss what is legacy code, how to understand it, and the required mindset needed to tackle it. Since dealing with legacy is mostly about understanding the code, we provide some ideas of what tools to use on the BEAM platform to ease grokking the legacy system. Through battle stories, we provide examples which challenge the job of future developers, suggesting how to avoid them.

  • General Meta Tags

    13
    • title
      Working with legacy code
    • theme-color
      #ff005f
    • keywords
      Legacy code, software, Erlang, Elixir
    • description
      In a world driven by software, sooner or later, everyone needs to develop code left behind by somebody else. In this talk, we discuss what is legacy code, how to understand it, and the required mindset needed to tackle it. Since dealing with legacy is mostly about understanding the code, we provide some ideas of what tools to use on the BEAM platform to ease grokking the legacy system. Through battle stories, we provide examples which challenge the job of future developers, suggesting how to avoid them.
    • robots
      index, follow

  • Open Graph Meta Tags

    7
    • og:site_name
      Code Sync
    • og:description
      In a world driven by software, sooner or later, everyone needs to develop code left behind by somebody else. In this talk, we discuss what is legacy code, how to understand it, and the required mindset needed to tackle it. Since dealing with legacy is mostly about understanding the code, we provide some ideas of what tools to use on the BEAM platform to ease grokking the legacy system. Through battle stories, we provide examples which challenge the job of future developers, suggesting how to avoid them.
    • og:title
      Working with legacy code
    • og:type
      article
    • og:url
      http://www.codesync.global/media/working-with-legacy-code-gabor-olah/

  • Twitter Meta Tags

    5
    • twitter:card
      summary_large_image
    • twitter:site
      @CodeBEAMio
    • twitter:title
      Working with legacy code
    • twitter:description
      In a world driven by software, sooner or later, everyone needs to develop code left behind by somebody else. In this talk, we discuss what is legacy code, how to understand it, and the required mindset needed to tackle it. Since dealing with legacy is mostly about understanding the code, we provide some ideas of what tools to use on the BEAM platform to ease grokking the legacy system. Through battle stories, we provide examples which challenge the job of future developers, suggesting how to avoid them.
    • twitter:image
      http://www.codesync.global/uploads/media/articles/0001/02/thumb_1198_reference.jpg

  • Link Tags

    4
    • icon
      /assets/img/favicon.93e85b1c.png
    • manifest
      /manifest.json
    • stylesheet
      /assets/global.73570f4b.css
    • stylesheet
      /ckeditor/plugins/codesnippet/lib/highlight/styles/monokai.css

Emails

2
  • ?subject=Working with legacy code&body=Take a look at this: http://www.codesync.global/media/working-with-legacy-code-gabor-olah/
  • [email protected]

Links

26