My son decided that he wanted his own YouTube channel to publish his Minecraft sessions. I think he wants to become the next DanTDM (13M subscribers!). Two big hurdles with this one:

1. Finding a good screen recorder for Windows 10
2. Not using his full name as the name of the channel

Finding screen recorder software isn’t very hard, Google has a bunch of options. But each one seemed more scammy than the next. We finally settled on Wondershare Filmora, because that’s what his buddy in fifth grade uses. He’s still practicing so the huge watermark on the recordings isn’t bothering him yet. To remove it, requires a purchase which is $59 and I’m guessing that will happen soon.

Because he’s already got his own email with @olore.net hooked into Google (thanks to me for setting up the Google Apps for your domain like 100 years ago when it was free for everyone), creating a channel and uploading videos is a piece of cake. Almost too easy, especially for a 4th grader. While complete anonymity isn’t quite possible, I at least wanted to remove his full name from the top of his channel page. Easier said that done.

Eventually I found that if I created a Google+ page for/as him, he could add a nickname. Unfortunately, his nickname then appeared between his first and last name in quotes. Not what I was looking for, but close. Finally I landed on the solution - in the same screen where his First, Last and Nick name are in Google+ I removed his Last name, and Nick name, then changed his Minecraft handle as his First name. There was a warning about this change taking affect for all Google services, which probably means GMail too, which isn’t ideal, but for now his name is off his channel, and just his Minecraft name shows, which is perfect.

Without further adieu, I give you the joecraft2015 channel !

A few months ago, at the office, I was lamenting the fact that TSLint doesn’t have the ability to WARN of problems, therefore any new rules that get introduced will break the build. We have a gigantic project and have had a lot of success slowly implementing ESLint rules thanks to being able to give teams time to adhere to the new rules by setting them to WARN instead of ERROR. Once all the warnings are gone from the build we switch it ERROR and move onto the next rule.

I found two issues (#629 and #345) on github and took a shot at implementing one of the suggested ways to allow for setting the “rule level”. At first I went a little crazy and renamed RuleError to RuleViolation which resulted in hundreds of files being changed. After a little feedback, I reverted that and added a simple RuleLevel that is attached to each Rule. I haven’t gotten around to writing tests for it, which is probably why it hasn’t had much attention, but I found the tests a little complicated and I need a solid block of time to get in there and make my changes. It’s also a bit weird because the TSLint project uses TSLint to lint itself. So, while backwards compatibility is very important, it’s a little odd trying to use the new stuff in HEAD while the scripts use the version (master) installed by package.json when running some of the tests.

I’m going to start pushing to get this pull request in as it’ll help my team adopt better and more consistent styling of our TypeScript. We have tons of Javascript being converted over to TypeScript and in the process losing our ESLint rules, so this is a high priority before we get too far off the rails.