I've started updating my article on Dart & Flutter best practices.
Do you like the new version of build methods?
https://lazebny.io/flutter-best-practices/
Do you like the new version of build methods?
https://lazebny.io/flutter-best-practices/
π₯17β€3π3
  Many of us have struggled with legacy code. It's not the most pleasant thing to do, is it :)?
Typically, in such systems, things are not well understood, there are many dependencies, and a change in one place can have non-obvious effects in others.
To minimize these problems, there is a well-known approach called the Strangler Fig Pattern.
I found an interesting article from Shopify Engineering Team where they talk about the application of this method:
https://shopify.engineering/refactoring-legacy-code-strangler-fig-pattern
  
  Typically, in such systems, things are not well understood, there are many dependencies, and a change in one place can have non-obvious effects in others.
To minimize these problems, there is a well-known approach called the Strangler Fig Pattern.
I found an interesting article from Shopify Engineering Team where they talk about the application of this method:
https://shopify.engineering/refactoring-legacy-code-strangler-fig-pattern
Shopify
  
  Refactoring Legacy Code with the Strangler Fig Pattern - Shopify
  There are strategies for reducing the size and responsibilities of large objects. Hereβs one that worked for us at Shopify, an all-in-one commerce platform supporting over 1M merchants across the globe.
π4π₯3
  I have fully updated the #bestpractices article with new structure and clarifications. Hope you'll like it!
In the meantime, im working on article about #errors handling. This will be interesting as well.
  
  In the meantime, im working on article about #errors handling. This will be interesting as well.
Michael Lazebny
  
  Dart & Flutter best practices
  Best practices for Flutter and Dart. Architecture, state-management, testing, QA, accessibility, UI/UX, BLoC.
β€8π₯3π2
  Starting in one hour!
Today we will finish the auth logic (refresh, sign out) and I will tell about changes made behind the scenes - migrations, gorm, atlas and docker-compose.
https://www.youtube.com/watch?v=EBB3M23C0Lc
  
  Today we will finish the auth logic (refresh, sign out) and I will tell about changes made behind the scenes - migrations, gorm, atlas and docker-compose.
https://www.youtube.com/watch?v=EBB3M23C0Lc
YouTube
  
  Stoic Way #5 - Finishing auth logic
  Today we will add refresh and sign out logic. I will also tell about all the changes made behind the scenes :)
β€4π4π₯3
  Article about exceptions coming on Friday.
π₯10π5π3β€1
  I am considering a new approach to my articles. I plan to introduce two subscription levels: Bronze and Silver. 
Bronze ($8) will provide early access to all articles (by default, each article will be published with a delay of 2 weeks to a month). New articles will be published every week.
Silver ($15) will provide access to exclusive (premium only) articles. These articles will be published once or twice a month and will contain detailed code reviews, approaches, and deep dives into aspects.
All tiers will have a "free" period of 3 days.
With the help of monetization, I believe I will have more opportunities to create and improve content.
Any ideas/hints/suggestions to share? thanks.
Bronze ($8) will provide early access to all articles (by default, each article will be published with a delay of 2 weeks to a month). New articles will be published every week.
Silver ($15) will provide access to exclusive (premium only) articles. These articles will be published once or twice a month and will contain detailed code reviews, approaches, and deep dives into aspects.
All tiers will have a "free" period of 3 days.
With the help of monetization, I believe I will have more opportunities to create and improve content.
Any ideas/hints/suggestions to share? thanks.
π7π₯3π’2π1π©1
  
  Mobile Tech
Article about exceptions just broke out.  https://lazebny.io/mastering-error-handling/
  
Subscription logic works perfectly :) 
You can sign up and start the free trial and unsubscribe at any time.
Full article will be available in 3 weeks for public access.
You can sign up and start the free trial and unsubscribe at any time.
Full article will be available in 3 weeks for public access.
π₯3π’3π1π₯°1
  Did you know that pub.dev is written entirely in Dart?
https://github.com/dart-lang/pub-dev
(taken from here)
  
  https://github.com/dart-lang/pub-dev
(taken from here)
GitHub
  
  GitHub - dart-lang/pub-dev: The pub.dev website
  The pub.dev website. Contribute to dart-lang/pub-dev development by creating an account on GitHub.
π₯6β€2π2π±1
  Tomorrow we will add Redis database as a session storage!
https://www.youtube.com/watch?v=B44B4Mvw56E
  
  https://www.youtube.com/watch?v=B44B4Mvw56E
YouTube
  
  Stoic Way #6 - Session Storage
  Implementing Redis and sign out logic
π3β€1
  It is a good idea to use https://pub.dev/packages/cronet_http and https://pub.dev/packages/cupertino_http for Android, iOS and Macos.
  
  Dart packages
  
  cronet_http | Flutter package
  An Android Flutter plugin that provides access to the Cronet HTTP client.
π6π€1
  Happy upcoming New Year π² 
Please open Telegram to view this post
    VIEW IN TELEGRAM
  β€17π9π2
  Dependencies initialisation is simplified in a new version of starter.
Now it supports compile-time safety and is a bit easier to implement.
https://github.com/hawkkiller/sizzle_starter/pull/308
  
  Now it supports compile-time safety and is a bit easier to implement.
https://github.com/hawkkiller/sizzle_starter/pull/308
GitHub
  
  refactor: Changed depedencies initialization by hawkkiller Β· Pull Request #308 Β· hawkkiller/sizzle_starter
  Simplified initialization processor
Removed initialization steps and hook
Now dependencies are initialized using a simple method call
Dependencies model doesn't use late initialization anymore
Removed initialization steps and hook
Now dependencies are initialized using a simple method call
Dependencies model doesn't use late initialization anymore
π8π₯6π€1