Skip to content

Generative AI 2025 chapter#4301

Merged
tunetheweb merged 44 commits intomainfrom
generative-ai
Jan 9, 2026
Merged

Generative AI 2025 chapter#4301
tunetheweb merged 44 commits intomainfrom
generative-ai

Conversation

@christianliebel
Copy link
Copy Markdown
Member

@christianliebel christianliebel commented Dec 29, 2025

@christianliebel christianliebel added the 2025 chapter Tracking issue for a 2025 chapter label Dec 29, 2025
@github-actions

This comment was marked as outdated.

@github-actions

This comment was marked as outdated.

@github-actions

This comment was marked as outdated.

@github-actions

This comment was marked as resolved.

@tunetheweb tunetheweb added the writing Related to wording and content label Dec 29, 2025
Copy link
Copy Markdown
Member

@tunetheweb tunetheweb left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we pull the SQL into a separate PR? Both those and the chapter might require some iterations (I've not looked closely yet!) so let's merge them separately.

I see you reuses resource hints hero image for this chapter - good idea! I was wondering how to handle that — I was considering using Generative AI for to create one, but this works just as good.

@christianliebel
Copy link
Copy Markdown
Member Author

Can we pull the SQL into a separate PR? Both those and the chapter might require some iterations (I've not looked closely yet!) so let's merge them separately.

@tunetheweb I moved the queries to the separate PR #4302.

I see you reuses resource hints hero image for this chapter - good idea! I was wondering how to handle that — I was considering using Generative AI for to create one, but this works just as good.

Yes, I think it works surprisingly well! 😊

Copy link
Copy Markdown
Member

@tunetheweb tunetheweb left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looking great!

Made some comments, but I'd personally advise reconsidering direct references to figures ("see figure 7.1") and instead present in the context of the test ("see the following figure") as easier to manage, doesn't require a linting override, and less likely to reference the wrong number if a new figure is inserted, or one removed.

Comment thread src/content/en/2025/generative-ai.md Outdated
Comment thread src/content/en/2025/generative-ai.md Outdated
Comment thread src/content/en/2025/generative-ai.md Outdated
Comment thread src/content/en/2025/generative-ai.md Outdated
Comment thread src/content/en/2025/generative-ai.md Outdated
Comment thread src/content/en/2025/generative-ai.md Outdated
Comment thread src/content/en/2025/generative-ai.md Outdated
Comment thread src/content/en/2025/generative-ai.md Outdated
Comment thread src/content/en/2025/generative-ai.md Outdated
Comment thread src/content/en/2025/generative-ai.md Outdated
@github-actions

This comment was marked as outdated.

@github-actions

This comment was marked as outdated.

@github-actions

This comment was marked as resolved.

@github-actions

This comment was marked as resolved.

@github-actions

This comment was marked as resolved.

@christianliebel
Copy link
Copy Markdown
Member Author

@tunetheweb Let me flip the following figures, then we should be good to go.

@christianliebel
Copy link
Copy Markdown
Member Author

@tunetheweb I've flipped the figures and removed the "(see figure below)" references. However, I've kept the big numbers after the relevant sections in the text, hope this is fine.

@tunetheweb
Copy link
Copy Markdown
Member

@tunetheweb I've flipped the figures and removed the "(see figure below)" references. However, I've kept the big numbers after the relevant sections in the text, hope this is fine.

SGTM! It's highlighting something you've already mentioned, so is different to presenting the data.

Good to merge then?

Comment thread src/content/en/2025/generative-ai.md Outdated
@christianliebel
Copy link
Copy Markdown
Member Author

@tunetheweb Yes, good to merge!

@tunetheweb
Copy link
Copy Markdown
Member

Still a couple of questions on the SQL PR that might slightly change some of the graphs, but let’s merge this and can update later if needs be.

@jcmpagel
Copy link
Copy Markdown
Member

jcmpagel commented Jan 5, 2026

will look throught the comments tomorrow and run some again just incase

@tunetheweb
Copy link
Copy Markdown
Member

I think most of them are just SQL formatting nits. But the date one might lead to slightly different (smoother?) graphs. And the AI one might change numbers slightly.

Let’s hold off for one more day then.

@github-actions
Copy link
Copy Markdown
Contributor

github-actions bot commented Jan 9, 2026

Images automagically compressed by Calibre's image-actions

Compression reduced images by 23.9%, saving 5.3 KB.

Filename Before After Improvement Visual comparison
src/static/images/2025/generative-ai/genai-ai-domain.png 22.0 KB 16.8 KB 23.9% View diff

22 images did not require optimisation.

@tunetheweb tunetheweb merged commit 1f58236 into main Jan 9, 2026
10 checks passed
@tunetheweb tunetheweb deleted the generative-ai branch January 9, 2026 13:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

2025 chapter Tracking issue for a 2025 chapter writing Related to wording and content

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Generative AI 2025 🆕

4 participants