| cmaloney | morning | 14:06 |
|---|---|---|
| _stink__ | yo | 14:08 |
| rick_h | morning | 14:08 |
| cmaloney | How goes? | 14:21 |
| rick_h | wheeeee | 14:24 |
| rick_h | I need a weekened to recover from my weekend | 14:24 |
| rick_h | https://photos.app.goo.gl/wuEpu6nc27eZRces2 is kind of a cool summary of it. https://photos.app.goo.gl/wuEpu6nc27eZRces2 | 14:24 |
| rick_h | bah | 14:24 |
| rick_h | anyway, fun weekend, sore and tired now. | 14:25 |
| rick_h | google is rocking the photo stuff from this weekend where I used the phone a lot. I've not leveraged it much but kind of cool | 14:25 |
| jrwren | cool beach | 14:32 |
| rick_h | yea, aunt's lake place is a lot of fun | 14:34 |
| rick_h | really makes me want a lake setup | 14:34 |
| jrwren | ha. | 14:35 |
| jrwren | I hear that from people so much. | 14:35 |
| notlikethesoup | morning | 14:49 |
| cmaloney | Am I reading this right: | 15:19 |
| cmaloney | "Xapo is seeking a senior Full Stack Developer to join our team. We need someone passionate willing to work with first class engineers around the world. The ideal candidate will be a seasoned developer with proven experience in backend development using python, with strong knowledge of MySQL programming and Redis. The candidate must also be able to master front end development technologies using | 15:19 |
| cmaloney | javascript, jquery and html. Developer profile mixture is 90% backend and 10% frontend. Experience with fin-tech and trading platforms development is required." | 15:19 |
| cmaloney | So you need a back-end person who might do 10% front-end that needs to be able to master front-end dev. | 15:19 |
| Zimdale | Master of the 10% | 15:19 |
| cmaloney | Wish they would just say it: we're too cheap to hire two people to do this job | 15:20 |
| Zimdale | That's what makes you a first class engineer | 15:20 |
| cmaloney | rick_h: That is a set of contented faces | 15:20 |
| cmaloney | Doing double the work at half the pay? :) | 15:21 |
| cmaloney | That makes you something, but first class doesn't come to mind | 15:21 |
| notlikethesoup | lol | 15:21 |
| _stink__ | s/cl// | 15:21 |
| notlikethesoup | what a.. weird job description | 15:21 |
| cmaloney | OK, so it's not just me then. :) | 15:22 |
| rick_h | cmaloney: heh | 15:22 |
| cmaloney | https://stackoverflow.com/jobs/150944/full-stack-developer-treasury-division-xapo | 15:22 |
| cmaloney | Oh, it gets better: "Experience with other major development language and frameworks like, C, C++, Java or .NET, Node.js is desirable" | 15:23 |
| cmaloney | Yeah... this sounds like a quagmire | 15:23 |
| cmaloney | Native/Bilingual English speaker is a must. Spanish is a nice to have. | 15:23 |
| cmaloney | Experience within fintech and knowledge about Bitcoins would be ideal. <- Oh hell no | 15:24 |
| cmaloney | Should have looked at that from the start | 15:24 |
| cmaloney | no wonder it reads weird | 15:24 |
| rick_h | "must be willing to be paid in bitcoin" | 15:25 |
| cmaloney | likely | 15:25 |
| notlikethesoup | must be heterochromatic and a black belt in tai kwon do | 15:25 |
| notlikethesoup | must make a really good toasted ham sandwich | 15:25 |
| cmaloney | I have plenty of board games downstairs; I have enough funny money | 15:25 |
| cmaloney | I'll pay myself in fate tokens | 15:25 |
| cmaloney | https://xkcd.com/1891/ <- love it | 15:28 |
| jrwren | https://goc.vivint.com | 15:38 |
| cmaloney | Public SSH keys | 15:38 |
| cmaloney | Read-only access | 15:38 |
| cmaloney | Yeah, no. | 15:39 |
| jrwren | are you kidding? | 15:39 |
| cmaloney | Nope | 15:40 |
| cmaloney | Just try to look at the problems. | 15:40 |
| jrwren | all of that is public anyway. They are being nice by telling you that they are accessing it. | 15:40 |
| jrwren | smh. | 15:40 |
| cmaloney | Right | 15:40 |
| cmaloney | https://goc.vivint.com/help | 15:41 |
| jrwren | oh yeah. I guess I had logged in already. | 15:44 |
| jrwren | Still, its fun. | 15:44 |
| cmaloney | This application will be able to list and see private details for your public SSH keys. Public keys provide SSH access to repository content. | 15:44 |
| cmaloney | Yeah, it's interesting how they set up the contest and the rules | 15:44 |
| jrwren | cmaloney: are you misunderstanding that text, or pointing out that its not very good? thanks for nothing, github. | 15:44 |
| cmaloney | I'm just curious why they would need this permission | 15:45 |
| jrwren | oh, to add your pubkey to their gitserver. | 15:46 |
| rick_h | we've been fighting that | 15:46 |
| jrwren | you do each problem by cloning a git repo, making changes and pushing to it. | 15:46 |
| rick_h | we want to auto import your public GH ssh keys...you can request them over the API without any permission/etc | 15:46 |
| rick_h | but if you want to know the name the user has on them, that they need to give you permission for with some lovely oauth dance bits | 15:46 |
| rick_h | which is kind of annoying just to add an already public key that you can get w/o any special permission over the api anyway | 15:47 |
| cmaloney | Ah, so you can access their private repos | 15:47 |
| cmaloney | So they can keep all of this stuff secret save for the participants | 15:47 |
| jrwren | for the goc, they use ssh as your ID. Rather than generate a new pair they use existing one from github. That is all. | 15:50 |
| cmaloney | jrwren: So I take it you're participating? | 15:50 |
| jrwren | cmaloney: no. i'm hosting :) | 15:52 |
| cmaloney | OK, there's a story there | 15:52 |
| jrwren | cmaloney: what do you mean? I'm not really hosting. My coworkers are hosting. | 15:54 |
| cmaloney | I'm confused then | 15:55 |
| jrwren | cmaloney: I'm sharing https://goc.vivint.com here, with all of you, as an employee of spacemonkey, a company inside of vivint. | 15:56 |
| cmaloney | Ah | 15:56 |
| cmaloney | I didn't understand the relationship | 15:57 |
| jrwren | No worries. I wasn't very clear. | 15:57 |
| jrwren | true story: I didn't think it was possible for software to be as bad as JIRA. | 17:11 |
| cmaloney | Bugzilla? | 17:12 |
| cmaloney | or are you using Jira and finding it bad | 17:12 |
| jrwren | using JIRA. | 17:12 |
| jrwren | I've used many different issue tracking softwares in the past. JIRA is the first that reminds me of Remedy at Ford. | 17:12 |
| cmaloney | Jira is what happens when you have a main product that doesn't get updated to newer conventions | 17:12 |
| cmaloney | Hah | 17:13 |
| cmaloney | I worked on Remedy at Ford. That was a clusterfuck | 17:13 |
| jrwren | same. | 17:13 |
| cmaloney | I mean I worked with the team that worked on Remedy | 17:13 |
| cmaloney | We did some of the reporting and what-not | 17:13 |
| cmaloney | That stupid quick-start panel was terrible | 17:14 |
| cmaloney | and if you needed anything more than that panel then it was a nightmare of fields | 17:14 |
| cmaloney | Of course Ford did what Ford does best: take a system that was designed for at most 50 users and try to scale it out to the whole fucking enterprise | 17:17 |
| cmaloney | and then turn it into something nobody wanted to use | 17:17 |
| cmaloney | The problem with Jira vs something like github / Trac is it's designed for issue management, not tracking | 17:22 |
| cmaloney | it's designed to figure out workflows and processes and procedures | 17:22 |
| jrwren | yup. terrible. | 17:22 |
| cmaloney | it figures folks will want to know how long something is in there, and what to surface when things move through the process | 17:23 |
| cmaloney | For most teams it is overkill | 17:23 |
| cmaloney | but tools like Rememdy and Jira are about trying to control the process | 17:25 |
| cmaloney | I remember one incident where a PC technician at Ford figured out how to game the system | 17:25 |
| cmaloney | he wrote a script that would find his open tickets and close them | 17:25 |
| cmaloney | got the technician fired but it highlighted that the main thing they were concerned with was keeping the SLA, not actually doing the work | 17:26 |
| cmaloney | As far as the SLA was concerned the tech was fine | 17:26 |
| cmaloney | model employee even | 17:26 |
| jrwren | lol | 17:27 |
| cmaloney | I think they fired the tech for something like destruction of data or some nonsense | 17:27 |
| cmaloney | Soon after they started implementing the whole "was the work completed" surveying | 17:29 |
| cmaloney | and the "reopen ticket" | 17:30 |
| cmaloney | which didn't solve anything other than make the process more convoluted and incorporated a short-circuit loop that allowed customers who didn't like the solution to be vindictive | 17:30 |
| cmaloney | But w/e | 17:31 |
| cmaloney | Stupid machine lockups | 22:52 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!