Category Archives: Programming

Recently, I’ve been trying to learn Objective-C as a work-related “gosh that sounds fun” project. I have excellent resources available in the form of my coworkers, and I’m generally quite confident with my ability to find what I need through careful googling, so usually my biggest blocker is myself.

But I hear there’s still plenty of legacy Objective-C code out there, and there will be for some time. I also hear that there are still reasons to use it sometimes. (For me, one of those is “our customers still use it, and I can better help them if I understand this.”) So in I dove.

There are plenty of existing Objective-C tutorials and getting-started guides, which were once regularly updated, but that seems to have ground to a halt a few years ago. Lots of dead links. Lots of “actually just learn Swift.” Lots of “newly updated for Xcode 6!”, which was released in September 2014, or Xcode 5, released in September 2013. Ouch. We’re on Xcode 8.x now.

There’s another site which suggests that you don’t even need to have your own environment set up to learn it (they suggest you can use Linux or Windows, which is going to be a bad time for something that’s clearly Apple’s domain).

I emailed the author of one site (who has created a ton of tutorials, previously in Objective-C, now in Swift) and asked if he had any recommendations. He told me he didn’t teach Objective-C anymore and suggested checking out the Wenderlich resources.

I talked to one coworker, then another (a member of the CocoaPods core team, so I figured she’d have access to more information). She checked with her people. Wenderlich again.

I was beginning to feel a bit of despair — as much as I love the idea of finally becoming the self-sufficient reverse-engineering hacker that I am probably, as the child of engineers, supposed to be, I also really love having clear information when it comes to learning a new skillset. It is easier to learn good habits than to unlearn bad ones. It is also easier to learn from current information than from something that’s four versions out of date.

First lesson: tell people about your problems. I’d complained to my manager about this paucity of resources a few times, but last week he said, “hey, look what I found,” and sent me a link to Coursera’s Objective-C course. I don’t even know how he found it (I think it was an accident), but it’s great. It is gently out of date — I have had to google one setting in XCode so far (the size classes checkbox is now “trait variations”). But it’s got an excellent tone, good pacing, and the option to care about it with money if you want. (I’m happy auditing it.)

I’m going to continue on with that for now: I have at least one app I really want to exist, and I’d rather make it myself. Finally.

In some number of weeks or months, I’d love to add a subtitle to this post’s title: “but it’s worth it.” Time will tell! In the meantime, I intend to keep writing about this quest. Surely, someone else out there is right there along with me.

Hey there! As of September 2016, I’ve accepted a position that I’m really excited about, but as an “archive, not delete” kind of person, I’m leaving this up. I found a lot of encouragement in other people’s similar posts. Maybe I can light the way for someone else, too.

Hello! I’m in the market for a new programming-related job, and I wanted to take this downtime to articulate who I am, what I’m looking for, and what I’m hoping to find.

About me

I have a work history that’s been zooming in on more tech-related companies and roles over time. Previously, I’ve been everything from an au pair in France to a support person in English, French, and Québecois (which may or may not be French, depending on who you ask and where they’re from).

Support roles ranged from tech support for a photo-uploading website to being a founding member of a pre-launch startup’s customer relations team. At the latter, I ended up getting to do a ton of different things under the banner of one title. At one point, I developed the training schedule for new hires; at another, I created a peer-review-focused system for customer messaging QA (I got a lot of practice giving compassionate, actionable feedback to people). I’m really looking forward to bringing those perspectives to a new role.

While I was at the Recurse Center last year, I primarily focused on Python, though I learned some more SQL and dabbled a bit in C. Git is a significant part of my workflow, and I’m plenty comfortable using what I know and adding to my knowledge over time.

Less tangibly, during my RC batch, I got a lot of grief-inspired practice in resiliency. It is difficult to quantify this in a resume or cover letter or interview without breaking people’s hearts (a practice best avoided, when possible), but let’s put it this way: even when the going gets tough, I know how to take a break, and I know how to get going again. I know what I can do on my own, and I know when I need to ask for help. Put very plainly, I have yet to come up against a programming problem that was worse than losing two friends in a month. There are solutions to almost every work problem, and we can find them together.

I make a clear distinction between working independently and working in isolation; I love the former and find the latter pretty tough. At the same time, being accountable to a team is highly motivating for me, and I love the intersection between independent work and team accountability. I’m grateful to my last company for building such a strong remote-friendliness into their culture over time, and as such, I’m confident that I communicate well with geographically distributed teams. (It’s an art and a science!)

Send me an email if you’d like to see my resume! I have much of the same information on LinkedIn, too, if that’s your bag (it’s certainly valuable as a professional Rolodex), and there are a few extra details for fun. (What’s your best Muppet face?)

Outside of work, I’m an avid person-on-bike (my partner and I are officially car-free, at least for now, as of a month ago) and a regular writer. I write three pages every day on 750words.com, where my longest writing streak was 1533 days in a row (as of this post, I’ve just re-crossed 800 days). I am really proud of this! I find it helps clarify my thinking and writing in general, which is immensely valuable. As a bonus, it gives me an extraordinary view into my history and thoughts over time. I’m itching to learn some NLTK and dive into that history programmatically, too.

I like good coffee and bad wordplay, though I know how to say no to both. I’m a relatively newly minted gym person (at a small gym full of nerds), because six months ago, I decided I wanted to get stronger and I wanted to practice being terrible at something until I got good at it (and beyond). I cannot yet deadlift my body weight. Working on it! edit: As of 27 July, turns out I can deadlift at least 175 lbs. Yuss. Onward and upward.

What I’m looking for

Company-wise:

Location-wise, based in Portland, OR, or open to (and experienced with) remote work. For the right company, New York City would definitely be an option, too.

Small- to medium-size. That’s a subjective measure, but mostly what I mean is that I am happiest in non-huge companies. For the purposes of this search, “huge” is probably in the thousands (one or more).

Good people. To be honest, I’ve worked with terrific people at pretty much every job I’ve had. I aim to continue this. If, when you think of your company, you think fondly of your coworkers, I’m interested in hearing more. I’m especially interested in teams which are diverse across several axes (i.e. not just gender, though that’s a great start).

Working on interesting problems. There are so many of them! I was raised by a couple of thoughtful engineers and I’m prone to happily air-punching when I solve something. I’m most interested in solving problems that ultimately help people, whether or not my work is a step or two removed from the actual humans.

Long-term potential. I’ve had a few people tell me to aim to leave companies regularly during this part of my career; I would rather not. I like getting to build relationships and mastery over time, and if possible, I’d be thrilled to do that in one place. Maybe it’s that you’re a young company. Maybe it’s that you’re a stable company. Both are super attractive to me.

Bonus points if you’re a Recurse Center company. RC was what helped me discover that I really do love working with people and computers all day long, and while that was a huge part of its value to me, it also gave me space to breathe and spread my wings. That experience means I get to be part of an extraordinary community of learners and terrific people, too. I never would have been able to take the time to learn so much about programming, myself, and what I need to succeed if RC weren’t free, and RC is free because companies hire incredible alums through them.

Role-wise:

I am primarily looking for (junior-level) programming/development roles. There is exactly one company I’ve found where I’d be overjoyed with a support-focused job (hi!), because there’s genuine space for programming and a really strong, positive culture, and they’ll be receiving my application shortly.

I have broad interests, and I’m open to suggestion as to where to focus my energies. I’d especially appreciate some form of mentorship and loose guidance — if some formal structure exists at your company, all the better. Past experience suggests that backend or ops work will probably interest me most, but that’s not an exhaustive list. (I suspect frontend work would be difficult for me, so that’s what I plan to learn next. After all, I might be wrong!)

I am open to internships, especially if you’ve got experience with non-college interns, and especially if the role may lead to a full-time opportunity after the internship ends.

Have questions? Think we might be a fit? I’d love to hear from you, especially if:

you work for the company in question

you’re actively hiring right now (or will be very soon)

Please send me an email (liene.v+jobs@gmail.com) and let me know a little about the company, why you think we might be a good match, and any other information you think is relevant. If you’ve got any questions, I’d love to answer them, too!

I recently got dinner with a rad friend who I used to work with at Simple. (Rachel is a skilled wordsmith and a sharp wit — she’s recently launched her new business, Gimme The Lute, and if you might need help with your brand, you should get in touch with her! She’s also an excellent florist, because of course she is. But I have more experience with her writing, and she is masterful. She was the one who did the majority of my initial training, and her blend of directness and compassion made a huge impact on me.)

We talked about resumes and how to distill several years of experience into a few bullet points. I’d really been struggling with this, so she suggested I write down the good-parts-only version of my time at Simple. It was just the push I needed, and I ended up with two pages of things I’m really proud of, which surprised me a little!

It’s occurred to me that this might be fun to share, so I’ve copied it below. If you’re wondering what I did in my last role, this covers a lot of it!

I found out about Simple (then BankSimple) at a networking event in the summer of 2011. I met Al3x, the CTO, and was impressed with his energy and his complete lack of ego. I went to Simple’s site to see what they were hiring for, figuring it would be “lots of programmers,” and was really excited to see that they were hiring for support.

Simple was about two dozen people at that point. I was the second customer relations (CR) hire; the first [Rachel!] had been there for almost a year and made the move with the company from Brooklyn to Portland, OR. We were pre-launch by an undetermined amount of time (it ended up being about seven months more), and all our customers (~100-200) were friends or family. Our accounts were so lightly featured that we gave every new account holder some spending money right off the bat, because depositing money was a particular pain point. (There was no check deposit, no Simple-initiated bank transfer, and we couldn’t accept electronic debits.) We had a nascent Rails app for managing customer interactions, coupled with external partners’ well-developed and kinda creaky old systems. Our whole phone system was two iPhones that rang with the wee-ooo space-robot noise. At that point, they often didn’t ring for days; that ringtone is still a good way to get my attention.

My training was shadowing the person who had been doing all (potential) customer interaction [also Rachel], plus having several meetings with the founders and a few other key people. I got occasional programming help from my boss as I worked through Chris Pine’s “Learn to Program” book (which uses Ruby), following a summer Ruby/Rails workshop with Stumptown Syndicate (through their Portland Tech Workshops, which may someday see a second workshop!).

When the VP of engineering found out I was learning to program, he told me that the best way to learn was to look at other people’s code, and so he set up an internal GitHub (GH:E) account for me. The CFO walked by in the middle of this, said “you can’t do that,” and the reply was “yes I can,” so I got my GitHub account, the first for someone in a not-technically-technical role.

We hired a few new support folks the next month. None of them had previously worked in a customer relations role (one was a bank branch manager, one was a lawyer, and one was a civil engineer). We talked about what had worked well in previous jobs, what might be transferable, and what our big dreams for the team were.

Customer Relations instituted a lightweight scrum-inspired daily standup, where we reported on what we’d accomplished the previous day, what we concretely hoped to accomplish that day, and any potential blockers. I later began recording all our daily goals/accomplishments (in handcrafted JSON!), with an eye towards building out a small web app. The web app, alas, never came to full fruition, but did make me very good at handcrafting JSON, and as a bonus I started learning to use different text editors.

I interviewed candidates. I joined the Twitter team as it grew from a single person’s responsibility to a shared one, and later mentored new members. I jumped right in when our internal Code Club started up, where engineers volunteered to teach some programming to anyone who wanted to learn. (There were a few iterations of this over time!) I suggested hand signals to our now-weekly CR standup meetings, which dramatically reduced interruptions and are still in use several years later. I ran CR’s new-hire education program for a while. I taught the culture class in new-hire education for a much longer while, and cultivated a space where we talked about fears, hesitations, and how to be successful even if you’re not perfect (mistakes are okay! Responding well is key to getting through them). I joined our off-hours PagerDuty team to help customers with urgent needs in off-hours, whether they were in Los Angeles or India.

I noticed that a lot of coworkers said nice things about each other behind their backs. Suspecting that it was at least partly due to shyness, I started a “Box o’ Compliments” form for sharing compliments with coworkers (anonymously or not), and regularly sent out the incredible results from this project. (It impacted people enough that it’s still in use, and its administration has been adopted by someone new. I am absolutely delighted by this.)

I pioneered a stats-inclusive, human-focused, peer-review-driven QA process for CR messages. I sent regular reports to each member of the CR team, and I worked with certain teammates one-on-one to improve particular problem spots. (Sometimes you need someone to understand where you’re coming from and figure out a game plan with you; sometimes you can use TextExpander to ensure you never send “withdrawl” again!) After an illuminating conversation with our Communications Lead in marketing, I learned how to strike the word “but” from my vocabulary almost entirely, especially when giving potentially difficult feedback, and saw strikingly positive returns.

I worked with our amazing, supportive engineering leadership to pilot a half-day weekly collaboration (tiny internship?) with our ops team. I paired for about half the time, and hacked on my own the rest of the time. I learned to use vim, and I made multiple PRs and contributions to our internal continuous integration tool, written primarily in Python. Ultimately, a large infrastructure upgrade (and the resulting complications) pulled the plug on this pilot after a few months, but if I hadn’t caught the programming bug before, this cemented it. The bug, that is. The bug was cemented. But not in a “sad butterfly in concrete” way. In an “I’m excited and I air-punch with happiness way more than I used to” way.

A few months later, I worked with one of our data engineers to try to implement something similar, with the ultimate goal of joining the data team. We started meeting one-on-one twice a week, before work, to teach/study Python (and a bit of SQL). For a while, we shifted focus to data structures and algorithms, and invited a few members of the data team to join us.

I was really hungry for the opportunity to learn programming for more sustained periods of time (an hour here and there is hard!), so I applied to the Recurse Center in NYC, which describes itself as “a writer’s retreat for programmers.” I was accepted, took a leave of absence, and moved across the country for three months. I loved the RC community, loved the supportive environment, loved the space to be joyfully intellectually curious. There’s much more to say about that, of course.

And now? Now, I’m more certain than ever that I’m on the right path. I like being intellectually tired at the end of the day. I love the challenge of a good problem. I thrive around kind, hardworking people. And I can’t wait to join my support experience with something more technical.

Earlier start to the day! I even did some chores at home, and saw the sunrise. (It was slightly foggy and ethereally beautiful.)

The Coursera Algorithms course continues to walk that line where it’s alternately awesome and completely baffling. It’s fine. This is fine.

Started in on quicksort today — partitioning is so simple it seems like it shouldn’t be so cool. And yet.

I feel like I have a reasonably good grasp on comparing Big-O complexities of various algorithms (like O(n log n) vs. O(n)), but DETERMINING the Big-O complexity of a given algorithm is something that I understand only temporarily, and then it slips away again. (I only know that merge sort is O(n log n) because I accidentally memorized this.)

My mom (who teaches programming) says Big-O is one of those things that you get, and you are so relieved, and then you learn more and it becomes SO HARD, and then you learn more and things start to click again. I think I’m in the middle part.

Finally headed back to Concordia University’s library for afternoon studying. (Also picked up my community library card!!) Decided that panicking for several hours over not being able to build a database from super messy data is not productive, and also it makes sense that I do not yet know how to do something I haven’t done before. (Panicked about other things instead [work-related things].)

Instead of panicking about the database that isn’t (yet), I headed back to my little weather app. I added in some temperature stuff, which I’ve been way more interested in since the answer stopped being “it is hot all the time, except when it is DANGEROUSLY hot and the air is poison.”

I started a new branch to do something I’ve been excited about since well before I started this project — I’m going to gather together whatever information seems most relevant for bike commutes so I can call up that info with a single command. (Maybe I’ll fling it in a mobile app someday, so I can call it up with a single tap.)

How much will this rule? I’ll just get to be like, “yo computer, I’mma bike today,” and it will give me relevant data.

From my preliminary notes, here’s what I want to include, with aspirational stuff in italics:

precipitation, if there’s going to be any today (later: narrow this to commute hours, so just morning/evening)

humidity, if it’s high (also decide what constitutes “high”)

temperature, if it’s “low” or “high” (decide what constitutes low/high) (later: only display if it’s very different from yesterday)

visibility, if it is (or will be) pretty low at some point today

sunset time, if it’ll be before I expect to head home

apparent_temperature (Dark Sky defines this! how rad), if it’s very different from the actual temperature. I’m fairly certain I care more about THIS measure of temperature than the technically-true one, unless there’s a good reason to pay more attention to actual-temperature (like…danger?). Haven’t thought of one yet, though.

Maybe I’ll do something really weird like make up a “biking pleasantness score” or something so I can be all, “ugh, today’s gonna be a 12” or “oh wow, I just HAVE to bike today; it’s a 47!”

It’s Monday! I am READY FOR THIS (I am sleepy, but I have coffee, and I did get out the door in plenty of time to have a full day AND enjoy some daylight). I am not feeling totally awesome, but am trying to ignore this.

I am officially almost lost, but I recognized literally non-zero concepts in my algorithms course. I know about Big-oh notation! Today I also learned about Big Omega, Big Theta, and Big Brother notation.

Just kidding about the last one!

Had a kind of rough momentum-crushing lunch break (but a deliciously weird burrito). Took a short nap, which sort of helped, mostly because it gave me a deadline for getting up and going again. Took some ibuprofen in the hopes that it would decrease the amount of space that “pain” is taking up in my attention. It maybe helped?

Remembered that workfrom.co exists and learned that there’s a new tea café not that far away from here. It is like some sort of light-filled hipster dream space, filled with white walls and plainly finished wood and mason jars and succulents in tiny pots, so I wanted to be Too Cool for it…and instead, I kinda dig it. I’ve been kind of blown away by the gluttonous uses of spaces here since returning from New York (so much space unused! how can you afford that?), but sometimes that feeling is really good.

Decided that rebuilding inertia was more important than working towards graphing my UP data today, and tried poking through YourFirstPR tweets (it’s Hacktoberfest! I still haven’t submitted any PRs!), then remembered that OpenHatch exists and went there instead.

I’m practicing using my newly installed (as of Friday) wget, and I made my first tarball (!), and I read a ton of the man pages for tar, and boy howdy is there a lot there. Knowing how to search for things in vim/vi has been SUCH a huge boost in reading man pages. (Don’t know how? In vim, or in a man page, type / and then your search. [Since you can do really complicated searches if you want, searching for . will not search for a literal period — it’s a wildcard! — but letters and many kinds of punctuation should work as you expect.] Type n to find the next instance of that term, or N to find the previous instance. Bask in your wizardry.)

In further man page adventures, patch has (surprise) another long one, but check out this gem:

Assumethatthispatchwascreated with the old and new filesswapped.(Yes, I’m afraid that doeshappenoccasionally,humannature being what it is.)

The -s flag is also basically how I work as a human being. I will leave it as an exercise for you, the reader, to figure out what that is.

ALSO learned about diff, which is one of those things that people have mentioned in context a lot, as if any garden-variety nerd toooootally knows what that is. “Yeah so like you just do a diff on it; it’s super easy.” Well, I didn’t. I mean. I got the concept. But apparently it’s a command-line tool. To generate these files that tell you the difference between this file and this updated/fixed one. Which rules.

diff -u nutty-pancake-original.txt nutty-pancake.txt

On the OpenHatch patching mission, they’re like, “yeah use the -u option, because this creates a unified diff (“the universally preferred flavor of diff output”). So it’s just diff, that flag, the original file, and the newly updated file. (Having used git a bunch, it took me a second to realize these files had to be separate.)

Also practiced using more grep to find and destroy every aubergine, regardless of capitalization. Turns out Digital Ocean has a nice little grep reference here.

Whew. I feel like I got through some stuff today! It’s still in short-term memory, but that’s a fine place to start.

Started the day flipping through Mathematics for Computer Science (amazing old link here — it has the very incredible “What is a Proof?” introduction to Chapter one; a more recent iteration of MfCS is here). It was mentioned by the Coursera algorithms course I’m trying out, so, hey! I have indeed already been lost by some of the math stuff in CLRS, so it seems like having a concise-ish reference on hand will be…handy.

Really, all this algorithms stuff seems to be a knowledge rabbit hole. “But I need to learn more math!” I hear myself say. I took calculus in high school (it was fine, and then it was a disaster), and then again after I dropped out of college because it seemed like fun (hello, I was raised by engineers!), and then…that was a very, very long time ago at this point. I ran into trouble trying to use my phone calculator to compute logs of things yesterday. So. Fortunately I know some excellent math nerds, and now I have actual things to ask them about.

Also! Do you love algorithms, too? Or would you maybe like to? Maybe you would just like to “Netflix and chill” with some algorithms. The animated (i.e. lively, not a cartoon) lecturer of this Coursera course has some recommendations, which I’ll share here for fun.

Aside from the Eric Lehman and Tom Leighton document, there are also books! The instructor gives his four favorite algorithms books, the second and fourth of which are available for free (!) online:

Also there’s a brief “you may be rusty on this stuff” explanation of log base 2, which is just, like, plug a number n into your calculator, then divide by two. Then keep dividing by two until the number is smaller than one. And the number of times you needed to do that is the log. WHAT. Awesome.

Trying to learn stuff and immediately apply it is still kind of terrifying. Maybe just with Postgres.

Also I had a way shorter afternoon than I intended, because I ended up going into the Apple Store to get my phone fixed. (There’s this thing with some early iPhone 5s, and I do indeed have a very early iPhone 5, and the sleep/wake button on top stops working, and it’s…not great. The fix requires sending the phone away, where they have to take EVERYTHING out, and you have to wipe your phone beforehand, so you have to have a recent backup, which I did not when I first went in in June.) The wait was especially long, I went to the library nearby and tried to study a bit, there was a really distracting dude nearby…and then Apple texted me to head back.

Here’s a fun fact: I got the iPhone 5 when it was new, to replace the iPhone 3 my dad had given me when he was fed up with it (I had no smartphone). Know when the 5 came out? A little over three years ago. Know how long this warranty fix is good for the faulty button? …Three years. So I was toast.

Fortunately, I had YET ANOTHER experience at an Apple Store where the people helping me intuitively understood the right thing to do (<3 to Erika/Erica and Mark, who modeled really good mentorship interactions during this whole thing). They found the note from when I came in early this summer, and they got a manager to sign off on…just swapping my phone out (!).

Anyway so I have a phone that just, like, works now.

This took forever, though, and I didn’t fancy studying til 7. Back to it Monday, then.

I have some outstanding questions from the end of chapter 1 of CLRS (outstanding questions…they’re terrific!) (ho ho ho), and I will ask about them later, but also I dove right into chapter 2.

Unsurprisingly, it gets denser pretty fast. I am reading and rereading and rerereading a bunch of things. I have a basic grasp on, say, loop invariants, but I absolutely do not yet grok them.

Had a part-social-catchup, part-lunch-with-Nathan-and-his-mom-who’s-in-town lunch, and have significantly decreased my FOMO related to RC chat (Zulip). (I made a lot of choices about what NOT to read, which I am really proud of, and chose to read a small number of threads. All hail good threading.)

Now I do not have a big glaring “6949 UNREAD MESSAGES” thing hovering over the icon, and also I haven’t been keeping Zulip open, which makes it even easier. And I didn’t have to read 6949 messages to get there. (Phew!)

Decided to bravely tackle a Postgres problem with Nathan after lunch. We’ve previously tried to work on programming problems before, and it turns out that that might be a dangerous thing to do with your partner?

This time went a lot smoother, though, than any previous attempt, which I suspect is largely due to practicing “I don’t know” and related skills at RC.

Let’s back up in the terminal and see what we discovered! My brain is exhausted, but I know that I can understand my past.

🎈 🎈 🎈 🐣 🎈 🎈 🎈 psql
psql: could not connect to server: No such file or directory
Is the server running locally and accepting
connections on Unix domain socket "/tmp/.s.PGSQL.5432"?

As you may remember from previous adventures with my prompt, the “🎈 🎈 🎈 🐣 🎈 🎈 🎈” is literally my bash prompt and I refer to it by its shortname sometimes, “chickparty,” because that’s what you get with a baby chicken and six balloons.

Anyway.

All the googling in the world yesterday & today helped me find some interesting information: namely, be exquisitely careful with your postmaster.pid, because you can do DEEP DAMAGE if you go messing with it all willy-nilly, but sometimes you MUST mess with it. This was not one of those times, regrettably.

For an excellent explanation of one possible path here, see this StackOverflow post. I’m especially impressed that the OP ultimately solved their own problem, and THEN took the time to retrace their steps, explaining each one for the benefit of others.

I tweaked the find command just in case I was missing something, but there was indeed no postgres…except, as Nathan explained to me, the instance of grep that was searching for postgres. Sigh. Now I know!

501 6548 3487 0 3:19PM ttys016 0:00.00 grep postgres

Ugh. Go find yourself, grep.

Alas, the end of my server log had an entirely different error than the one in the SO post:

LOG: skipping missing configuration file "/usr/local/var/postgres/postgresql.auto.conf"
FATAL: database files are incompatible with server
DETAIL: The data directory was initialized by PostgreSQL version 9.2, which is not compatible with this version 9.4.4.

Yesterday, I had PAGES upon pages upon pages upon pages of this, almost endlessly repeating (there was some other stuff way way way up high, and the only dates I found for THOSE were in early 2014…hmm!). I scrolled with the mouse, the scrollbar barely moved, and I ultimately just had to drag and drop it like some kind of…person who does inelegant things.

For fun, and because both the internet and Nathan had suggested this, I ran tail -f, which follows (aha! there’s the f) the progress of the file until you tell it to stop. Sure enough, guess what kept adding to itself every few beats:

🎈 🎈 🎈 🐣 🎈 🎈 🎈 tail -f /usr/local/var/postgres/server.log
DETAIL: The data directory was initialized by PostgreSQL version 9.2, which is not compatible with this version 9.4.4.
LOG: skipping missing configuration file "/usr/local/var/postgres/postgresql.auto.conf"
FATAL: database files are incompatible with server
DETAIL: The data directory was initialized by PostgreSQL version 9.2, which is not compatible with this version 9.4.4.
(and on and on until control-c stopped it)

SPOILER ALERT it is the postgres logs! My friend, you have been so, so busy for SUCH a long time, huh? Your legs must be tired (why) because you have been running on my computer for all eternity (groan) ho ho ho

All the base are belong to us directories correspond to previously existing databases (from a zillion years ago when I managed QA reports for support, and also possibly from an open source day at Grace Hopper a few years ago?). Which is neat! I did not know that. That is a thing I learned today, too.

Because I decided that I did not care about these old databases that I have not looked at in literally years, we sallied forth with a rm -rf *, which felt so so spooky to run.

Just. Whole postgres folder there. GONE. Run ls, completely empty.

Running psql still gave the same error (about /tmp/.s.PGSQL.5432), BUT, I ran lsagain in /usr/local/var/postgres/, and we NOW have…dun dun dun…a server.log file! It’s Not Nothing!

Look at the cool new stuff at the end of server.log:

postgres cannot access the server configuration file "/usr/local/var/postgres/postgresql.conf": No such file or directory

It’s different! And then it was just THAT forever and ever, ^C (which is, I don’t know, like a computer’s “amen”? sure).

Okay so maybe not the most thrilling, but it’s Progress, and that is what I was after today.

Tried to get something going, since we’d now cleaned out all the old misbehaving stuff. Ran a series of commands that did not impress the computer:

initdb? no.

initdb -D .? no, initdb: directory “.” exists but is not empty. If you want to create a new database system, either remove or empty the directory “.” or run initdb with an argument other than “.”.

This puzzled Nathan for a bit, too (we didn’t hit on the perfect command the first time, anyway), which made me feel way better, because he does Postgres-y things a bunch for work. It’s nice to have people model that expertise does not equal omniscience — part of being experienced is knowing how to be productive and curious when stuck, I think.

So! Now I still have four CSVs full of all numbers (one date, many many many floats with 15 digits past the decimal…if they’re already double precision types, I’m kinda wishing there were a non-CSV format for these SUCH AS perhaps a database file). But I also have a working postgres to wrestle with tomorrow.

Postgres wrestling! Coming to a television near you. It’s gonna be big.

Back in Oregon. It’s strange here. People look at you on the street and I notice the air every time I go outside (it’s delicious; I breathe in and sigh and exclaim) and we only took a few hours to get back in our house (key excitement) and our friends are lovely and it gets so, so much colder at night here.

Today’s day one of Algorithm Study Time (I didn’t start on the road, we got home last Friday, and I gave myself Monday & Tuesday to take care of pressing home needs). Or maybe I’m calling it Autumn Bridge Term. I feel like I need a name for this.

Sonali at RC told me that for the next three weeks, it’s algorithms in the morning, building stuff in the afternoon, with lunch or a bike ride or whatever in the middle, and also I don’t have friends for now. Okay! I’m finding it comically freeing to have this much structure. Also that this feels like structure after the vast open fields of RC.

Cracking into the apparently-infamous CLRS algorithms book on Sonali’s recommendation. It is a beast, and it is a self-aware beast (it has already made references to its enormous size two times outside of the introduction, and I’m only in the first chapter). It is also the first time that I am doing highlighters to a book (perhaps ever), and I’m starting to find my way with this. It doesn’t hurt that I have magic windowed highlighters from Muji, so I can see through the pen as I’m highlighting (!). I continue to find ways to do small, personally meaningful rebellions, like writing “WTF” in the margin when appropriate. This continues to alarm and delight me.

I’m writing all my questions in a notebook, and typing out my exercise answers in a brand new repo. It seems like the kind of thing I should keep to myself, so I’m sharing it, because this is the kind of thing that seems reasonable now, after RC. Just. Share all the things. I like this feeling.

I got through Chapter 1, just not all the exercises or the problem yet. My brain is full, so now it’s time to give my stomach the same treatment. I’m talking, of course, about lunch. We will represent lunch here as a horizontal bar:

I either snuck into or went to the Concordia University library after lunch. The whole third floor, to my delight, is a quiet zone. No music. No talking. Just big beautiful windows and books and study corrals (in case you are a study horse or other study livestock) and wooden chairs and squishy chairs. There IS a “community library card” available here, but I don’t know if that means I’m also allowed to, like, come do stuff here. The existence of a Guest wifi network suggests that yes, however.

¯\_(ツ)_/¯

As mentioned above, the second half of my days for the next few weeks is (are?) Building Something. I ended up deep in the mud of “interesting datasets” and then tried to scale back and think about datasets I have on myself, which might be more interesting to me. Handily enough, I’ve been tracking my sleep and steps nearly every day for almost three years now (with some gaps due to technology or human errors of one kind or another).

Haven’t been using my Jawbone UP24 to track sleep lately, but I’ll figure out if that matters. The Mi Band I got after learning about Xiaomi from the Keyboard.io Kickstarter [whew!] is so so so much easier for sleep tracking, and has stellar battery life…but also a pretty bare-bones app. But also it was $15. In any case, the UP should have excellent coverage as far as steps go. (And also non-labeled “workout” sessions that are mostly bike commutes!)

So! I’m thinking I’d like to do stuff with that data, even if I’d had a rocky relationship with Jawbone products. I had a semi-original UP (not the very first generation, but the second gen, IIRC, which still plugged into the phone’s headphone jack to transmit information). I’ve had a series of misadventures with my original UP and UP24:

Original UP (headphone jack sync) stopped working entirely. Just. Blinked out of existence in a way no charging could fix. I eventually received a replacement (through a convoluted return process that almost turned me off of Jawbone entirely), AND, some time later, what I believe is the original defective bracelet. Hmm.

Next one stopped vibrating entirely (the vibrations partially confirm mode changes, give alerts, and function as the alarm). Since one of the reasons I am gleefully fond of this band is the little buzzing smart alarm, this was pesky/removed a functionality I had come to depend on.

Not wanting to deal with the return process again, and ready to leverage Bluetooth technology to be lazier (programmer’s mantra!), I got a new UP24 (which syncs via BT). It eventually became filthy (fine) and stopped functioning completely, except for secret flashing error codes (not fine). After a series of emails, I eventually had to call (on the telephone!) and go over all the information again to convince them that the thing was really really broken, and there was really really no way for me to fix it, and yes I know how to soft- and hard-reset my band now. It was a new kind of miserable, but the return process was much much easier.

And then there’s this one…the rubber has detached at both ends, eventually splitting on the cap side, and it can’t be slid back down to where it should reside. So it is eating itself at both ends, like some sort of Ouroboros.

But! Jawbone continues to make, as far as I can tell, incremental improvements in their support experience. Went to the FAQ, found something about Rubber Warping (sounds about right), filled out a tiny amount of information…and they’re sending me a warranty replacement (!) and it’ll have a return shipping label included (!!). A+, Jawbone.

Anyway now I’ve got five CSV files, each of which was just a click away once I found what I was looking for (thanks, Quora), one for each year from 2011-2015, including one from a year where there shouldn’t be any information (2011 — I got my first UP in November 2012).

Don’t know quite what I’m doing with it yet, but when building something, it helps to have literally any clue about what you are doing. And unless I find something wicked compelling, it’s Data On Myself which I am Finally Using For Something.

I eventually threw up my hands in frustration and headed back to the Udacity Relational Databases course, which I’d really like to finish up (and maybe review a bit). It is, after all, exactly what I am wanting to do with my project (Python + DB == BFF). And I finished lesson 4 of 5!

I also found a bilingual copy of Rainer Maria Rilke’s French poems in this library (yes! he wrote some French poems!) and anyway I guess I DO need to find out about this community library card business.

I can’t get Postgres to start, but fortunately I’m not even sure I’m doing the right thing (something may be broken, and if so, I just found one of those quintessentially lovely StackOverflow pages so I can piece through why and solve it).

Also, my Pomodoro timer went off again, and that makes 10 half-hour ticks or tocks or whatever today, and that’s about three hours of morning & three hours of afternoon and I am happy with that.

I’m learning about python packaging, and I think I just expected to Do A Google, copy a few commands, and be on my way. This is because I was wrong, which is both disappointing and awesome: turns out I get to learn a lot more than I thought I was going to!

Had good coffee-walk check-in chats with Aagje and Laïs, whose presence(s) I have been enjoying so much. Talked more about why I want to do what I want to do after RC, and although I’m happy to flip the table if need be, I need to give it a shot first.

I have been developing a different kind of patience here, and a big piece of that is that I am no longer willing to throw myself under the bus in the name of patience. I do believe that I had good reasons for doing it before, but I also believe that that was hella destructive, and I’m putting that firmly behind me.

More time with relational database study today! <3 So good. There’s a piece in the code I edited that I don’t quite understand (it looks kiiiinda like a list comprehension, but not quite), but the rest of it makes sense, and ALSO it works:

Learned about the inside guts of SQL injection and input sanitization and cleaning up the results of not-sanitizing.

Working inside of Vagrant is starting to make sense, in pieces. Having switched almost entirely to vim for text-editing, I notice some things missing already when I’m inside mah box (e.g. “where are my line numbers?”). But it’s helping me strengthen the muscle memory of certain commands (e.g. :set nu!).

Also went for some good walks (I have my first pair of non-little-kid Keds and apparently they are Taylor Swift edition?, and I went by the Littlebits store, and I went on soup-quest with Sonali and Nancy).

Our friends have been in town, and tonight’s their last night in town. For maybe the first time our whole batch, there’s no Monday night talk, and I’m kind of relieved, because it means I don’t have to skip out on something.