The productivity argument (introduced by AI) kills the incentives for reviewing. It's just cheaper to generate more and more until you're happy, without looking at the outputs!
Would that be more efficient than just building it in the first place?
Somehow developers have been convinced that the future of computing is to leave their computers busy doing something with a swarm of "agents", going to sleep, and then accepting —without reviewing— the garbage output after they wake up the next morning.
My colleague @staltz.com and his team are at it again, working magic with UIs to reduce cognitive load and make security information easier to explore. Excited to see this launched! 💜
It was vibe coded. Get used to it, it's the future!
git commit -m'Did what AI did not, because this is the future'
Solution for Greenland: split into North Greenland and South Greenland. Trump is going to do this anyway, so why not find a compromise where most of the population (southwest-concentrated) remains untouched, while the USA can do their world policing thing in the north.
I can totally relate to this
Would highly appreciate if you can link to some visible work that is nearly all yours, and you're proud of building.
Want to work with me and a number of world-class JS open source developers at @socket.dev protecting ALL open source libraries from supply chain attacks?
We're looking for stellar frontend developers. DM me
For some reason, humans like – and have always liked – anthropomorphized animals.
Doom-scrolling generation looking back at the early 2000s: we were happy, and we didn’t realize it.
AI-slop generation looking back at the doom-scrolling era: we were happy, and we didn’t realize it.
If you ever wonder where did Andre Staltz go
I select "Light Mode" in Tahoe and the header "Appearance" fades away, while the Back/Forward buttons remain in dark mode.
👏
I think spreadsheets as a concept are brilliant. Can you imagine computers *without* them?
They are simultaneously databases and user interfaces. Manipulation is direct: the input is the output. Reactive programming and no need to reason about outdated state or cache invalidation.
Simply brilliant
In before "what browser are you using", this is Google Chrome.
The slop is everywhere. Even Google with infinite budget can't make a dropdown work.
And... it made software less secure
Even the pagination UI is utterly broken in this product. Seriously, vibe coding is one of the worst things that happened to our industry. We were going in a pretty okay direction until AI came along.
It made products worse, programming frustrating and code review miserable.
Slop slop slop slop slop.
I wish AI were anything else than slot machines. Sometimes you win! But mostly you're just busy pulling thay lever over and over again, hoping for the output you want.
Probably gonna cancel this subscription soon.
The audio generative AI simply does not function as advertised. You're offered the possibility of adding a new instrument track, and you can choose an instrument, but the generated audio turns out to (basically always) be a song, not an instrument track. An interesting one! But not what I asked. 😅
I start realizing from the UI that this product is probably for the most part vibe coded. Stuff like: multiple "collapse sidebar buttons" differently styled and conflicting with each other. Which immediately made me lose some respect for the product.
But worse...
So I gave Suno (music production AI) a try and I was mind blown and inspired. It remixed/improved one of my song demos and that gave me fresh ideas for the song.
So within a few minutes, I pulled out the credit card and got the premier plan. Then I'm playing around with it, until...
That was very sophisticated and good, but most of the work was in cycle/dom, which I wouldn't build. I would just use React, much like how cycle/react currently is written. I'd also drop the functional programming because embracing the React ecosystem means those child components are anyway not pure
JSX can burn in hell as far as I'm concerned
Frameworks are opinionated ways of building apps, so I would make those opinions clear and support only one way of working with Cycle.js.
No "flexibility", but a lot of interoperability (via React with its ecosystem).
Good thoughts, and I respect you. But this thread is a good counterexample of what I'd like to build. As soon as a good open source tool comes out, people start asking for support for alternative building blocks (RxJS, xstream, Preact), which quickly dilutes the whole thing.
Because it's the new HTML. No point in competing with it. Too many good React component libraries out there that must be utilized
