diff --git a/src/links/2024/2024-05-29-a-common-web-component-learning-blunder.md b/src/links/2024/2024-05-29-a-common-web-component-learning-blunder.md
new file mode 100644
index 00000000..35b19b1c
--- /dev/null
+++ b/src/links/2024/2024-05-29-a-common-web-component-learning-blunder.md
@@ -0,0 +1,7 @@
+---
+title: "A common web component learning blunder"
+date: "2024-05-29T09:51-08:00"
+tags: ["tech", "development", "javascript"]
+description: "Through stalking the #WebComponents hashtag and my Frontend Masters course, I’m privy to a lot of developers’ first experiences with web components. There’s a wide range of people digging in, but the most common first-time experience I come across is a developer coming from a classical component framework like React with JSX going straight to writing vanilla Web Components, becoming frustrated, and then deeming web components 'not ready for primetime.'"
+link: "https://daverupert.com/2024/05/cold-turkey-wont-fix-your-javascript-addiction/"
+---
\ No newline at end of file