sverrirs

Nice, here is another more detailed version I made a few years back off the back of a rather excellent wait but why article :) https://labs.coruscantconsulting.co.uk/life/weeks/

Barrens. General. Chat... /shudder

Seriously, create a small report based on the logs that tracks visits, popular calls etc. It will do you good every morning to check it (charts and comparisons are great) and it will be an asset when promotion time comes around and you have define your "contribution" to the company :)

Agree on the cognitive overhead.

People will and are arguing that "it is kernel code, it should be complicated" but I really think this is backwards. Because it is low level and debugging is really cognitively intense and difficult at this level the code should be even clearer and easier to understand.

Projects should be accessible to new developers regardless of their complexity level. Even operating systems. Otherwise they will simply stagnate and die.

Also, "less skilled devs" are just people that are still learning. We've all been there.

On modern CPU architectures, the XOR technique can be slower than using a temporary variable to do swapping. One reason is that modern CPUs strive to execute instructions in parallel via instruction pipelines. In the XOR technique, the inputs to each operation depend on the results of the previous operation, so they must be executed in strictly sequential order, negating any benefits of instruction-level parallelism.[3]

https://en.wikipedia.org/wiki/XOR_swap_algorithm#Reasons_for...

I don't know why I'm even replying, this will get so much hate here, oh well...

1. Just because things aren't done "the way you would do them" doesn't mean they're "bad" or "wrong".

2. If you're not on a solo project, I've found writing correct but less "clever" code to help shorten ramp-up time for new devs and be more beneficial to future maintainability of the code-base and system.

TL;DR; Swapping values by XOR'ing may look elite and clever but hurts you in the long run.

Indeed! :)

Ah good mention, didn't know about this tool. Looks very sleek!

I wanted to avoid building a solution to do the whole communication as I was pretty happy with the website functionality. This tool is mostly to enable you to use the website on windows and to automate a lot of the annoying Windows stuff while still retaining the option to use the website or the Let's Encrypt client in a pinch :)

Just chiming in, gethttpsforfree.com does not ever get your private key. Only a certificate signing request that is generated using your private key. There is no such private key risk involved using this site.

Thanks for the kind words :)

I had thought about integrating the whole thing into the app but I wanted to keep it nice and simple (it is only a few hours of work actually).

Also it kind of felt wrong to deprive the gethttpsforfree.com of their traffic as I think their tool is really nice and deserves attention :)

Based on the idea discussed in this original article

http://waitbutwhy.com/2014/05/life-weeks.html

Additional reference data from:

http://people.math.sfu.ca/~idmercer/celebdeathsbyage.html

https://en.wikipedia.org/wiki/List_of_countries_by_life_expe...

gold, pure gold :D

You're more than welcome, glad that you might find this useful. Hope this HELPS "stabilise" things ;)

Exactly this. There is a fine line with regions and they have their uses.

As an example, I was working on a project a while back that had StyleCop rules set up so stringently that nothing could live in the same file, no enums, structs, extension methods, nada. The amount of files you had to create when adding new functionality (even a minor one) was mind boggling...

Please stop, dear god the Entity Framework as well! This horror will keep me up all night now.. :/

>older MVC apps (where the controllers get insane).

Oh dear lord the MVC madness I've seen... thousand yard stare

I admit that sometimes I find them handy to use when dealing with large complex files. Grouping together member variables, events, statics can help with reducing the initial noise when opening the file (these tend to be at the top of the class usually).

But they indeed depend on the team's total commitment on keeping them organized and up-to-date.

Thanks for the kind words :) Yeah regions are a strange beast in C#. In some cases I find them handy, like in this instance where I wanted the COM interfaces embedded in the main class file. Also to clearly separate which functions belong to the manipulation of master vs individual program audio levels.

The region paradigm is very often misused and is one of those things that starts off nice and then degrades as time goes on (meaning new functions get added in the wrong region, refactorings end up all over the place, etc). I prefer them though over partial classes (shudder) and when properly used they can be a huge timesaver when dealing with those annoying UBER-Forms that tend to happen when dealing with legacy WinForms code :)

Hahaha, indeed. I didn't realize myself until I started looking into this that MS named the system in Vista the same as the Apple team did in Panther. :) Guess it is the nerd in us all wanting to be working on the "Core" stuff

That sales pitch was "subtle"