Disqus - Latest Comments for blowmage

Re: PBTfans Dolch – KBDfans® Mechanical Keyboards Store

Mike Moore — Fri, 23 Sep 2022 14:23:18 -0000

Is an icon mod kit going to be available?

Re: PBTfans™ Retro Dark Lights – KBDfans® Mechanical Keyboards Store

Mike Moore — Wed, 24 Aug 2022 06:17:36 -0000

Love this. Please consider an icon mods kit.

Re: PBTfans™ Doubleshot Twist – KBDfans® Mechanical Keyboards Store

Mike Moore — Sat, 06 Aug 2022 10:01:34 -0000

The base kit has blue, gray, and yellow R1 escape keys. The 40s kits is shown with only blue and gray R2/R3 escape keys, but not yellow.

Re: PBTfans™ Retro – KBDfans® Mechanical Keyboards Store

Mike Moore — Sun, 17 Jul 2022 13:57:57 -0000

can command keys be added to add-on kits?

Re: PBTfans™ Doubleshot Twist – KBDfans® Mechanical Keyboards Store

Mike Moore — Sun, 03 Jul 2022 10:25:15 -0000

Love it. Can we get yellow escape added to the 40s kit?

Re: PBTfans Doubleshot Neon – KBDfans® Mechanical Keyboards Store

Mike Moore — Tue, 03 May 2022 05:10:51 -0000

Same. Need a 3u spacebar that matches the 40s kit…

Re: KBDfans PBT Doubleshot Spark – KBDfans® Mechanical Keyboards Store

Mike Moore — Thu, 07 Apr 2022 23:20:08 -0000

The IC used to have a 40s kit. Will there be a 40s kit when this goes on sale in May?

Re: KBDfans Doubleshot Resonance – KBDfans® Mechanical Keyboards Store

Mike Moore — Sat, 02 Apr 2022 12:41:26 -0000

One render shows icon mods, but there is no kit that offers them. Will icon mods be an option?

Re: PBTfans Doubleshot Neon – KBDfans® Mechanical Keyboards Store

Mike Moore — Sat, 02 Apr 2022 12:38:02 -0000

This is the set I’ve wanted since I first entered the hobby. It’s perfect. I am all in on this set, and pretty much every other color way that uses these molds, regardless of my three requests:

1) Can the colors be posted? This will help for planning on where to use the set.
2) Can a 40s kit be added? Specifically I have one board that needs a 1.25u enter keycap that I would love to use this set for, which requires a robust 40s kit to cover.
3) Can a r3 stepped Control keycap be added. Every other option for that key has a stepped variant except Control, which is what I use exclusively. I would prefer a stepped Control if possible.

Re: How to write a conference proposal

Mike Moore — Sat, 11 Aug 2018 20:18:23 -0000

Glad it was helpful!

Re: yield_self in Ruby 2.5 // Michał Łomnicki

Mike Moore — Thu, 28 Sep 2017 14:09:17 -0000

Yes.

42.tap        { |num| String num } #=> 42
42.yield_self { |num| String num } #=> "42"

Re: Using RSpec Mocks with Minitest - Courageous Software

Mike Moore — Tue, 13 Oct 2015 10:29:26 -0000

You might also want to take a look at RR. https://github.com/rr/rr

Re: The War on Testing

Mike Moore — Wed, 24 Jun 2015 13:30:15 -0000

The minitest gem is shipped with modern ruby. It is possible you have a bad ruby install and the default gem was not installed properly. How did you install ruby?

Re: Managing Login Passwords for Capybara with Minitest and Rails Fixtures | Brandon Hilkert

Mike Moore — Wed, 25 Jun 2014 11:44:45 -0000

https://github.com/humaneco... and https://github.com/humaneco...

Re: Managing Login Passwords for Capybara with Minitest and Rails Fixtures | Brandon Hilkert

Mike Moore — Wed, 25 Jun 2014 10:14:15 -0000

Nice write up. Been enjoying these posts.

I use a similar approach. I also call BCrypt::Password in the fixtures, but I set the password to be the same name as the fixture. So users(:fred) will have the password "fred". That's the simplest approach I've landed on.

If I don't like having a magic string in my test, I'll create a `user` method to return the fixture, and a `user_password` method to return the password.

Re: The War on Testing

Mike Moore — Thu, 29 May 2014 19:43:54 -0000

A bit of an inflammatory title, but also mistaken IMO. (The following is my understanding, if I'm wrong please let me know.) Ruby will continue to ship with minitest and test/unit, but they will be packaged as the actual gems and not as ruby files located in the standard library directory. Ruby now enables rubygems by default, so new users don't have to install the rubygems code or the individual testing gems. There are no extra steps needed to use the testing gems. Just require them like you always have. Only the packaging is different.

In Ruby 2.0 and 2.1 there are fake gems for these testing libraries that use the files in the standard library directory. Its been a pain to manage these fake gems. Instead of continuing with a poor solution the Ruby core team is simplifying their approach and they should be commended for it. Hopefully this new approach will extend to the other default fake gems like Rake and RDoc and JSON.

This change will also enable Ruby to ship with a newer version of Minitest, which wasn't a possibility until this change. So all in all this is progress and a good thing,

Re: Jim Weirich: My Mentor

Mike Moore — Thu, 20 Feb 2014 21:30:54 -0000

My heart goes out to you and your family. Please thank them for sharing Jim with us.

Re: Adding Minitest Spec in Rails 4

Mike Moore — Tue, 01 Oct 2013 19:28:47 -0000

I've done other talks, but not on minitest. They are all on my blog. I am working on a book or two, and might release some screencasts.

Re: Adding Minitest Spec in Rails 4

Mike Moore — Tue, 01 Oct 2013 19:03:28 -0000

I answered this on your StackOverflow post. There are multiple problems with that code.

Re: Us vs. Them: when management thinks software testing is less important then you do.

Mike Moore — Mon, 17 Jun 2013 22:34:49 -0000

Answering questions and exchanging viewpoints is not the same as arguing. But other than that I fully agree with this post.

The thread in question:

https://groups.google.com/f...

Re: MetaCasts.tv - MiniTest Rails

Mike Moore — Mon, 08 Apr 2013 15:37:06 -0000

Nice screencast. I'm planning on adding expectations for all the rails assertions by the time we get to 1.0.

Also, minitest-rails ships with autotest support so you can skip all that config if you use autotest. I'm happy to accept code needed for guard support.

Re: Refactoring towards "better" code

Mike Moore — Thu, 07 Feb 2013 16:20:45 -0000

Haters gonna hate, ponies gonna pwn!

Re: Refactoring towards "better" code

Mike Moore — Thu, 07 Feb 2013 14:21:07 -0000

@erikhollensbe I'm sorry if I upset you. That was the opposite of my intent. I am perfectly aware the Discourse team will not likely accept the pull request. The comment that was made to me by them was that sharing code would be better than snark, which is what I tried to do. I wanted to explain as clear as I could what I value and what my experience has taught me is trouble.

In retrospect I should have made it clearer that by "better" I meant this is a subjective matter. I assumed this would be obvious, but I guess not. My "better" is different than your "better".

Besides, how smart can I be if I can't get the month right on the blog post?

Re: How to write a conference proposal

Mike Moore — Mon, 28 Jan 2013 09:06:32 -0000

I wouldn't recommend folks put _less_ effort into their proposals. But I would recommend they put effort in the right areas.

Re: How to write a conference proposal

Mike Moore — Thu, 24 Jan 2013 17:32:49 -0000

Why are they passionate about speaking? They are probably passionate about the topic they are speaking about.

Or are you asking a different question?