Today I will work on user service. I will define general architecture, layers and folder structure in #Golang.

https://www.youtube.com/watch?v=9f8Rgj-GxPo

Started 🙂

Today Google released Gemini!

https://deepmind.google/technologies/gemini

#ai

Added database section to sizzle starter template documentation!

https://sizzle.lazebny.io/storage/database/about/

Some interesting (and hard) questions:

- How does setState result in a new frame?
- What's the rendering pipeline?
- How does repaint boundary work?
- How to implement offline-first?
- What is declarative navigation?
- How do you initialize dependencies?

Working on small, but interesting article about overlays and popups.

It will be about OverlayPortal, OverlayController and other widgets to make alignment & positioning ease.

inspired by this one: https://plugfox.dev/layer-link/

Tomorrow we will build something interesting! Hope to see you there.

https://www.youtube.com/watch?v=blJzdukYZwg

We are starting 🙂

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

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/

Next article will be about exceptions.

- how to handle them correctly
- backend errors
- stacktrace / throwing / rethrowing
- comparison to either

I've recently discovered a cool free font named "Satoshi"

2D scrolling infinite canvas: https://x.com/definev2/status/1735319830641963284?s=46&t=dWA1m7fMpzIgC8FgRKo4XQ

in 2 hours we will continue the development of Stoic Way app.

https://www.youtube.com/watch?v=NyUvvqhBIeA

Amazing motivation.

https://www.youtube.com/watch?v=wUpBrALhlnc

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/

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

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.