96 lines
3.1 KiB
YAML
96 lines
3.1 KiB
YAML
uuid:
|
|
- value: 2530ef2e-0df9-4364-8e08-5d872cd9621e
|
|
langcode:
|
|
- value: en
|
|
type:
|
|
- target_id: daily_email
|
|
target_type: node_type
|
|
target_uuid: 8bde1f2f-eef9-4f2d-ae9c-96921f8193d7
|
|
revision_timestamp:
|
|
- value: '2025-05-11T09:00:18+00:00'
|
|
revision_uid:
|
|
- target_type: user
|
|
target_uuid: b8966985-d4b2-42a7-a319-2e94ccfbb849
|
|
revision_log: { }
|
|
status:
|
|
- value: true
|
|
uid:
|
|
- target_type: user
|
|
target_uuid: b8966985-d4b2-42a7-a319-2e94ccfbb849
|
|
title:
|
|
- value: 'What is legacy code?'
|
|
created:
|
|
- value: '2024-03-20T00:00:00+00:00'
|
|
changed:
|
|
- value: '2025-05-11T09:00:18+00:00'
|
|
promote:
|
|
- value: false
|
|
sticky:
|
|
- value: false
|
|
default_langcode:
|
|
- value: true
|
|
revision_translation_affected:
|
|
- value: true
|
|
path:
|
|
- alias: /daily/2024/03/20/what-is-legacy-code
|
|
langcode: en
|
|
body:
|
|
- value: |
|
|
<p>How do you define legacy code?</p>
|
|
|
|
<p>Is it code written by previous Developers who worked on the codebase?</p>
|
|
|
|
<p>Is it code you wrote last week or last month?</p>
|
|
|
|
<p>Is it code for features everyone no longer uses?</p>
|
|
|
|
<p>Is it the "old" part of the application that no one wants to work on?</p>
|
|
|
|
<p>It is any code that's not nice to work on or difficult to change?</p>
|
|
|
|
<p>Is it code written with different conventions to your current ones or in a different style?</p>
|
|
|
|
<p>Is it any code that doesn't have automated tests or wasn't written with test-driven development?</p>
|
|
|
|
<p>Is it code built with outdated tooling or frameworks (like CSS libraries) that were popular then but have since been replaced by something newer?</p>
|
|
|
|
<h2 id="here%27s-the-thing">Here's the thing</h2>
|
|
|
|
<p>These are just some of the potential definitions I can think of.</p>
|
|
|
|
<p>The term "legacy code" and others, such as "technical debt", often mean different things.</p>
|
|
|
|
<p>What's your definition? Reply and let me know.</p>
|
|
|
|
|
|
format: full_html
|
|
processed: |
|
|
<p>How do you define legacy code?</p>
|
|
|
|
<p>Is it code written by previous Developers who worked on the codebase?</p>
|
|
|
|
<p>Is it code you wrote last week or last month?</p>
|
|
|
|
<p>Is it code for features everyone no longer uses?</p>
|
|
|
|
<p>Is it the "old" part of the application that no one wants to work on?</p>
|
|
|
|
<p>It is any code that's not nice to work on or difficult to change?</p>
|
|
|
|
<p>Is it code written with different conventions to your current ones or in a different style?</p>
|
|
|
|
<p>Is it any code that doesn't have automated tests or wasn't written with test-driven development?</p>
|
|
|
|
<p>Is it code built with outdated tooling or frameworks (like CSS libraries) that were popular then but have since been replaced by something newer?</p>
|
|
|
|
<h2 id="here%27s-the-thing">Here's the thing</h2>
|
|
|
|
<p>These are just some of the potential definitions I can think of.</p>
|
|
|
|
<p>The term "legacy code" and others, such as "technical debt", often mean different things.</p>
|
|
|
|
<p>What's your definition? Reply and let me know.</p>
|
|
|
|
|
|
summary: null
|
|
field_daily_email_cta: { }
|