[02:55] <cmaloney> Yeah, we just let anyone post a comment
[02:56] <cmaloney> I borrowed that idea from  UNIX Stickers
[13:54] <cmaloney> morning
[14:15] <_stink_> yo
[14:41] <rick_h> party
[14:51] <cmaloney> Are we having fun yet?
[15:53] <jrwren> Do you ever feel the cortisol flood your body as a result of reading code?
[15:57] <rick_h> I thought that was just blood flowing, but hey maybe?
[16:03] <jrwren> need to find better stress mgmt methods, I guess :)
[16:14] <brousch> Hm, I normally just feel disappointment
[16:16] <jrwren> usually no biggie... but when you know where a couple of bodies are burried in teh code and you are digging them out and then find a dozen more... aaaahhh!!!
[16:33] <cmaloney> jrwren: I've tried to be more mindful when I code
[16:33] <cmaloney> and realize that it's just code
[16:33] <cmaloney> and write things down when they occur
[16:33] <jrwren> oh sure, I am pretty good about that.
[16:33] <cmaloney> instead of trying to fix all the things in the moment
[16:34] <cmaloney> but yeah, sometimes you inadvertently stick your hand into a hole and then realize there's a lot of sleeping wasps in there
[16:34] <cmaloney> and one of them just woke up
[16:34] <jrwren> lol.
[16:34]  * cmaloney is still trying to parse the person who said that Virtualenvs are an antipattern discussion on github
[16:34] <jrwren> its when I already was mindful, made the note, came back 2 weeks or a month later to address the issue and find the wasps that I feel it.
[16:35] <jrwren> virtualenvs are an antipattern. I agreee with that ;)
[16:35] <cmaloney> jrwren: Don't make me come find you
[16:35] <jrwren> they are a workaround for the inability to achieve an ideal.
[16:35]  * cmaloney thinks snaps are an anti-pattern. ;)
[16:35] <jrwren> ideally every python program on your system would depend on teh same version of whatever libraries on which it depends.
[16:36] <jrwren> achieving that ideal is hard, so we use virtualenvs instead.
[16:36] <cmaloney> Yeah, this person said that pinning packages to a particular version was causing him grief
[16:36] <cmaloney> and I'm thinking "If you're installing this system-wide I fear for your ssytem"
[16:36] <cmaloney> but e/w.
[16:36] <cmaloney> w/e
[18:24] <brousch> Ideally you wipe and reinstall your OS each time you work on a different program so you don't have to worry about virtualenvs
[18:25] <cmaloney> brousch: Yeah, that totally works. ;)
[18:25] <cmaloney> (though that's pretty much containers in a nutshell)
[18:26] <jrwren> lol
[18:27] <cmaloney> honestly that is my workaround for ruby code
[18:28] <cmaloney> never understood that ecosystem and how it is supposed to work
[18:28] <jrwren> its just like python
[18:28] <cmaloney> except not
[18:29] <cmaloney> it does some strange version pinning that I didn't grok
[18:29] <brousch> rake magic?
[18:29] <jrwren> python has that too.
[18:29] <cmaloney> well, bundler didnt help either
[18:29] <cmaloney> jrwren: in the same venv? :-)
[18:29] <cmaloney> not quite
[18:30] <jrwren> 2 diff ver in same venv?
[18:30] <cmaloney> in ruby yes
[18:30] <cmaloney> it did some strange shit when i set up redmine
[18:31] <cmaloney> not remembering everything that happened but i remember it felt like it was cresting a repo for many ruby versions and setups jnstead of python's one python per venv
[18:31] <cmaloney> damn typos
[18:32] <cmaloney> creating
[19:17] <jrwren> redmine is insane though.
[19:17] <jrwren> i think the python equiv would be like setting up reddit
[19:46] <cmaloney> It wasn't quite that bad
[19:46] <cmaloney> but yeah, it wasn't trivial
[19:46] <cmaloney> and we used rbenv I think
[19:46]  * cmaloney is a little foggy on details