This week has been going much better in terms of my mood and motivation. I did lots of small tasks, emails, etc. on Monday morning and spent Monday afternoon doing #research #sketchnotes for a #client #content article.
Slept in today, which started my day badly, so I didn’t get heaps done. I did submit my second #uni assignment, and I enrolled in two units for the next study period. I’m switching to study psychology (trying it out, anyway), since I’m getting nothing out of this #writing degree. I sent out six #interview requests for my next uni assignment, which is a longer feature article.
Another busy #HelloCode day today:
- Drafted a blog post for #exist about our new Todoist integration
- Finished replying to #interview questions from @josh so he could publish our first interview on the #larder blog
- Finished my first draft of my first personal #essay attempt. Got some feedback from @josh so I can refine it before pitching to editors.
- Drafted a post for the Larder blog about my work schedule
- Worked on a post for the Hello Code blog about fixing a tricky #exist for #ios a while ago
- Emailed some active Exist for iOS users to see if they’ll beta test for me, as I have a tiny pool of testers
- Republished my #sketchnotes post from my #blog yesterday on Medium
- Cleared my inbox
- Sent a media pitch about Exist
- Thought I finished the Larder import/export guide but it needs some changes still
Hope everyone is having a happy and relaxing Easter break, if that’s your thing! I’ve managed to avoid work for almost 3 full days straight, which wasn’t intended but was a nice change of pace.
Tonight, however, I prepped for an #exist-related #interview I have tomorrow for a How Stuff Works podcast, and took a look at #braid, my old little compiler/interpreter learning project. I’m thinking I might resurrect it with #LLVM as the back-end, but I’m not sure what language to use this time. No more Python. Maybe Rust? I’ve been reading some LLVM tutorials and docs I’ve saved for various languages’ bindings, and trying to work out what’ll work best for me.
Wrote up a draft of a #client article based on an #interview with one of the client’s customers. It’s really interesting to see how stories come together out of interviews, but the process of getting the interview material is so time-consuming and “messy” (hard to compartmentalise because there’s so much back-and-forth and waiting around) that it’s not my favourite work to do. Anyway, hope this one will turn out well, but I probably won’t do any more of this style if I can help it. #content
Had a #Skype call planned for tomorrow morning for an #interview, but based on my last interview experience, I decided to switch this one to email-only. Even in an hour-long call I only got through a third of my questions last time, and struggled to pull it all into an interesting #article. Hopefully email will work better. #content #client
So here’s what I’ve completed so far today:
- edits for a #client article
- invoiced two #clients
- followed up emails that were waiting for replies
- scheduled an #interview call for another #client article
- outlined my two #client articles due this week
- sent off #interview questions via email for yet another future #client article
- wrote an about page for #FieldTrip and added a link to my #Patreon account
Working on a #client article based around an #interview I did earlier in the week. Interviews are hard! I need a lot more practice at this, but I think they’ll always be hard. It’s a real art form, and I’m not sure it’s one I enjoy. I do think there’s a great story in here if I can find it and shape it, though. It’s an interesting #writing challenge, for sure. #content
More iteration on our #interview process for product engineers. Candidates will have a takehome exercise to build a tiny project tracking app. We pair & iterate additional features during the onsite, culminating with a product design exercise with product mgmt and UX - by this point the candidate is the technical owner and can speak to eng needs. If we're hiring people to build an app, what better way to see if it'll work than to build an app together?
Iterating on my team's #hiring process, hiring web developers. Any good content out there on #inclusive #interview strategies with strong indicators? We're looking at some pairing for remote screens (via coderpad.io or similar) and realistic web dev exercises on prebuilt problem templates (via jsbin) as well as more open ended design problems for onsites.