Using wavelets and entropy coding to analyze code structure https://lobste.rs/s/8ntcw9 #programming #vibecoding
https://yogthos.net/posts/2026-06-02-wavescope.html
vibecoding
Know thine enemy: A critical engagement with AI-assisted software development via @projectgus https://lobste.rs/s/7ke9cs #vibecoding
https://medium.com/bits-and-behavior/know-thine-enemy-a-critical-engagement-with-ai-assisted-software-development-e41d9b058ab1
The real energy use of agentic AI https://lobste.rs/s/6lml19 #vibecoding
https://www.theclimatebrink.com/p/the-real-energy-use-of-agentic-ai
How to not write parsers https://lobste.rs/s/vzm4hm #haskell #vibecoding
https://crtschin.com/posts/how-to-not-write-parsers
Appearing Productive in The Workplace https://lobste.rs/s/2h8ben #vibecoding
https://nooneshappy.com/article/appearing-productive-in-the-workplace/
Talk more to your coding agents https://lobste.rs/s/4rcwmh #vibecoding
https://www.datawill.io/posts/2026-06-my-agent-workflow/
What I’m Hearing About Cognitive Debt (So Far) https://lobste.rs/s/kriejt #practices #vibecoding
http://margaretstorey.com/blog/2026/02/18/cognitive-debt-revisited/
BattleTris: Two-player networked tetris with a twist https://lobste.rs/s/sg1z79 #retrocomputing #vibecoding
https://github.com/bcantrill/BattleTris
The first known runaway AI agent - or a very bad marketing stunt? https://lobste.rs/s/nsnb4j #vibecoding
https://martinalderson.com/posts/huggingface-openai-exploit/
Three Cultures of Math https://lobste.rs/s/ioiepg #math #vibecoding
https://rkirov.github.io/posts/three-cultures-of-math/
Now more than ever: building reliable software in the age of agents https://lobste.rs/s/8aeoeo #video #practices #testing #vibecoding
https://www.youtube.com/watch?v=rUYP4C29yCw
Chatto is now Open Source https://lobste.rs/s/hufoqf #privacy #release #vibecoding
https://www.hmans.dev/blog/chatto-is-open-source
Language integrated LLMs as an OCaml function via @cryptix https://lobste.rs/s/savxgn #ml #vibecoding
https://anil.recoil.org/notes/language-integrated-llms
Check out my latest #VibeCoding project, "DIY Federated Reader"
https://www.speedofcreativity.org/2025/09/05/diy-federated-reader/
On GitHub: https://github.com/wfryer/federated-reader-bot
#create2learn #AI #MediaLit #edtechSR #edtech #SocialMedia #HealOurCulture #OwnYourFeed
SQLite Does Not Accept Agentic Code https://lobste.rs/s/lc26ar #vibecoding
https://simonwillison.net/2026/May/27/sqlite-agents/
DeepSeek-V4-Flash means LLM steering is interesting again https://lobste.rs/s/wycfiy #vibecoding
https://www.seangoedecke.com/steering-vectors/
Thoughts on AI agents https://lobste.rs/s/gwl8q6 #vibecoding
https://goulven-clech.dev/2026/ai-agents/
RaTeX: LaTeX math renderer in Rust https://lobste.rs/s/qdfbsp #rust #vibecoding
https://github.com/erweixin/RaTeX
Twenty Years of Stacking Commits via @dario https://lobste.rs/s/7nu9cr #vcs #vibecoding
https://julien.danjou.info/blog/twenty-years-of-stacking-commits/
AI is Breaking Two Vulnerability Cultures https://lobste.rs/s/kuhmb0 #security #vibecoding
https://www.jefftk.com/p/ai-is-breaking-two-vulnerability-cultures
What Happens to Software When Proof is Cheap? https://lobste.rs/s/r8epo9 #video #formalmethods #vibecoding
https://www.youtube.com/watch?v=oSHVPvM56sA
If you don’t have the resources to write and understand the code yourself, you don’t have the resources to maintain it either.
Any monkey with a keyboard can write code. Writing code has never been hard. People were churning out crappy code en masse way before generative AI and LLMs. I know because I’ve seen it, I’ve had to work with it, and I no doubt wrote (and continue to write) my share of it.
What’s never been easy, and what remains difficult, is figuring out the right problem to solve, solving it elegantly, and doing so in a way that’s maintainable and sustainable given your means.
Code is not an artefact, code is a machine. Code is either a living thing or it is dead and decaying. You don’t just write code and you’re done. It’s a perpetual first draft that you constantly iterate on, and, depending on what it does and how much of that has to do with meeting the evolving needs of the people it serves, it may never be done. With occasional exceptions (perhaps? maybe?) for well-defined and narrowly-scoped tools, done code is dead code.
So much of what we call “writing” code is actually changing, iterating on, investigating issues with, fixing, and improving code. And to do that you must not only understand the problem you’re solving but also how you’re solving it (or how you thought you were solving it) through the code you’ve already written and the code you still have to write.
So it should come as no surprise that one of the hardest things in development is understanding someone else’s code, let alone fixing it when something doesn’t work as it should. Because it’s not about knowing this programming language or that (learning a programming language is the easiest part of coding), or this framework or that, or even knowing this design pattern or that (although all of these are important prerequisites for comprehension) but understanding what was going on in someone else’s head when they wrote the code the way they wrote it to solve a particular problem.
It frankly boggles my mind that some people are advocating for automating the easy part (writing code) by exponentially scaling the difficult part (understanding how exactly someone else – in this case, a junior dev who knows all the hows of things but none of the whys – decided to solve the problem). It is, to borrow a technical term, ass-backwards.
They might as well call vibe coding duct-tape-driven development or technical debt as a service.
🤷♂️
Edited 160d ago
cursed_browser: A web browser with no rendering engine — the VLM reads the HTML and hallucinates the page https://lobste.rs/s/njcvka #browsers #satire #vibecoding
https://github.com/scosman/cursed_browser