Hide table of contents

TL;DR: How to contact me

EDIT: I'm no longer offering my time for free. Feel free to reach out if you want to hire me for projects.

If you think this could be useful to your org, please book through this calendly (Google Meet). As a fallback, I’m available as well through WhatsApp.

I’m offering help with:

(In no particular order)

  • Software engineering
    • Algorithm Implementation
    • Solving performance problems
    • Backend development
    • Computer Vision
    • Pushing that feature always wanted, but didn’t find the resources to implement
  • Data Science
  • Weird quests you're not sure what genre they fall into
  • Strange problems
  • Software engineering consultation
    • Bottleneck Analysis
    • Design review
    • Mentoring

If you don't see anything on this list that matches your problem, you can still book and tell me about it, I'd be happy to listen.

Why do I think I’ll be useful?

I've been a professional engineer for 9+ years and I expect to need very little management overhead.

Some recent examples:

  • I was the tech lead of an autonomous drone startup,  we created drones that intercept other drones, this included machine learning, tracking algorithms, computer vision, distributed low latency messaging, creating our own custom electronics and hardware.
  • I owned a critical silicon development framework at Apple and 1000x Improved its performance. My work had to do with computer vision and image processing IP development.
  • I joined Connected Papers to help them fix performance bottlenecks they've been having. I onboarded to their codebase in less than an hour, and 20x improved their most painful bottleneck.
  • I have reverse engineered undocumented APIs, dealt with authentication challenges and improved backend error resilience for Wix's no-code app builder. This was part of automating the manual labor of managing mobile apps' lifecycle in the Google Play Store and Apple App Store.
  • I've mentored and assisted engineers and to advance their skills and career. Mostly close friends but also from through a mentoring program.

For more thing, you can look at my CV and my LinkedIn and also my blog (which is updated infrequently).

Should you contact me?

If you think I might be useful to you - yes. Right here.

Alternatively, give me feedback on why not in this form.

What kinds of problems do I think I’ll be useful with?

TL;DR: Complicated problems please! (If you're not sure - book with me!)

Engineering

  • “We want to find a scheduling solution with the following constraints”
  • “We need to reduce the amount of alerts / errors in production”

Performance

  • “Our cloud bill is exploding when we have a lot of user activity”
  • “Our app feels unresponsive”
  • “We can’t add more tests because our test suite is already too slow”
  • “Let’s grab a coffee while my build runs!”

Mentoring / Consultation

  • “We need to grow our engineers but don’t have capacity” (also see Yonatan’s  mentoring post)
  • “Which database should we choose?”
  • “We can’t onboard new engineers because it would take too much time walk them through our system”

What will working with me be like?

  • A meeting over video where we talk about your engineering challenges and figure out if I’m a good fit.
  • An onboarding session to your codebase (optional)
  • Ongoing communication mostly with async messaging
  • PRs at your repository’s doorstep

Direct communication

I like to be frank about things (especially around engineering) that I’d, eh, do differently. 
I do this in a constructive way aiming to help make the situation better (this is indeed what I’m looking for - help solve this stuff), and still, I’d like to say explicitly that I’d like to work with people who are happy with this style of communication.

How can you help?

  • Refer software orgs / teams to me, if you believe they could benefit from a strong engineer in the short term.
  • Let me know why your org chose not to work with me. Here's the form for that.

This is all very much a beta endeavor, I plan to tune what I’m offering based on my observations, any feedback and suggestions to improve this effort are welcome.

 

Special thanks to Yonatan Cale for helping me create and memeify this post.

(Yonatan insisted I add this one)
Comments5


Sorted by Click to highlight new comments since:

I personally vouch for Soof and hope to work with him on important software projects myself

Following  anonymous feedback that I got from this form (thank you!) here's my more professional (and meme-less) pitch:
 

I'm offering my engineering / consulting time for free for a limited time for EA Aligned projects.

TL;DR

Book this calendly if you believe I might be a good fit to your challenges.

I'm offering help with

  • Software engineering
  • Data science
  • Exploration of new ideas and testing their tractability
  • Performance issues
  • Mentoring
  • Consulting

Experience: 

I've been a professional engineer for 9+ years.

Some recent examples:

  • I was the tech lead of an autonomous drone startup,  we created drones that intercept other drones, this included machine learning, tracking algorithms, computer vision, distributed low latency messaging, creating our own custom electronics and hardware.
  • I owned a critical silicon development framework at Apple and 1000x Improved its performance. My work had to do with computer vision and image processing IP development.
  • I joined Connected Papers to help them fix performance bottlenecks they've been having. I onboarded to their codebase in less than an hour, and 20x improved their most painful bottleneck.
  • I have reverse engineered undocumented APIs, dealt with authentication challenges and improved backend error resilience for Wix's no-code app builder. This was part of automating the manual labor of managing mobile apps' lifecycle in the Google Play Store and Apple App Store. 
  • I've mentored and assisted engineers and to advance their skills and career. Mostly close friends but also from through a mentoring program.

For more thing, you can look at my CV and my LinkedIn and also my blog (which is updated infrequently).

How will working with me be like?

  • We'll do a first meeting over video to talk about your challenges and figure out if I can help you.
  • An optional onboarding session to your codebase.
  • Async messaging as day-to-day synchronization (more video calls optional)
  • I deliver whatever we've established needs to be done.

Direct Communication- I express my opinions about engineering in a very frank way,  I do this in a constructive way in order to find solutions to the problems we have at hand. I hope to work with people who are happy with this communication style.

Should you contact me?

If you think I might be helpful to you - yes.

If not - please provide feedback on you you think is missing right here.

Is helping out with theCaDC.org something that you'd be interested in? Many of the analytics are open source and on GitHub.

I might be interested :) 
Would you like to schedule a meeting and talk about the challenges you're facing?

Curated and popular this week
 ·  · 16m read
 · 
At the last EAG Bay Area, I gave a workshop on navigating a difficult job market, which I repeated days ago at EAG London. A few people have asked for my notes and slides, so I’ve decided to share them here.  This is the slide deck I used.   Below is a low-effort loose transcript, minus the interactive bits (you can see these on the slides in the form of reflection and discussion prompts with a timer). In my opinion, some interactive elements were rushed because I stubbornly wanted to pack too much into the session. If you’re going to re-use them, I recommend you allow for more time than I did if you can (and if you can’t, I empathise with the struggle of making difficult trade-offs due to time constraints).  One of the benefits of written communication over spoken communication is that you can be very precise and comprehensive. I’m sorry that those benefits are wasted on this post. Ideally, I’d have turned my speaker notes from the session into a more nuanced written post that would include a hundred extra points that I wanted to make and caveats that I wanted to add. Unfortunately, I’m a busy person, and I’ve come to accept that such a post will never exist. So I’m sharing this instead as a MVP that I believe can still be valuable –certainly more valuable than nothing!  Introduction 80,000 Hours’ whole thing is asking: Have you considered using your career to have an impact? As an advisor, I now speak with lots of people who have indeed considered it and very much want it – they don't need persuading. What they need is help navigating a tough job market. I want to use this session to spread some messages I keep repeating in these calls and create common knowledge about the job landscape.  But first, a couple of caveats: 1. Oh my, I wonder if volunteering to run this session was a terrible idea. Giving advice to one person is difficult; giving advice to many people simultaneously is impossible. You all have different skill sets, are at different points in
 ·  · 47m read
 · 
Thank you to Arepo and Eli Lifland for looking over this article for errors.  I am sorry that this article is so long. Every time I thought I was done with it I ran into more issues with the model, and I wanted to be as thorough as I could. I’m not going to blame anyone for skimming parts of this article.  Note that the majority of this article was written before Eli’s updated model was released (the site was updated june 8th). His new model improves on some of my objections, but the majority still stand.   Introduction: AI 2027 is an article written by the “AI futures team”. The primary piece is a short story penned by Scott Alexander, depicting a month by month scenario of a near-future where AI becomes superintelligent in 2027,proceeding to automate the entire economy in only a year or two and then either kills us all or does not kill us all, depending on government policies.  What makes AI 2027 different from other similar short stories is that it is presented as a forecast based on rigorous modelling and data analysis from forecasting experts. It is accompanied by five appendices of “detailed research supporting these predictions” and a codebase for simulations. They state that “hundreds” of people reviewed the text, including AI expert Yoshua Bengio, although some of these reviewers only saw bits of it. The scenario in the short story is not the median forecast for any AI futures author, and none of the AI2027 authors actually believe that 2027 is the median year for a singularity to happen. But the argument they make is that 2027 is a plausible year, and they back it up with images of sophisticated looking modelling like the following: This combination of compelling short story and seemingly-rigorous research may have been the secret sauce that let the article to go viral and be treated as a serious project:To quote the authors themselves: It’s been a crazy few weeks here at the AI Futures Project. Almost a million people visited our webpage; 166,00
 ·  · 32m read
 · 
Authors: Joel McGuire (analysis, drafts) and Lily Ottinger (editing)  Formosa: Fulcrum of the Future? An invasion of Taiwan is uncomfortably likely and potentially catastrophic. We should research better ways to avoid it.   TLDR: I forecast that an invasion of Taiwan increases all the anthropogenic risks by ~1.5% (percentage points) of a catastrophe killing 10% or more of the population by 2100 (nuclear risk by 0.9%, AI + Biorisk by 0.6%). This would imply it constitutes a sizable share of the total catastrophic risk burden expected over the rest of this century by skilled and knowledgeable forecasters (8% of the total risk of 20% according to domain experts and 17% of the total risk of 9% according to superforecasters). I think this means that we should research ways to cost-effectively decrease the likelihood that China invades Taiwan. This could mean exploring the prospect of advocating that Taiwan increase its deterrence by investing in cheap but lethal weapons platforms like mines, first-person view drones, or signaling that mobilized reserves would resist an invasion. Disclaimer I read about and forecast on topics related to conflict as a hobby (4th out of 3,909 on the Metaculus Ukraine conflict forecasting competition, 73 out of 42,326 in general on Metaculus), but I claim no expertise on the topic. I probably spent something like ~40 hours on this over the course of a few months. Some of the numbers I use may be slightly outdated, but this is one of those things that if I kept fiddling with it I'd never publish it.  Acknowledgements: I heartily thank Lily Ottinger, Jeremy Garrison, Maggie Moss and my sister for providing valuable feedback on previous drafts. Part 0: Background The Chinese Civil War (1927–1949) ended with the victorious communists establishing the People's Republic of China (PRC) on the mainland. The defeated Kuomintang (KMT[1]) retreated to Taiwan in 1949 and formed the Republic of China (ROC). A dictatorship during the cold war, T