haha, all of our code is a mess at the bedinning. We just need to be mindful of it and be aware of when it starts to slow us down, then we gotta put some structure in there. But until then, keep it messy!
Came here from @Fireship - one video in and I'm subscribed. Universities should be teaching this stuff, and from my experience at multiple comp sci routes and my daughter's experience doing the same in different universities they are not.
That is a really nice compliment ☺️ thank you very much. I'm happy to hear you find it useful. I post less often now, but I still write about software engineering here. filledstacks.substack.com/ You would like some of the articles if you like this video.
Again a really nice video! However I am still and always have been, struggling with identifying what is actually UI code and what is state code. Maybe a follow up video and short that showcases them/ shows an example would be really helpful!
Thank you. And Did the explanation not help? UI = Code that renders content (Widgets) State = Code that decides what UI to render or which code to run when there's an interaction I doubt a follow-up video of 50 seconds would clear that up. Most likely because the code I'll use is not the code you're working on. Take a single line of code in your file and as, does this code visually appear on the users screen. If the answer it yes it's UI code. If not, then it's not UI code.
The course has this built in from the start. Stacked spilts the UI and State logic from the beginning so we don't have to apply this step during our development. It "naturally" occurs.
I appreciate that. And there are follow ups, in written form on my newsletter/blog. filledstacks.substack.com/ Those are the posts about creating architecture in Flutter. Starting from the second post.
Hey there! Very good video. A suggestion, please add some accompanying visuals with your explanation. It's hard to follow what you are saying with static images.😅
I'm happy that you enjoyed it. It usually takes me weeks to make my videos, I'm trying to make that shorter by using Slides. It's pretty common in presentations. Next video I'll add some better graphics per slide if there's something visual.
Would you consider something like displaying a snack bar after a user clicks a button as state code or UI code? Should that kind of code be at the end of the button's onPressed or moved into the viewmodel file as well?
It depends on how you've separated your codebase. I would say the actual code that shows the snackbar shouldn't be in your ViewModel as it would remove the ability to unit test the viewmodel. Which is the point of separating the UI and State code. If you've wrapped it in a service and using dependency inversion to access it in your ViewModel then that works out fine. The ViewModel stays testable and decoupled from the actual Framework code.
@@FilledStacks I think your architectural mindset is so strong that you don't need it, which makes perfect sense. For someone like me, it helped act as a stepping stone to get me over the line, so I could start explaining it to my team. We come from a lawless Cordova code base so these were big jumps for us. That being said it is pretty boilerplate heavy which is annoying. In future I'll want to do a simpler app with riverpod and compare. BloC discussion aside, this is a great vid! Many thanks from JHB
@@kurtschloesser I can only imagine your pain haha. I spent 8 months working with cordova code bases back in 2014, it was so ridiculous. Yeah, the boilerplate is crazy. The CLI I built for stacked ( stacked.filledstacks.com/ )makes everything so much faster. But, like I always say, use what your mind understands, and imporantly, which you mention as well. Use something you know well enough that you can explain to your team as you scale. I'm happy you enjoyed the video!
I've done that for 4 years on my channel 😁 what happens, from my experience, is that the viewers get fixated on the details of the implementation and cannot grasp the broader concept. My idea was to teach software engineering principles so that after watching one of my videos it can be applied to any project, in any language, using any framework. What I found when I shared this information with actual code is that they get fixated on the actual code. I'll get questions like, "there's a UI overflow exception on the screen, how do I fix it" and the video is about decoupling your state to ensure scalability 😂 This happened for almost every video where I want to explain high level topics. Developers get fixated on my code on screen, and also cannot transfer that to their own code. Still trying to figure out the best way to teach it, but I know by now that when I show specific code the feedback is always "my code is different, how do I do it for mine". The fixation goes to the code on screen, not on the idea.
@@FilledStacks I understand. But the title says "Threat to Flutter Developers" so I thought I would see at least 1 or 2 examples of flutter code. That would have been very helpful. Even a small bad/good example would have been enough to show those mistakes flutter devs make. If you want to create a video for any project/language, please don't mislead with video titles. Cheers.
@MrAmG17 why would threst signify that it has to show Flutter code 🤣 All the information is literally 100% accurate. Your definition of misleading seams spoiled by the nature of unforgiving social media. To make the idea of the video clear. The biggest threat to Flutter developers is that everything in Flutter is written in code. UI and State and business logic. And since the separation of concern software engineering principle is not put at the forefront of Flutter education it means that every single beginner will fall into the same trap of code with mixed concerns and responsibilities. Hence making it "The biggest threat to Flutter developers" Cheers bru 🤜
This is bad advice and just going to result in confused devs writing confused code....100%. The number 1 threat to flutter developers is that Flutter community is rife with the blind leading the blind.
Given your blind belief in your Flawed opinion I can say with confidence that you're completely wrong. Having guided, taught, grown a team of 16 developers, and turned them into valuable developers I'd say my advice is far from wrong. There is absolutely no instructions on how to write your code. All you're saying is "Don't teach developer separation of concerns. It'll confuse them". Which is a pretty dumb statement to make. Everything in Flutter is written in code, the UI included. I can guarantee you that maaaaaaaany developers keep their state, business logic, and application logic with their UI because the mistake is easy to make.
5:09 "You dont' start writing the best solution you can think of.." gem. Made my day, coz my code is kind of mess :)
haha, all of our code is a mess at the bedinning. We just need to be mindful of it and be aware of when it starts to slow us down, then we gotta put some structure in there.
But until then, keep it messy!
Came here from @Fireship - one video in and I'm subscribed. Universities should be teaching this stuff, and from my experience at multiple comp sci routes and my daughter's experience doing the same in different universities they are not.
That is a really nice compliment ☺️ thank you very much.
I'm happy to hear you find it useful.
I post less often now, but I still write about software engineering here.
filledstacks.substack.com/
You would like some of the articles if you like this video.
Again a really nice video! However I am still and always have been, struggling with identifying what is actually UI code and what is state code. Maybe a follow up video and short that showcases them/ shows an example would be really helpful!
Thank you. And Did the explanation not help?
UI = Code that renders content (Widgets)
State = Code that decides what UI to render or which code to run when there's an interaction
I doubt a follow-up video of 50 seconds would clear that up. Most likely because the code I'll use is not the code you're working on.
Take a single line of code in your file and as, does this code visually appear on the users screen. If the answer it yes it's UI code. If not, then it's not UI code.
i look forward to you implementing this in the course
The course has this built in from the start. Stacked spilts the UI and State logic from the beginning so we don't have to apply this step during our development. It "naturally" occurs.
love your videos as a juniour developer i learned lots of new things from you .
thank you for ur awesome videos
Its my pleasure. thank you for leaving such a nice comment. I appreciate it.
Just started following you on Linkedin. Great video. It let me with the impression that there would be a follow up. Is it payed? Udemy?
I appreciate that. And there are follow ups, in written form on my newsletter/blog. filledstacks.substack.com/
Those are the posts about creating architecture in Flutter. Starting from the second post.
I'm excited for the upcoming course. lesgo! :)
That’s great to hear. I’m deep in the edit land now. moving at a good pace. I’m trying to get it done next week for release.
@@FilledStacks lesgo! ^__^
Thank you for the wonderful video sir it is very helpful for me and my team, Thanks again sir
You're very welcome. I'm happy to help.
Awesome indeed
It's the best ❤
Much appreciated ❤. Thanks for leaving a comment.
Hey there! Very good video.
A suggestion, please add some accompanying visuals with your explanation. It's hard to follow what you are saying with static images.😅
I'm happy that you enjoyed it. It usually takes me weeks to make my videos, I'm trying to make that shorter by using Slides. It's pretty common in presentations. Next video I'll add some better graphics per slide if there's something visual.
@@FilledStacks Thanks!
Would you consider something like displaying a snack bar after a user clicks a button as state code or UI code? Should that kind of code be at the end of the button's onPressed or moved into the viewmodel file as well?
It depends on how you've separated your codebase. I would say the actual code that shows the snackbar shouldn't be in your ViewModel as it would remove the ability to unit test the viewmodel. Which is the point of separating the UI and State code.
If you've wrapped it in a service and using dependency inversion to access it in your ViewModel then that works out fine. The ViewModel stays testable and decoupled from the actual Framework code.
your video title has a typo btw i think you ment threat not thread
haha, yes. Absolutely. Thank you. I'll update it now.
This is Quality content 🎉🎉🎉🎉
I appreciate that Ismail! Thank you for watching and leaving a comment.
Hey Dane! on what developer level would the course be? Intermediate?
Just excited for you to create and earn more on it!
Hey, yes. Intermediate.
You have to already know Flutter to benefit from it. I don't explain anything about Flutter specifically.
Clean architecture with bloc is top tier
I have avoided BLoC since the first time I used it 4 years ago. I use MVVM through stacked which we used to build all our client applications.
@@FilledStacks I think your architectural mindset is so strong that you don't need it, which makes perfect sense.
For someone like me, it helped act as a stepping stone to get me over the line, so I could start explaining it to my team. We come from a lawless Cordova code base so these were big jumps for us. That being said it is pretty boilerplate heavy which is annoying. In future I'll want to do a simpler app with riverpod and compare.
BloC discussion aside, this is a great vid! Many thanks from JHB
@@kurtschloesser I can only imagine your pain haha. I spent 8 months working with cordova code bases back in 2014, it was so ridiculous.
Yeah, the boilerplate is crazy. The CLI I built for stacked ( stacked.filledstacks.com/ )makes everything so much faster.
But, like I always say, use what your mind understands, and imporantly, which you mention as well. Use something you know well enough that you can explain to your team as you scale.
I'm happy you enjoyed the video!
People need actual code/architecture example along side explanations not just explaining :)
I've done that for 4 years on my channel 😁 what happens, from my experience, is that the viewers get fixated on the details of the implementation and cannot grasp the broader concept.
My idea was to teach software engineering principles so that after watching one of my videos it can be applied to any project, in any language, using any framework.
What I found when I shared this information with actual code is that they get fixated on the actual code. I'll get questions like, "there's a UI overflow exception on the screen, how do I fix it" and the video is about decoupling your state to ensure scalability 😂
This happened for almost every video where I want to explain high level topics. Developers get fixated on my code on screen, and also cannot transfer that to their own code.
Still trying to figure out the best way to teach it, but I know by now that when I show specific code the feedback is always "my code is different, how do I do it for mine". The fixation goes to the code on screen, not on the idea.
@@FilledStacks I understand. But the title says "Threat to Flutter Developers" so I thought I would see at least 1 or 2 examples of flutter code. That would have been very helpful. Even a small bad/good example would have been enough to show those mistakes flutter devs make. If you want to create a video for any project/language, please don't mislead with video titles. Cheers.
@MrAmG17 why would threst signify that it has to show Flutter code 🤣 All the information is literally 100% accurate. Your definition of misleading seams spoiled by the nature of unforgiving social media.
To make the idea of the video clear. The biggest threat to Flutter developers is that everything in Flutter is written in code. UI and State and business logic. And since the separation of concern software engineering principle is not put at the forefront of Flutter education it means that every single beginner will fall into the same trap of code with mixed concerns and responsibilities. Hence making it "The biggest threat to Flutter developers"
Cheers bru 🤜
This is bad advice and just going to result in confused devs writing confused code....100%. The number 1 threat to flutter developers is that Flutter community is rife with the blind leading the blind.
Given your blind belief in your Flawed opinion I can say with confidence that you're completely wrong.
Having guided, taught, grown a team of 16 developers, and turned them into valuable developers I'd say my advice is far from wrong.
There is absolutely no instructions on how to write your code. All you're saying is "Don't teach developer separation of concerns. It'll confuse them". Which is a pretty dumb statement to make.
Everything in Flutter is written in code, the UI included. I can guarantee you that maaaaaaaany developers keep their state, business logic, and application logic with their UI because the mistake is easy to make.