azuredivay said If we finish the sprint early we should be able to take rest of the days off :v

or at half days ffs,1. Leave big company of 1.5y for new job in different country
2. New company tries getting me a visa for 2 months and fails
3. Puts bogus blame on me and ends contract 2 weeks before my "temporary visa" expires coz their incompetent HR couldn't get the documents right. 

Fuckers didn't have ONE COMPLAINT against me so UNASSIGNED me from COMPLETED Jira tickets to ruin my OKR stats just to build grounds for this (since last week)

And when I protested, blamed some automation but DIDNT change the spreadsheet. (should've rung some bells for me, but naïve me believed their reasoning)

Big company meeting last week. Engineering Lead put a slide just about me coz my fixes brought a 20-FUCKIN-X performance improvement.
He said "oh I put a slide about [me], I dont see it", HR who was in-charge of compiling the slides said "Oh you sent the slide too late so we didnt put it". 

I shrugged it back then thinking oh well but in hind-sight Fuckers went OUT OF THEIR WAY to bury anything I did to build grounds for termination coz THEY couldn't get the visa.

kill me.,As much as I dislike google, it's so much more pro-active compared to Bing and Yandex :v

google already indexed my pages n removed the ones per updated robots.txt

Bing doesnt know I exist even though crawlled in webmaster, and Yandex still shows the Novemver version of pages in their results,Visual Studio in the recent releases got some updates where it "accelerates build time" by caching DLLs or something
Good in theory? sure.
In practice? So very often, a "hot reload" now doesn't trigger a DLL swap. VS says that changes have been updated but you see stale code and you've to turn off the program and re-run it

I'm sure there's a way to turn this acceleration off and will do that after this rant, but I don't get how such retarded features get green-lit and make it to production :v

I understand that for biiiig solutions with minutes of build-time, this would be god-sent, but if it's this unreliable in my 8-Project Solution, I wonder how unreliable it'd be in bigger Solutions

at least turn it off by default if you know it's shit ffs.,Did anyone here use .NET AOT/Native?
since it isnt CLR/VM dependent, theoretically it should be more performant, even if with a few limitations

my "Even if 5% perf increase, it's worth a code-refactor" senses are tingling 💀 someone give me a push to take the plunge```