we learned that the implementation most changed but we choose not to do it ( generally), if you are a good engineer you don't need a ticket to fix this , you don't need someone to tell you to do it , you apply the engineering skills you are been pay to

Part of the problem it's the lack of understanding on how software it's made, you learn while you build, you discover new requirements while you build , what you usually do with the learning, nothing, most of the time we say we just patch it and that it

Awesome stuff , thanks for sharing

Always come back on a Friday 😁

Nice to see this type of real life anecdotes they can be used to clarify the power of Aspire and how they speed up Local Development ( and hopefully engineers get the local part finally 😜)

Thanks for sharing, that was interesting

That's an Interesting point, do you think it depends on each organization definition of conflict ( or even maybe the official English definition of conflict). I heard before that debates and transparency should be encouraged but never described as "encourage conflict".

Aspire is perfect fit to help also Auth|DB |Stripe providers to add Aspire comp or Service default code that make to setup connection to their respective services
Like:
frontEnd.WithAuth0()
. WithClientId(".")
.WithSecret("env var").
..
That we can use

Another words if I search on YouTube "Start up app starter kit using .Net tech stack" vs "Start up app starter kit with NextJs"
I see why newcomers get their attention directed by the simplicity of the other content.
I'm still in love with .Net tho :)

I have my own starter kit ( as any .net engineer should)
But I wanted to see + encourage .Net content creators to target this level of simplicity (on the steps and instructions not the stack) for other that want to have a product using dotnet can have ready in under 30 min as re ref video had.

3- Configure the DB provider and update the keys and secrets
4- Configure Stripe and update keys.
5- Configure deployment and deploy

On step 3 there is no migration of DB work, or Auth with social working.

Most of the YouTube content of starters kits don't exist with this level of simplicity.

A couple of note worth mentioning about why I found worth mentioning:
Note on the reference content posted where NextJs is used
1- It start just by cloning the repo( nothing special there)
2- configure a Auth provider and update the needed keys and secrets

Thanks!! Good to see dotnet content here on the bluesky

CC: @james.montemagno.com :)