Mobile Tech
1.14K subscribers
91 photos
8 videos
6 files
138 links
Michael Lazebny's blog about @dart and @flutter
lazebny.io
Download Telegram
Mobile Tech
Tomorrow we will build something interesting! Hope to see you there. https://www.youtube.com/watch?v=blJzdukYZwg
Guys, I’d like to ask you for some feedback or suggestions!

What you liked on streams and what you didn’t.

Or maybe, you have some ideas
πŸ‘Œ5
Popups in Flutter the right way!

I'm asking for some feedback - Do you find this article of your interest, is it written in clear language? Thanks!

https://lazebny.io/popups-in-flutter/
πŸ‘11
Next article will be about exceptions.

- how to handle them correctly
- backend errors
- stacktrace / throwing / rethrowing
- comparison to either
πŸ”₯24πŸ‘9
πŸŽ‰
Please open Telegram to view this post
VIEW IN TELEGRAM
πŸŽ‰24πŸ₯°8πŸ‘5🍾3❀1πŸ‘1πŸŽ„1
I've recently discovered a cool free font named "Satoshi"
πŸ‘11❀2
πŸ‘14
in 2 hours we will continue the development of Stoic Way app.

https://www.youtube.com/watch?v=NyUvvqhBIeA
❀6πŸ‘2
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/
πŸ”₯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
πŸ‘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.
❀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
❀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.
πŸ‘7πŸ”₯3😒2πŸ‘Ž1πŸ’©1
Never understood why people do posts like this.

it is easier to complain than to contribute, yeah?
πŸ‘6🀬2
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.
πŸ”₯3😒3πŸ‘Ž1πŸ₯°1