Time |
S |
Nick |
Message |
01:11 |
|
pdurbin |
dotplus: was the person thinking of one of those? Or maybe OpenHatch? |
02:20 |
|
pdurbin |
huh, "A full list of all our salaries" https://open.buffer.com/transparent-salaries/ |
02:20 |
|
pdurbin |
mentioned at https://stackoverflow.blog/2016/08/24/podcast-72-jay-doesnt-get-a-raise-in-this-podcast/ |
14:21 |
|
dotplus |
pdurbin: up for grabs was the one they were thinking of. |
14:21 |
|
pdurbin |
ah |
14:23 |
|
dotplus |
I haven't investigated any of them, but if *any* of them are executed even moderately well, they would be a great resource not just for undergrads/newbies to the *field*, but even to longtime/pros who are branching out into a new language/tech. |
14:24 |
|
dotplus |
helping with the "never seem to have enough time for my own (entire) projects" by providing bitesize tickets. |
14:25 |
|
pdurbin |
yep |
14:26 |
|
pdurbin |
yeah, that reminds that I recently posted a list of ideas for my own entire projects: http://wiki.greptilian.com/ideas |
14:45 |
|
dotplus |
connectors is cool. I might steal the D3-fu for some graph work I was thinking of. If so, I'll let you know. |
14:59 |
|
pdurbin |
cool, issues and pull requests welcome |
15:41 |
|
pdurbin |
dotplus: I didn't link to https://github.com/openknot/openknot because it's your idea, not mine :) |
16:11 |
|
dotplus |
hm? you mean add a node in your D3 graph? I don't mind, do what you like. |
16:13 |
|
pdurbin |
dotplus: sorry, I meant I didn't add openknot to my list of ideas. |
16:14 |
|
dotplus |
openknot has rather stagnated anyway. Not least because I just don't have time for something so grand. |
16:16 |
|
dotplus |
It did occur to me recently that I could perhaps make some of putative win by merely writing (modifying) a bot that a) supports multiple chat protocols (matrix/IRC/XMPP) b) outputs to multiple "storage" protocols (SMTP, NNTP) |
16:16 |
|
dotplus |
I think that would be rather easier. |
16:17 |
|
dotplus |
and therefore more likely achievable. |
16:21 |
|
dotplus |
Could be a) python cos it's easy/familiar/has a massive library of packages b) erlang because it's absolutely aimed at this type of many-to-many network activity c) Golang with AMQP |
16:32 |
|
pdurbin |
take it to #openknot ;) |