The shape of that bottle is creepier than the text.

The URL seems to have a typo. Correct URL is https://github.com/presslabs/gitfs

If I was to create a blog today, I would use a static page generator and host it on GitHub or GitLab. I would spend my time on creating original content instead of tweaking the infrastructure.

I think the developer basically killed the project. I'm not sure Moq can recover from this. I recommend everyone to move to NSubstitute as soon as possible. I suspect most of the migration can be done via Find/Replace.

I would add Ars Technica to that list and call it a day.

For programming I follow YouTube channels of the conferences relevant for my tech stack (YouTube natively supports RSS). They are generally 1 hour talks but it's a great way to stay up to date.

I don't work much with Linux systems these days, but I would vote for $ sudo over #. Two reasons:

1. It's easy to overlook the prompt. That part is basically "some characters before the actual command", so I don't normally pay attention to it.
2. # is also used for comments. I think it would be confusing to use the same character for two wildly different things.

Would love to see a browser based implementation of this.

Thanks. I didn't know that when one adds an image it would override the URL. Even though the post contains the URL, clicking on the title only shows the image. I included the URL in the post body, but it's not as visible, unfortunately.

• Linus Torvalds
• Kent Beck
• Dylan Beattie
• Ian Cooper
• Simon Brown
• Martin Fowler
• Daniel Terhorst-North
• Sam Newman
• Andy Hunt

I think this is a good rule-of-thumb in general. But I think the best way to decide on the correct coverage is to go through uncovered code and make a conscious decision about it. In some classes it may be OK to have 30%, in others one wants to go all the way up to 100%. That's why I'm against having a coverage percentage as a build/deployment gate.

link to xkcd

Disclaimer: I'm not an expert on this at all (I don't have a blog either).

Have you considered using static site generators (Jekyll, Hugo, Gridsome, Pelican, etc.)? Both Gitlab and Github support custom domains? I suppose you can set up a pipeline (Github Action) to convert and publish your markdown files into the blog. You don't need to think about hosting at all. And you have all of your content in plain text files in a Git repository.