parthi

I recruited a small group of medical students to act as accountability coaches. We're offering 2 weeks of free coaching via text. So if you're trying to cutdown on snacking during Corona, practice the piano more, go to bed on time or study for a big test, they can help you get to a point where it's second nature for you.

Just text 415-874-1545 (US/Canada only) with your name and the routine you want to build. The outcome is that you either pick up the routine or make a conscious decision that it's not for you at this time. No in-between.

I'm talking SAFEs, contracts, employee agreements, NDAs, etc. I also have some paper documents lying around. Some of this stuff is in Clerky. Just dump it in Drive? It's getting hard to manage

I just had to mail a paper check recently after a very long time and was wondering where people still use paper in their job, especially with everyone being remote

We're a small startup running Node for our backend. Using a combination of LogDNA, FullStory, Sentry and Mixpanel across frontend and backend.

Problems I face:

1. Can't trace user journey: User reports a bug. I look through logs with a timestamp of the user report, but can't trace the user journey, especially with lots of asynchronous operations going on in parallel

2. Insufficient logging: I can identify the error being thrown but can't identify the cause. Would want to see logs of surrounding code which we maybe didn't log

To solve this, I've resorted to adding logging around the suspected problem path, pushing to production and asking the user to try again (very annoying for them)

Any best practices I'm missing or is this really the best way to be debugging issues in prod?

Backend and data engineers, what analytics tools do you use to instrument your backend? What is your stack and DB? What are you tracking?

We're opening up integrations on our platform so developers can build on top of us. What matters to you as a developer when interacting with a 3rd party API? Would appreciate any pointers to good developer experiences (I like Slack and Stripe) and how to think about implementing them

Top of mind is: - Comprehensive documentation - Interactive APIs - Easy to test - Easy to get keys, register webhooks, etc to setup OAuth - Fast approval if needed - Stats on your API usage