@unclebobmartin OK. Understood. It took me a while before I start using some of these "enhancements" and I don't feel comfortable with some others . Not sure if I know all of them ๐ . But I have the impression you can still keep your habits.
@mcflyDev Just discovering Kubbo. FYI, there's a display issue on Galaxy S24 at least. Continue button is unclickable.
I tried to send you a PM but I don't have a premium account.
@unclebobmartin@RPK_ Those who see themselves as "coders" and fear AI may be missing what SwEng really is. Code is the visible tip. The work is understanding problems, designing solutions, making trade-offs, delivering value. AI let us build more, better, and do projects once deemed too $$.
@karomancer@IndieGamesCafe Fun!
https://t.co/hfCvF5GXL4
Luckily AI were not existing the time I met my wife. With such a description, geeking with no reference to interpersonal relationship, I 'd be single today ๐
@KinglishMr@LaPestaNegra@KaiXCreator Butโฆ their god is the same as yours and the same as muslims. Or are you saying there are multiple gods ?Just asking
@megasaetopoulos @niedermuller47@tomek_builds@KaiXCreator This should answer your question by giving a huge hint on his ยซย leftย ยป definition . On top of that probably undereducated and for sure with no knowledge nor understanting of Europe and itโs cultural diversity. World is black and white, good and evilโฆLife is so simple. Lucky hum
State management discussions often focus on packages.
Bloc vs Riverpod.
Provider vs Cubit.
Hooks vs ChangeNotifier.
That usually misses the real problem.
Most state management issues come from:
- unclear ownership
- rebuild propagation
- business logic inside UI
- duplicated derived state
- uncontrolled async flows
The package rarely causes the architecture drift.
The boundaries do.
I put together some Architecture Notes on Flutter state management fundamentals, the tradeoffs between common approaches, and the production pitfalls that tend to appear over time.
#flutter #dart #softwarearchitecture #mobiledevelopment #softwareengineering #flutterdev #bloc #riverpod #reactiveprogramming #programming
@jaeholeeeee@Zinny_Edmund These segregations between Architect,BE and FE dev is quite new (appeared 10y ago?) and is a non sense. Sw eng are all of that. And coding is the easiest part. Thanks to AI, we'll finally go back to real value of Sw eng : build softwares, whatever it is, whatever the stack.
@RaoulBitemboi@nalinrajput23 I guess you're not running any backend. My system needs to handle 15 dockers for services, 2 IDEs, browser, mobile device simulators, RDBMS. 64gb is a bit short but it works. My M4 128gb is what I need for comfort.