dominikh1 changed the topic of #cinch to: The IRC Framework | Latest version: Cinch 2.0.6
rickmasta has quit [Quit: Leaving...]
v0n has joined #cinch
_whitelogger has joined #cinch
_whitelogger has joined #cinch
rickmasta has joined #cinch
space has joined #cinch
Spami has quit [Read error: Connection reset by peer]
Spami has joined #cinch
Spami has joined #cinch
postmodern has quit [Quit: Leaving]
postmodern has joined #cinch
postmodern has quit [Remote host closed the connection]
postmodern has joined #cinch
jonahR has joined #cinch
jonahR has quit [Client Quit]
v0n has quit [Ping timeout: 256 seconds]
Spami has quit [Quit: This computer has gone to sleep]
Dwarf_ has quit [Ping timeout: 260 seconds]
Dwarf has joined #cinch
kludge` has quit [*.net *.split]
tempestas has quit [*.net *.split]
petru has quit [*.net *.split]
petru has joined #cinch
tempestas has joined #cinch
kludge` has joined #cinch
petru is now known as Guest25803
kludge` has quit [Changing host]
kludge` has joined #cinch
rickmasta has quit [Quit: Leaving...]
postmodern has quit [Quit: Leaving]
v0n has joined #cinch
v0n has quit [Ping timeout: 248 seconds]
v0n has joined #cinch
space has quit [Read error: Connection reset by peer]
resure has joined #cinch
<resure>
Hi. I've tried to use ENV variables for cinch sasl config, but it fails (can't modify frozen string). We can use ENV['...'].dup, but shouldn't that dup be in cinch sasl module itself?
<dyoung522>
resure: are you using bot.config.sasl.username ?
<resure>
dyoung522, yes
<dyoung522>
so bot.config.sasl.username = ENV['...'] is giving you that error?
<dyoung522>
in any case, I'm stuck with dyoung522 for now on freenode. I use other nicks on other servers.
Spami has joined #cinch
Spami has joined #cinch
<oddmunds>
im kinda lucky with oddmudns
<oddmunds>
oddmunds
<dyoung522>
stuck, as in, 'I don't feel like going through the hassle of finding something else and changing all my usernames everywhere'
<oddmunds>
it's my actual name plus the first letter of my surname
<dyoung522>
oddmunds: your name is odd?
<dyoung522>
;-)
<oddmunds>
over and over it is the ame that is given to me at universities, workplaces etc
<dominikh>
heh
<oddmunds>
it's oddmund
<dyoung522>
yes, I was joking
<oddmunds>
odd is common name in norway, though :)
<dyoung522>
I never understood the firstname_last_initial
<dyoung522>
maybe it's a European thing. I've always used (and seen) first_initial_lastname
<dyoung522>
not that it matters
<dyoung522>
though donovany is also silly
<dominikh>
I didn't want people to know my last name initially ;)
<dominikh>
before I realized that I need fame
<dyoung522>
HA
<dominikh>
now I wear my full name proudly in most places
<dyoung522>
this is the information age, anyone can find you anyway, so I stopped caring about that a long time ago.
<dominikh>
it's not too hard to hide your identity unless you troll 4chan ;)
<dominikh>
but at some point I stopped hiding it and putting myself out there
<dyoung522>
I think that's the logical conclusion most people reach, unless they're actively trying to hide something
<dominikh>
I think most people just don't think about it, use their real name, then get fired for pretending to be sick and smoking weed naked on an orgy.
<dominikh>
*at an orgy
<dyoung522>
heh, well, there is a bit of common sense necessary
<dominikh>
that's different from making sure people know who you are ;)
<dominikh>
most people would be better off hiding their identity
<dyoung522>
vanity searches of myself only bring up boring shit nobody else cares about
<dyoung522>
but sure, your point is valid. If you're that type of person.
<dyoung522>
Oh look! I ran a BBS in 1992! *yawn*
<dominikh>
:D
<dominikh>
you'll mostly find my blog entries and some other sites I contributed to. nothing too fancy, but better than party pictures if an employer searches for my name
<dyoung522>
I do my partying under an alias
<dominikh>
haha
<dominikh>
page two of google results has note that I'm a Go contributor, that's nice to show up ;)
<dyoung522>
heh
<dominikh>
(until people find out *how* I contribute...)
<dominikh>
dyoung522: your first iteration of the PR only removed stop's body, not the method definition itself
<dominikh>
hm, there seems to be no call to stop?
<dominikh>
if there's no call, it's fine
<dyoung522>
dominikh: I couldn't find a reference to it
<dominikh>
yeah, me neither. okay
<dyoung522>
yea, the first time I left the definition in just to be sure, but the second time I did a deeper search and couldn't find a call, so removed it entirely.
<dominikh>
:)
<dyoung522>
if I worked on a test suite in rspec, would you be thoroughly disgusted? =)
<dominikh>
yup
<dyoung522>
otherwise, it's learning minitest (which is on my list but not sure if I want to tackle it now)
<dominikh>
fun thing is, there's already a test/ directory with some basic tests, which doesn't use rspec
<dominikh>
so I can point to that and say "we no rspec" :P
<dyoung522>
yes, I saw those
<dominikh>
minitest is like test/unit in pretty much every language. it's the most basic form of writing tests
<dominikh>
a bunch of assert_* functions
<dyoung522>
but they don't run (read: I couldn't get them to run)
<dominikh>
(and our test() helper)
<dominikh>
brb
<dyoung522>
but I respect your opinion, so won't use rspec (on cinch proper).
Spami has quit [Read error: Connection reset by peer]
<dyoung522>
but that means putting that project off, and/or learning minitest sooner
Spami has joined #cinch
Spami has joined #cinch
<dominikh>
good choice ;-) why didn't the tests run? I haven't run them in forever
<dyoung522>
I wasn't either until I started doing it
<dominikh>
if it works for you, maybe.
<dominikh>
I tried it; it's the opposite to how I work
<dyoung522>
it's a tough mind-switch
<dominikh>
I don't subsribe to ideas that don't benefit me ;)
<dyoung522>
I was used to teasing out the code (and still do), but I make sure to go back and write a test before I move on.
<dominikh>
there's a difference between writing tests and written tests first :)
<dominikh>
one makes sense, the other will never work for me
<dyoung522>
there is. Generally you write a test with the 'code you wish you had'.
<dyoung522>
but sometimes that doesn't work
<dominikh>
because I don't even know the API I want yet before I implement it to see if it works
<dyoung522>
that's where the 'code you WISH you had' comes in. That's the key.
<dominikh>
in most of my projects I change the APIs multiple times, based on how hard they are to implement and how they interact with other components.
<dyoung522>
sure, as do most people I think
<dominikh>
I don't *WISH* to have any code yet, I wish to come up with some
<dyoung522>
that's the refactoring phase
<dominikh>
great, then I refactor and the tests break because the API changed, and I need to change the tests. might as well not have written them yet ;)
<dyoung522>
but you have to start somewhere... so, for me, it's "hmmm... let see, how would I want to be able to use this?"
<dominikh>
TDD only works if your refactors don't change the API but only the implementation
<dyoung522>
not true. I change the API quite a bit as I add stuff. Yes, you have to go back and changes some of your tests to reflect those changes. But you know which ones you need to change easily enough.
<dyoung522>
but the tests tell you exactly where you need to make changes.
<dominikh>
might as well write the tests once I'm done implementing.
<dominikh>
anyway, not going to discuss TDD, I've been doing that for over 5 years :)
<dyoung522>
AND, you don't forget to make changes to other bits of your code that may rely on the API changes (which you've forgotten about)
<dominikh>
well, that's why I use a compiled language now ;)
<dominikh>
I never forget!
<dyoung522>
heh
<dominikh>
that does quite affect the degree of testing you wish you had
<dominikh>
if I forget to change some bit, it probably won't compile
<dyoung522>
true, I think it's more relative in interpreted languages
<dominikh>
yeah.
<dyoung522>
but, even so, you could make a change that compiles (but doesn't work). But, we'll drop this for now. I'm not a TDD advocate, per say, I've just seen some of the benefits in my own work since I've started doing it.
<dyoung522>
it was HARD to start, too
<dominikh>
*per se
<dyoung522>
indeed
<dyoung522>
I am an advocate, but only for myself.
<dyoung522>
I'm also new to it
<dyoung522>
a half dozen projects so far... for me, it makes coding more pleasurable
<dyoung522>
but that's highly subjective, too
<dominikh>
best kind of testing is to find someone to write the tests for you ;)
<dyoung522>
heh, yes, well we don't ALL have that options. =P
<dominikh>
hasn't worked for me yet, either :P
jonahR has joined #cinch
<dyoung522>
I'm a one-man shop here... along with my other IT duties. I don't know if I would enjoy being a full-time programmer with constant deadlines.
<dominikh>
heh
<dyoung522>
my other problem is that I enjoy learning too much, so I spend too much time on new projects
<dyoung522>
for instance, instead of finishing up cinchbot, I'm now off writing cinch-storage (although there is a tie-in, cinchbot needs the storage engine). But now that's leading me towards learning minitest... the dependency trail is nearly endless sometimes. =
<dyoung522>
=)
<dyoung522>
s/needs/could benefit from/
<dominikh>
you don't need minitest for either cinchbot nor cinch-storage (yet)
<dyoung522>
that's true, but if the long-term goal is to merge cinch-storage into cinch than using minitest now would save me a bunch of rework later.
<dominikh>
true.
<dominikh>
unless you never finish cinch-storage because of minitest
<dyoung522>
heh, and there's the rub
<dyoung522>
but I will, I generally finish projects (bugs me if I don't)
<dyoung522>
they just take longer than I expect
<dominikh>
ok
<dyoung522>
funny enough, one of the maintainers of rspec is a member of ATLRUG
<dyoung522>
(Atlanta Ruby Users Group)
<dominikh>
ah. who?
<dyoung522>
just found that out today. ALindeman
<dominikh>
hm, never heard of him.
<dyoung522>
nor I, until I met him at the meeting
<dyoung522>
young guy, still in college I think
postmodern has joined #cinch
<dyoung522>
then again, he may have been embellishing his role as well. :shrug:
<dominikh>
:D
<dyoung522>
well, actually, he's on the github rspec memembers list.
<dominikh>
well yeah, he's one of the 3 owners of the gem