Main

type

5 (blog/news article)

status

21 (imported old-v2, waiting for another import)

review version

0

cleanup version

0

pending deletion

0 (-)

created at

2025-10-27 17:25:25

updated at

2025-10-27 17:25:26

Address

url

https://asamsig.com/blog/infrastructure-as-actual-code

url length

54

url crc

31162

url crc32

2245622202

location type

1 (url matches target location, page_location is empty)

canonical status

30 (canonical url is different, page_canonical_page_id points to it)

canonical page id

2871114696

Source

domain id

122089618

domain tld

2211

domain parts

0

originating warc id

-

originating url

https://data.commoncrawl.org/crawl-data/CC-MAIN-2025-33/segments/1754151280328.73/warc/CC-MAIN-20250811100340-20250811130340-00063.warc.gz

source type

11 (CommonCrawl)

Server response

server ip

76.76.21.21

Publication date

2025-08-11 10:34:55

Fetch attempts

0

Original html size

110232

Normalized and saved size

34303

Content

title

Infrastructure as actual Code (IaaC)

excerpt

content

Infrastructure as actual Code (IaaC)January 19, 202512 minute read#iac#programmingSetting the Scene My first introduction to Infrastructure as Code (IaC) must have been back in 2016. We were exploring AWS for the first time in my team, and we were using CloudFormation with its JSON-formatted templates. I'm pretty sure this was before the YAML-formatted templates were even a thing since that wasn't launched until September 2016. Anyway, as a developer, I'm used to writing code. I follow "best practices", such as Don't Repeat Yourself (DRY), by using variables, methods, and abstracting where necessary. I also try to keep it as easy to read, understand, and maintain as possible. Sometimes, that includes comments in my code, usually to explain the rationale behind certain choices or highlight potential gotchas. Yes, yes, not everything should be abstracted, You Aren't Going to Need It (YAGNI), and all that. Well, you see... The problem with most IaC solutions is that they are actually conf...

author

updated

1762831804

Text analysis

block type

0

extracted fields

233

extracted bits

featured image
title
full content
content was extracted heuristically
OpenGraph suggests this is an article

detected location

0

detected language

1 (English)

category id

Frontend (137)

index version

2025110801

paywall score

0

spam phrases

0

Text statistics

text nonlatin

0

text cyrillic

0

text characters

10944

text words

2296

text unique words

763

text lines

1

text sentences

128

text paragraphs

1

text words per sentence

17

text matched phrases

2

text matched dictionaries

2