Perl 6 - the future is here, just unevenly distributed

IRC log for #crimsonfu, 2016-09-25

crimsonfu - sysadmins who code

| Channels | #crimsonfu index | Today | | Search | Google Search | Plain-Text | summary

All times shown according to UTC.

Time Nick Message
00:31 Whoop joined #crimsonfu
12:53 skay_ joined #crimsonfu
13:32 dotplus_ pdurbin: re job board. I'm not doing freelance (any more, except for a teeny amount of hosting for poeple who have been with me for ages), but I think that having gigs filled/offered by already known/recommended poeple could be useful for consultant/client both.
13:34 dotplus I suspect that crimsonfu would not generate enough gig traffic for it to be very valuable, otoh, even one moderately-sized (well-filled) gig would make it worthwhile because it would be so easy to achieve.
13:36 dotplus a) Brief guidelines/template on what kind of postings are "ontopic" (both in the offered and wanted categories) b) github integration between Issues and #crimsonfu
13:38 pdurbin dotplus: yeah, I'd expect all traffic to come from word of mouth, direct links, people who know people.
13:39 pdurbin I was thinking we could use GitHub issue labels to tag jobs with keywords (specific technologies). And maybe a label or two for stuff like "remote".
13:41 dotplus honestly, I think that sort of thing is *such* a great idea on a larger scale that "we" the tech community at large (and our customers) would be well served if that kind of approach were common practice in most major open source communitites
13:41 dotplus on that particular note, I would suggest that you specify a default assumption of remote and tag for locality only if remote is not acceptable
13:42 pdurbin Yeah, remote should be assumed. Could have an angry red label for "local only". :)
13:42 dotplus there ya go
13:43 pdurbin dotplus: but what kind of approach do you like so much? Connecting people? "I know someone who would be a good fit for this."?
13:56 dotplus decentralized, pre-existing communities have builtin topicality. Example: An HN jobs posting, assuming you don't already (know/recognize the worth of/research) the nick of the submitter is only better than something on dice.com becuase HN has a level of respect in certain areas of the tech community, but the actual submitter could easily some slimeball recruiter who has learnt a few buzzwords. But if someone posted an offered gig in the relevant ...
13:56 dotplus ... project's job board, you could at least assume a *lot* more commonality of understanding.
13:59 dotplus I have more related thoughts on community networking, reputation and the like, but I'm afriad I can't articulate it at the moment.
14:05 dotplus pdurbin: I'll just leave it at this: There are 3 major advantages in descending order of (importance*relevance): 1) Small and/or focussed pre-existing communities increased the "shared language/understanding/assumptions" factor, the value of which can hardly be overstated in the context of small to medium freelance gigs (even more true for systems/ops kinda gigs than straight software dev) 2) "topicality" - you're more likely to find a flask ...
14:05 dotplus ... expert (or conversely flask gigs) if you post on a flask board 3) pre-existing reputation
15:46 chasmo77 joined #crimsonfu
17:19 bene_ joined #crimsonfu
21:23 pdurbin dotplus: I hear you. Makes sense.

| Channels | #crimsonfu index | Today | | Search | Google Search | Plain-Text | summary

crimsonfu - sysadmins who code