You learn a lot when writing code.
- You can bundle issues into milestones and tie them to releases in GitLab
- You can't quickly and easily send someone a link to a TFS work item. ARGH.
- Dell docking stations sometimes decide that the DVI port just won't work but the VGA port will continue to work. Also, sometimes they can't drive multiple screens.
- The Korean language has SEVEN different forms of speech levels. Yes, seven. And no, they are not honorifics, they are different.
- You can write c# 6.0 code that runs against .NET framework 4.0, even 2.0 !
- Semantic versioning of your NuGet package is very, very important
- Dividing numbers in c sharp works differently than VB.NET
- & and | are non-short circuiting operators of && and ||
- You can convert vb.net code to csharp, offline, using SharpDevelop 4.4 (not version 5)
- If a Microsoft Client Report Definition file (*.rdlc) has a data source with an invalid field, it will fail silently and just not display anything in the report
- log4net accidentally broke their backwards compatibility from version 1.2.11 -> 1.2.15 by changing their strong key
- If you accidentally enable silverlight debugging you won't be able to debug your ASP.NET app because VS thinks that silverlight is 64bit and your ASP.NET IIS app is 32bit. (Can't find a link, take my word for it).
- Apparently, MSRelease manager isn't as good as Octopus Deploy
- Interviewing people is hard. Make them submit a programming test first.
- Dapper runs faster than Entity framework for a lot of stuff
- Stet means "cancel this edit" which is typesetting lingo
- If you're referencing a version of a DLL (say, log4net 1.2) , and you're referencing another DLL that also needs a different version of that DLL (eg, log4net 1.1), you can add an assembly mapping entry into your config file telling .NET to automatically use the newer version. This is called assembly mapping and the Microsoft explanation page is unbelievably complicated and convoluted.
- When Jenkins runs out of memory it really, really barfs and you need to manually restart the service
- TFS keeps track of people who have pending changes - even if those people's accounts have been disabled. After many years this can build up to be a lot of pointless data in TFS that needs to be cleaned up
- TFS can do labelling but searching for labels sucks. A label is “owned” by a user account. You also need to enable "recursive" for it to do what you think it will probably do.
- You can't ask Twitter to have someone's inactive account. Even if they haven't tweeted in three years.
Who ever said programming was boring?