Most remote work guides I see during these days of COVID-19, are all about optimizing for remote work in a remote company where everyone will keep working remotely forever. I haven't yet seen any realistic, simple, unsexy and "down to earth" guides on how to urgently switch a "traditional" old-school corporation to remote in 1 day.
Ages ago some dude I met at the Microconf conference (I don't remember his name unfortunately) explained to me how B2B software sales work in under 3 minutes, and it was brilliant.
Programmers often wonder, why executives make more money than developers. How come "John the manager" gets paid more than me, who's doing all the work?!
Here's a little C# hack I'd like to share, might be really useful to other devs too since it's a very common pain in all languages, not just .NET.
The .NET Framework's built-in WebClient class does not have a built-in timeout feature.
Sometimes you need to "log out other user sessions". To prevent cookie replay attacks or - a very common use case - log out other sessions when a user changes their password. ASP.NET does not have a built-in way of doing this, but there's a simple solution.
TL;DR I spent the last month testing how CloudFlare affects my organic traffic by turning it off and on again™ and measuring the ranking changes. Looks like CF hurts SEO. So we've built our own caching proxy with blackjack and hookers AWS and nginx, while saving a couple of hundred $ a month on the way.
This post has nothing to do with tech nor startups. Today, while adding proper "right-to-left" support to our app UI (for Hebrew and Arabic languages) I got a little carried away and found myself discovering a lot about Aramaic languages and ancient numeric systems.
If you're using OutputCache directive like this:
[OutputCache(Duration = 600, VaryByParam = "*", Location = OutputCacheLocation.Server)]
Or storing custom data in HttpRuntime.Cache like this
HttpRuntime.Cache.Add(...)
You probably caught yourself wondering
If you search for "generate zip in ASP.NET/C#" you get tons of blog posts and StackOverflow answers suggesting DotNetZip, SharpZipLib and other 3rd party archiving libraries. And up until now that was the only solution - all because .NET had no built-in support for zip format.
