85 lines
3.4 KiB
YAML
85 lines
3.4 KiB
YAML
uuid:
|
|
- value: 6433f0ed-d000-473b-8412-c61c8e39a80e
|
|
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:38+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: |
|
|
Too many choices?
|
|
created:
|
|
- value: '2023-07-17T00:00:00+00:00'
|
|
changed:
|
|
- value: '2025-05-11T09:00:38+00:00'
|
|
promote:
|
|
- value: false
|
|
sticky:
|
|
- value: false
|
|
default_langcode:
|
|
- value: true
|
|
revision_translation_affected:
|
|
- value: true
|
|
path:
|
|
- alias: /daily/2023/07/17/too-many-choices
|
|
langcode: en
|
|
body:
|
|
- value: |
|
|
<p>I've recently considered moving my infrastructure automation code from Pulumi to Terraform.</p>
|
|
|
|
<p>One of Pulumi's features is that you can write your automation in a programming language instead of a domain-specific language (DSL) with Terraform.</p>
|
|
|
|
<p>As a Developer, this seems appealing, but it poses an important question - which programming language should you use?</p>
|
|
|
|
<p>I've written and re-written Pulumi code in TypeScript and Python and experimented with Go to see which feels best for me.</p>
|
|
|
|
<p>If one of these were my primary language, it would be a no-brainer.</p>
|
|
|
|
<h2 id="here%27s-the-thing">Here's the thing</h2>
|
|
|
|
<p>When I go into my automation repository, I want to write my code as quickly and simply as possible. I don't want to be thinking about how to write it or what language would be best to write it in.</p>
|
|
|
|
<p>Whilst I'd have to learn another DSL for Terraform, it would simplify my options by removing that choice for me, but also if I write automation code and hand it over to a client.</p>
|
|
|
|
<p>It's like taking my children to a restaurant.</p>
|
|
|
|
<p>They'll get overwhelmed if there are too many options on the menu. If we limit the options or order for them, they won't.</p>
|
|
|
|
|
|
format: full_html
|
|
processed: |
|
|
<p>I've recently considered moving my infrastructure automation code from Pulumi to Terraform.</p>
|
|
|
|
<p>One of Pulumi's features is that you can write your automation in a programming language instead of a domain-specific language (DSL) with Terraform.</p>
|
|
|
|
<p>As a Developer, this seems appealing, but it poses an important question - which programming language should you use?</p>
|
|
|
|
<p>I've written and re-written Pulumi code in TypeScript and Python and experimented with Go to see which feels best for me.</p>
|
|
|
|
<p>If one of these were my primary language, it would be a no-brainer.</p>
|
|
|
|
<h2 id="here%27s-the-thing">Here's the thing</h2>
|
|
|
|
<p>When I go into my automation repository, I want to write my code as quickly and simply as possible. I don't want to be thinking about how to write it or what language would be best to write it in.</p>
|
|
|
|
<p>Whilst I'd have to learn another DSL for Terraform, it would simplify my options by removing that choice for me, but also if I write automation code and hand it over to a client.</p>
|
|
|
|
<p>It's like taking my children to a restaurant.</p>
|
|
|
|
<p>They'll get overwhelmed if there are too many options on the menu. If we limit the options or order for them, they won't.</p>
|
|
|
|
|
|
summary: null
|
|
field_daily_email_cta: { }
|