smarticus-blog - Latest Comments

Re: My new funky editor. A story about Sublime Text 2

Luis Lavena — Fri, 20 Jan 2012 19:49:14 -0000

Is also worth mentioning that changing any of the settings and preferences it applies immediately so you don't need to restart or anything to see them in action.

Also is good to install Package Control and with it things like Alignment, Git and others.

http://wbond.net/sublime_packa...

Long gone the days of cd'ing into Application Support and doing git pull to your bundles ;-)

Re: My new funky editor. A story about Sublime Text 2

bryanl — Fri, 20 Jan 2012 13:38:51 -0000

good catch. hopefully he won't see that i typo'd his name :)

Re: My new funky editor. A story about Sublime Text 2

Fanny Flappenhouser — Fri, 20 Jan 2012 13:33:16 -0000

Tim Pope, not Tim Pop ;)

Re: Why people don’t ask for advice

Serguei Filimonov — Thu, 19 Jan 2012 16:14:58 -0000

In many many cases, when I'm asked for advice, the person is not asking for advice at all. They are asking to tell them that what they are doing is right or great or cool. They are looking for validation and a confidence booster. That's not advice. So most of the time instead of "How do I build a rendering engine?" it's more like "Look at me! I'm making a complicated rendering engine. Could you hear me tell you about it and be impressed with my progress.". But they phrase it in a form of a question. I know this to be true, because i've done something similar in the past. Wasting someones time asking them things when really I'm looking for positive feedback and confidence boost.

When someone asks me something in that way, I'm also very suspicious that their project won't go anywhere useful, in which case, their questions are wasting my time, which I don't want to do. So the best course of action is to give them short answers that are useless hoping they go away.

What might have happened to you is the above. People will help you only if it sounds like you're gonna succeed with their help and improve their reputation as "advice giver" (consultant)

Disclaimer: I'm not a psychology expert, but that's my mental model of the conversations discussed.

Re: Why people don’t ask for advice

Gerald — Wed, 18 Jan 2012 11:32:51 -0000

I was in a relatively heated conversation on /. some time back and was astounded at the lack of faith people had in themselves and the world at large (re: ability to start a successful business as an independant Joe). The dreamers, the revolutionaries, the stars don't let the constraints of other's mindsets define their own.

Asking advice is good and necessary, always view it critically, though. Understand that it comes from someone with different experiences and worldview. There's probably value in what you got from him, and will get from others, just have to filter for it.

I, like you, am a math (academically) klutz with a desire to work on some indpendent game development - if I can get over the mountain of projects I have in queue. It's a little overwhelming to look at, but you're sure as hell not going to get there if you don't try.

Re: Why people don’t ask for advice

Ra'Shaun Stovall — Wed, 18 Jan 2012 11:03:10 -0000

Or maybe he was using you as a mirror. You might have opened up an old wound that he had previously with going down the same path. That said..just cause I can't swim doesn't mean I should tell Michael Phelps he can't smoke. I'm just sayin!

Re: Code folding in vim

Keoghsie — Sat, 14 Jan 2012 05:37:26 -0000

Thanks, this helped a lot!

Re: Code folding in vim

Alex Lee — Tue, 06 Dec 2011 01:40:46 -0000

Thanks for the tip!

Re: Code folding in vim

A11142176 — Mon, 14 Nov 2011 03:02:59 -0000

Thanks a lot. This really helps!

Re: Code folding in vim

imissmyjuno — Mon, 10 Oct 2011 14:09:01 -0000

I think that's xoria256 but I'm not a 100% sure.

Re: Code folding in vim

Ray Rashif — Mon, 10 Oct 2011 14:03:53 -0000

Thanks for this. I've been a long-time vim user but never tried code folding, which I missed from IDEs and others editors like Kate.

Anyway, more importantly (for me), what colour scheme is that? If it's custom, could I have the vim file for it? Thanks!

Re: If your tests don’t scale, you might want to look in the mirror

sunaku — Fri, 23 Sep 2011 23:21:28 -0000

And finish here: https://github.com/sunaku/test... :P

Re: If your tests don’t scale, you might want to look in the mirror

bryanl — Thu, 22 Sep 2011 10:23:00 -0000

Start here: https://github.com/grosser/par...

Re: If your tests don’t scale, you might want to look in the mirror

Bob — Thu, 22 Sep 2011 10:21:04 -0000

Which test runners allow for multiple cores?

Re: If your tests don’t scale, you might want to look in the mirror

zenspider — Wed, 21 Sep 2011 23:56:26 -0000

Amen

Re: Code folding in vim

Test — Tue, 30 Aug 2011 01:30:37 -0000

Thanks!

Re: Pet Peeve Thursday: ruby private statements

Mark Wilden — Mon, 22 Aug 2011 10:52:09 -0000

Well, sure, because in the context of the eigenclass, the methods aren't class methods, so private works. But your point is taken.

I generally do not use private methods either. I spent too long in C++, fine-tuning access with public, protected (useful in C++), and private modifiers; then tweaking it with friend directives. It's that kind of bureaucratic programming I gave up when I turned to Ruby, along with variable type declaration.

Interesting idea to use an object, hidden in an instance variable, to protect access. I think I would prefer just using classes for OOP/SRP purposes. Of course, the two goals may coincide.

Re: Pet Peeve Thursday: ruby private statements

bryanl — Mon, 22 Aug 2011 07:49:34 -0000

That isn't 100% accurate:

https://gist.github.com/116220...

I prefer not to have private methods. If i start to think I need them, I generally try to create a new class.

Re: Pet Peeve Thursday: ruby private statements

Mark Wilden — Mon, 22 Aug 2011 02:03:43 -0000

This is an old, old argument, and if you search the Usenet archives from around 2000 or so, you'll find me arguing against testing private methods, too. I've since changed my views. I now think that any method is a candidate for unit testing. What difference does it make who calls it? You want to make sure the method - the UNIT - is correct.

In theory, if you test your public methods sufficiently, there's no need to test your private methods. But this was before mocking, where your private methods might not even get called!

It all comes down to what way produces the correct code in the fastest time. In the last ten years, I've decided that testing private methods is that way. But ask me again in 2020. :)

Re: Pet Peeve Thursday: ruby private statements

Craig Buchek — Mon, 22 Aug 2011 00:28:38 -0000

If you are testing your private methods, you're doing it wrong. Private methods should be used to pull out common functionality from public/protected methods. Since they're not used directly, they don't need to be tested directly.

Re: Pet Peeve Thursday: ruby private statements

Mark Wilden — Sun, 21 Aug 2011 14:54:26 -0000

I must admit - I prefer text, too. That's why I read books and don't attend conferences. But I'll take my Smarticus any way I can get it.

Re: Pet Peeve Thursday: ruby private statements

bryanl — Sun, 21 Aug 2011 00:58:14 -0000

The reason isn't too complex. I like video. Feel free to blog on this topic using text, and post a link here.

Re: I’m at Madison Ruby

John Ford — Fri, 19 Aug 2011 11:28:42 -0000

I was waiting for some arms to snap at 1:04

Re: Pet Peeve Thursday: ruby private statements

mcmoyer — Fri, 19 Aug 2011 11:23:34 -0000

I define my methods and then afterwards call the private method

class MyClass
def a end
def b end
private :a, :b
end

To me, it's a lot more expressive of your intentions

Re: I’m at Madison Ruby

Ra'Shaun Stovall — Fri, 19 Aug 2011 11:21:45 -0000

That's pretty fresh. I actually smiled lol.