Just add a WinUI3 project to your solution, it can import the same C# services your backend is using (if u put them in their own Class Library at least)
with simple XAML u can have an usable GUI in no time
ANND if u didnt segregate the services into DLLs, then make your GUI make Http calls to your API, cud be local if ur server is local
https://learn.microsoft.com/en-in/...,bro got done in by a big-tittie goth girl π,@retoor beyond fucked.
At least in your case you've a valid reason, here coz the company hid its incompetence and put the blame on me, so MY career/record is ruined.
If I had not put in effort, I wouldn't care.
But the marketting dept will send out a "Amazing Product update with 20x performance increase!!!" newsletter this week. THAT I SOLO-ED. And I won't even be in the company when it goes out.
Legit used-and-thrown.,@Demolishun very likely. Coz in my product's repo I saw a LOT of people who aren't in the company with 5-6 months of idless between them
So it'd be easier for them to hire, get it refurbished every few months, fire and save on salaries.
PS: their 2nd highest selling product is a wrapper around a FREE, OpenSource product which they download as code, compile and obfuscate to hide the illegality. Then sell it at 4k USD/month to enterprise
