@dmitryrechkin I actually like your philosophy, and I often follow the same rule myself. 😄
In the real world, that is, not through the lens of Twitter arguments.
So if a security vulnerability goes unnoticed and nobody contacts support, does that make it correct behavior? :)
I agree that every change carries risks, but the absence of complaints isn't the same as correctness. That's exactly why we need requirements, not just tests that preserve existing behavior.
@omikhan4901@kentcdodds The bigger problem is that the agent might remove both the function and its tests because it decides the functionality is no longer needed.
Now CI is green, all tests pass, and you've silently lost a feature. That's why tests alone aren't enough.
@LukeParkerDev@LukeParkerDev glad I found you and followed. Used to write most of my projects in C# as well, so a lot of it hits home. Warms the soul a bit.
At university, my academic supervisor used to say that documentation and tests are useful when they’re written by people with enough experience to have learned from their mistakes and know which problems are worth preventing.
With AI, it’s easy to end up with tests that simply capture the code’s current behavior, even when that behavior doesn’t match the requirements. The same goes for documentation: you can quickly churn out Markdown files that bloat the context and need constant updating.
I prefer concise diagrams in .puml: they’re text that both people and AI can read, and in my experience, they often describe a system more clearly and compactly than pages of prose. UML is the best notation, in my opinion. And just look at the notation they taught me at university: IDEF0. I often scare my programmer friends with it.
@suat_tw@Damianships@peteralexbizjak Let's be honest: the only real "win" here is if you're already a Flutter dev who wants to avoid learning web tech. Calling a compromise "good for web" just because you already know Dart isn't an engineering argument — it's personal convenience.
So Flutter Web is "good enough" for a narrow use case like internal dashboards. Fair enough. But why would a web developer choose Flutter over React or Vue, which already have mature ecosystems, established tooling, and ready-made solutions for pretty much everything an admin dashboard needs? What exactly does Flutter Web bring to the table that makes it worth choosing over them? 🤔
@suat_tw@Damianships@peteralexbizjak And what about SEO? Even the Flutter team recommends using HTML or Jaspr for SEO-focused websites instead of Flutter Web. 🙃
Borrowed the gradient idea from @itssotsot and made my own T3 Code theme 🎨
I also fixed the thing that always trips me up: the usage limits. I'm used to seeing how much of my session I've "used", not how much I have "left", so I flipped it.
@theo, if you'd ever consider adding a toggle for this, I'd be incredibly happy 🙏
The link to the theme is below
Borrowed the gradient idea from @itssotsot and made my own T3 Code theme 🎨
I also fixed the thing that always trips me up: the usage limits. I'm used to seeing how much of my session I've "used", not how much I have "left", so I flipped it.
@theo, if you'd ever consider adding a toggle for this, I'd be incredibly happy 🙏
The link to the theme is below
@brandontroberts This is definitely a change for the better. It feels like people are finally starting to think for themselves again, and I love seeing actual technical discussions instead of endless arguments about whose AI is better at generating UIs or building games this week.
What about mobile developers, especially those working on iOS? Xcode and the iOS Simulator require macOS, so moving the entire development workflow into a Linux container isn't really an option.
And containerization isn't a silver bullet either. If malicious dependencies can access mounted secrets or host directories, or end up executing during native builds on the host, you're still exposed.
Isolation reduces the attack surface, but it doesn't eliminate supply chain risks. Proper permissions, secret management, and controlling what code gets executed matter just as much.
@hot_town The problem isn't useState, it's how the state is modeled.
A discriminated union with useState solves the same issue without introducing a reducer.
useReducer is great for complex transitions, but it's not a replacement for proper state modeling.