Finally made a programming language where every line is literally an LLM call! 🤖
Not Turing complete = world's safest language (not safe to use)!
Not what this generation asked for, but absolutely what it deserves.
https://t.co/SCyOXt2drt
#programming#ai#rust#vibecoding
I missed the #90s, so I brought the #blink tag back as #webcomponent - Use it with `<bl-nk>Welcome to my homepage</bl-nk>` after adding the script https://t.co/4jVSemZDjD
And don't forget what #drwho said to Sally Sparrow: Don't blink!
Our #coding team has created its own blog! Check out the first #VolocopterDevBlog post for all the info, tips, and tech info you need: https://t.co/8Cb7FPoZ9i Plus, see if you might have what it takes to code right alongside us! https://t.co/EKHxvueFhh
#Volocopter
Old man yelling at things: I think the proposal for the pipe operator |> for #javascript is not supported by how the language works, and will lead to #bugs and hard to debug issues - read why https://t.co/bsxPOOb5Kd
One of the more difficult decisions in software development is choosing between specialised and reusable solutions. Milena, @goosebumps4 and me wrote a short article that may help you decide: https://t.co/kVjd2wYIDF
#pureLit just got it's v2 released! New features include optionally async rendering (no more useEffect for a single fetch), async hooks and component workflows! Never been easier to start with #webcomponents#js - see examples here: https://t.co/pg3qj6b852
Yesterday I shared my new #presentation framework;today, I want to give an example that shows how much more interactive a #slideshow can be if not limited by a tool but only your imagination. See how to write better #code by solving the pathfinder example https://t.co/7BqtJyDyzU
My last few #presentations I created with a self-written tool that you can find here: https://t.co/Dz28YUpJYq
Go and try it: No need to set up anything (no #npm install) to create your #slides; create an #html page and go for it. Brought to you by the power of #webcomponents#js
@kentcdodds@goosebumps4 For my understanding: you think that writing testing-library tests for requirements you have for other teams is to rigid, and the broker to share them is to abstract? Or such approaches in general? How would you solve the problem from the article?
Did your #ui break due to integration issues lately? Our #frontend is getting as decomposed as our APIs. And yet, we lack the tools to have cheap #tests that ensure that we won't break the system. Here's a solution: #contracttests for #js
https://t.co/dLqy2Bf44T
#testing#reactjs