1. 22

This is the weekly thread to discuss what you have done recently and are working on this week.

Please be descriptive and don’t hesitate to champion your accomplishments or ask for help, advice or other guidance.


  2. 10

    Signing on to a new part-time (3d/w) gig. I hit up a lot of my network, job sites, recruiters, meetups, but what finally came through was this comment when I saw the story on its way up the homepage; I emailed everyone who talked about working part-time and got a few emails responding to my comment. Finally it came down to three really good possibilities (two from networking, one response to that comment) and I went with the one that has just about everything I’m looking for. I’ll say their name in a bit when all the paperwork is signed and it’s done-done, but for now I’m going to wrap up my current gig (which might be abrupt, because I’m between projects at a consultancy, so they probably won’t want to pay me to benchwarm for two weeks) and take a vacation.

    Thanks very much to the folks here who connected me with opportunities, I really appreciate you reaching out.

    1. 3

      Been on working on this for a while beforehand, but the recent burst of posts on Gopher (1, 2) inspired me to get back to my own client for Emacs and crushed a problematic bug. Found gopher.el before starting but even now I still can’t make much heads or tails of what the heck it’s doing. I’ll make the source available once it functions.

      Managed to fix the filter function doing things wrong thanks to how process output is in chunks and am now making it interactive with buttons. Going to do a write-up on it when I get type-1 and type-0 items finished to help folks new to Emacs how to do things and explain what things mean.

      Here’s to hoping this first week of classes won’t be too troublesome to keep going.

      1. 3

        Last week, I pulled the trigger on opening up new registrations on PDFDATA.io (our PDF data extraction-as-a-service). Things have settled in for our first customers without any crises, so I’m feeling pretty good about that, as well as our choice to roll out on Heroku as a first step.

        (We’ve had a couple of requests for an option to deploy “hands-off” instances of the service via AWS Marketplace, so it seems that people are actually using it for more than e.g. Sharepoint and Wordpress installs. Thankfully, walking our Heroku-expecting app over to “bare” AWS infra will be ~cake.)

        The first client library we planned was to be for Node.js, and I mostly finished the spike of pdfdata-node over the weekend, and even got it [published to npm](). This was a bigger deal for me than you might otherwise expect: I’ve consciously avoided working with node directly (though I’ve abused it as a runtime for ClojureScript and such), so this was my first foray. If anyone with suitable experience/expertise wants to critique pdfdata-node, that would be awesome.

        I just deployed a new rev of our API docs that include prose and examples for using the Node library. I continue to enjoy using slate for those docs. The interleaving of examples and prose for different “platforms” (curl, Node, Ruby + Python soon, etc) has worked out as well as you could expect for a strictly text-based documentation system. I wrote about slate some in a previous WaYWoTW.

        This week, I’m starting on the bones of an in-browser toolchain that PDFDATA.io users will use to try and configure the various data extraction operations we offer. I’m actually vacillating some on the stack to be used there: most of my recent front end work has been in ClojureScript, but insofar as I am not the only one on the project, and I’m not planning on even being the technical lead ~forever, a more common toolchain might make more sense right now.

        Beyond that, I’ll probably be working on polishing the sales copy turds, and hopefully getting some beach time.

        1. 1

          PDFDATA sounds exactly like something I need. But I need it for personal use from a shitty home-made electron app, for 5-20 documents a month. I’d love to see an option involving say a one-off sign-up fee (to weed out time wasters) and simply paying 20c per document like you would on the “Freelancer” plan once you’re over the monthly limit. I’ve been using a commercial OCR app and an Automator script, which frankly sucks for my use case.

          1. 1

            I’d be happy to hook you up with an API key that would allow that level of usage, so that I could understand your use case; email us, or ping me on twitter or irc. As you might imagine, any plan @ ~ $4.00 / mo is just not feasible for a variety of reasons.

        2. 3


          1. 2

            I’m going to try to make some more progress on viola, which is currently just a gap buffer implementation I’ve refactored several times. It’s let me play with building safe interfaces over “unsafe” code in Rust and experiment with property testing. Hopefully it’ll actually become an editor at some point.

            1. 2

              Learning C++ for work, reading Clean Code by Robert C. Martin and looking into different ways to make apps for Android. Anyone got suggestions?

              1. 3

                Honestly, I’ve learned a fair bit by reading the C++ FQA, even though it’s not totally up-to-date. I’ve been thrust back into C++ with my work on LLVM and it’s helped a bit (I’m nowhere near done the whole thing, mind you, nor am I anything approaching an expert).

                Also, A Tour of C++ is helpful.

              2. 2

                Trying to reach 100% code coverage on sn/service, a decentralized social network service written in Go.

                1. 2

                  This week (and much of next week) I’m working half days to accommodate some dirty renovation work at my house. (Sanding, paint stripping, oiling & painting.) Partly it’s to give at least some presence at work while doing it, and partly it’s just hard work so I am not physically up to doing full days at the DIY.

                  Our house has very deep (50+ cm) window sills which were covered in a thick rubbery brown paint that had started to peel. We intended to strip the gunk off and paint them, but they turned out to be Teak—so we’re stripping and oiling with a hardwood kitchen worktop oil instead. They look great! And I am learning to use a belt sander, so that’s something…

                  1. 2

                    Ongoing projects:

                    • sanegl - still working on PBR. I think I finally figured out the math :P
                    • pep - toyed around with the idea of rewriting my text editor in scheme. So far, it seems like a good idea (no more segfaults at least :P), so I’ll probably do that when I’m tired of dealing with OpenGL’s crap.
                    • ircbots - installed OpenBSD on my little home server, and set up an irc server. Wrote some bots that print my rss feeds and twitter feeds. I’ll write one that handles reddit soon-ish. Not particularly a fan of Perl, but it’s the most convenient language atm.

                    If anyone has recommendations for other services that could run on a home server and work well on OpenBSD let me know. I’m definitely going to add an rsync backup, and was thinking about running bittorrent sync to sync my the pictures/notes on my Android phone (but would prefer something lighter weight and more cli oriented, if anything like that is available).

                    1. 2

                      camlistore should work on bsd; it’s currently filling the role of android photo backup target nicely on my lan.

                      1. 1

                        Woah, that looks awesome - I think this’ll perfect for what I’m trying to do. Thanks!

                    2. 2
                      • A small analysis system to look at log files and flag any issues with Google’s crawls.
                      • Chapters 10-13 of my first novel
                      • Sorting the first printing of the board game I’m working on (rules now complete, printing a few first copies to get feedback)
                      • Planning a talk on React.JS
                      1. 1

                        I got my msmtp/mbsync/mu4e mail setup working, including bbdb <-> CardDAV syncing. This feels like an accomplishment, although the end result is … I can read my email in something less crappy than OS X native mail client. I mean, yay? But this doesn’t seem like it should feel like as much of an accomplishment as it does.

                        For work, I’m trying to figure out a better way to provide our data to internal customers than publishing godawful amounts of denormalized data to Redshift. Also, wrestling with some npm versioning inanity and trying to understand Amazon’s Byzantine web interface, particularly their security stuff. I thought I’d never see anything as wretched as the iTunes internal tooling. Ha ha, what an optimist.

                        1. 1

                          bbdb <-> CandDAV – does that mean syncing with Apple Contacts without having to do a manual export/import vcard-dance?

                          1. 1

                            Well, I’m using Fastmail’s CardDAV at the moment, but I’ll test it out against iCloud’s. I found asynk, a sort-of functional python module for doing contacts syncing that includes bbdb support. So, we’ll see?

                        2. 1

                          Working on talk and workshop announcements for 44CON over the next few weeks. We have one each weekday till the day before the event.

                          I’m also going up to BSides Manchester, where I’m doing a talk on designing hardware for hardware hacking. I’m going to talk about the 44CON badge, what it’s a prototype for, the approach taken to selecting hardware, building prototypes and testing things out and where I’m going with my plan to build a tool to help people learn hardware hacking.

                          1. 1

                            Getting my home LAN fully running dual stack IPv4/IPv6. I’ve got it connecting to IPv6 webpages now but I still need to update bind and dhcpd to handle things on IPv6. Currently they are only doing IPv4 things.

                            I just found out about Free Code Camp so I’m starting to work through their paths. My hope is that after Jul 2017, I will have finished Free Code Camp and my CS degree (math minor) and be quite marketable for my career switch from the Air Force where I officially do nothing with computers.

                            And at work, I’m still plugging away on an internal website that I’m writing in Rails. I just found out yesterday that my input screen is completely inappropriate for the way data is received. Back to the drawing board on that.

                            1. 1

                              I finally got a Rasberry Pi (I know, right?). Going to get Firestr working on it. Because why the hell not. Firestr is light weight and fast and should run great there. However I use threads heavily so we shall see.

                              1. 1

                                I’m building a graph store backed by redis and fronted by a rest api. Its going to hold some medical/neuroscience data, so the security requirements are a bit special. eventually we’ll be running some machine learning algos over it, to build “annotating” edges, so this is all foundational from the fun stuff that comes next.