lily!!!🌸

₊˚⊹♡₊ᴗ₊♡˚⊹₊ |

Into reading, coding, and journaling (｡•̀ᴗ-)✧ | dotnet

[lily!!!🌸 @lorycodes]

learn with me!!

https://t.co/gZKGAZVsHW

[lily!!!🌸 @lorycodes]

Joined the LLM Zoomcamp 2026 by @DataTalksClub!

Over the next 10 weeks, I’ll be building production-ready LLM applications with RAG, vector search, embeddings, AI agents, evaluation, monitoring, and orchestration

Thanks @Al_Grigor and the team for putting this together

[yuu @_soulleater]

i still talk ab u btw

[Avie Fukai 🇵🇭🇯🇵 @AvieDev]

Cheers ladies🙌🌸
Happy International Women’s Day my fellow women in tech👩‍💻
Hope we can get together and do activities together even online.

[lily!!!🌸 @lorycodes]

@AvieDev pan de coco!

[lily!!!🌸 @lorycodes]

@patloeber thats cute

[lily!!!🌸 @lorycodes]

@AvieDev oh nooooo

[lily!!!🌸 @lorycodes]

ill probably post a review after a month. lets see how will the battery performs.

Bought lenovo yoga slim 7i aura edition. the 258v, oled display version. what i love about it is portable and light, i can open it with one hand. #lenovo #yoga

[Milan Jovanović @mjovanovictech]

How does the Cache-Aside pattern work?

1. Check the cache and return the data if it exists

2. If not, fetch it from the source

3. Store the result in the cache for next time

Simple and effective.

This pattern helps you:

• Load data faster using memory
• Reduce pressure on your database
• Scale better with distributed caching

I wrote a quick guide on how to implement this in .NET: https://t.co/kArj1AhGlT

What’s your go-to approach for caching in your apps?

---
Do you want to simplify your development process? Grab my free Clean Architecture template here: https://t.co/pDIEdGkoIa

[✨Leah✨ @LeahTCodes]

Your daily reminder to build/learn in public!

You never know who’s watching or where it'll take you ✨

[Ayda golahmadi @Ayda__gol]

Saturday night.

They’re out partying,You’re here,still creating, still pushing.

Because you know it will pay off.

Keep building.

[lily!!!🌸 @lorycodes]

@lovelacecoding @kc_dc @PragVue_conf @tunisiadevdays safe travels!

[Milan Jovanović @mjovanovictech]

Want to write clean, testable middleware in ASPNET Core?

The easiest way is to make it strongly typed.

You create a class that implements IMiddleware, and put your logic inside InvokeAsync.

But don’t forget two key steps:

1. Register the middleware with the DI container

2. Add it to the request pipeline using UseMiddleware()

This keeps your middleware reusable, scoped properly, and easy to test.

I put together a quick guide that shows exactly how to do it: https://t.co/T05D5nP3M7

Have you tried this approach, or do you still prefer conventional middleware?

---
P.S. Here's a FREE Clean Architecture template to speed up your development: https://t.co/rZlBr524gN

[Milan Jovanović @mjovanovictech]

A while back, I worked on a subscription system that needed to track payment status.

The problem?

We couldn’t rely on client redirects.
We needed something more reliable.

The solution?

Webhooks.

Whenever a payment succeeded or failed, the provider sent a webhook to our backend. That’s how we kept things in sync.

No polling. No guesswork. Just clear, event-driven updates.

Webhooks are used in all kinds of systems: billing, messaging, CI/CD, and analytics.

But building a solid webhook system takes more than a single endpoint.

You need:
• Subscription handling
• Secure delivery
• Retry logic
• Failure tracking
• Event dispatching

However, at the core of webhook design is building an async workflow.

Here's how you can build async APIs: https://t.co/CBrYtjcgiK

Have you built or integrated webhooks before?

---
P.S. Here's a FREE Clean Architecture template to speed up your development: https://t.co/rZlBr524gN

[♡ @heart_jpg]

cherry blossom ice cream

[Milan Jovanović @mjovanovictech]

Did you ever need to inject a scoped service into a singleton service?

ASP .NET Core has three service lifetimes:

- Transient
- Singleton
- Scoped

Here's how they work. 👇

Transient services are created each time they're requested from the service container.

Scoped services are created once within the scope's lifetime. For ASP .NET Core applications, a new scope is created for each request. This is how you can resolve scoped services within a given request.

ASP .NET Core applications also have a root IServiceProvider used to resolve singleton services.

What if you want to resolve a scoped service inside a singleton service?

Surprisingly, the solution isn't too complicated.

Here's what you will need to do: https://t.co/4fUI52c0ue

---
Simplify your development process with my free Clean Architecture template. Download it here: https://t.co/JCzRfpNtQq

[lily!!!🌸 @lorycodes]

@_rafaelgss congrats!! ��