nickls

What are some good options for a standing desk while traveling in an RV, travel trailer or van?

Solid work. Nomad List has really improved over the last few years.

Is most of your NL revenue from user subscriptions or ads or ...?

Invitae | San Francisco, Boston, New York, and Seattle | ONSITE | FULL-TIME

Invitae makes genetic testing an integral part of the patient journey. At Invitae, you'll get to change patient’s lives on a daily basis, the scale to impact millions and to live on the cutting edge of medicine. Sound interesting?

We are looking for: 1) Senior Product Managers -- who have either deep genetics or consumer web experience, come build the future. 2) Technical Program Managers -- lead complex projects that span a huge set of technologies and teams. 3) Senior Software Engineers -- front &| backend, we're building distributed systems to handle the scale and complexity of genomic data.

I'm the hiring manager for the first two and sometimes involved in the last one. Hit me up if you have any questions, or apply through our website.

More details: * Career Page -- https://www.invitae.com/en/careers/ * Senior PM -- https://boards.greenhouse.io/invitae/jobs/1412977?gh_jid=141... * TPM -- https://boards.greenhouse.io/invitae/jobs/1468409?gh_jid=146... * Software Eng -- https://boards.greenhouse.io/invitae/jobs/888569?gh_jid=8885...

I had a similar problem at one of my first jobs, I was given ownership of a few different highly complex and lightly documented codebases: sshd, kerberos, ntp, netsnmp, etc.

Other commenters are giving great advice around burn out, depression and health -- I'll leave that to them.

On the technical side, two things helped me with understanding complex code bases:

1. Write and draw on paper the object model, stack, protocol, interface, anything you can glean from the code or docs. Start small and keep adding to it. This helps you "chunk" the new information and have somewhere to attach new insights.

2. Run the system (or parts) in debug mode with maximum logging. Save the output and then start stepping through it line by line from the top. Find the source of each output in the code, try and understand the general area and then move to the next line. This will start to give you a good understanding of program flow.

Combined these two techniques will make it much easier to understand what is happening and when -- all you have left is to figure out why.

What do you build? I'm looking for talented freelance developers.

BloomAPI | SF, Seattle, DC, USA only | Full-time | Onsite/Remote

  Senior Engineers: Backend, Frontend & Windows (C#/.NET)

Interested in building out some unique technology that will impact the lives of tens of millions of patients?

  * Work from anywhere!

  * Make a difference

  * Have a pivotal role

BloomAPI | SF, Seattle, DC, USA only | Fulltime | Remote

Senior Engineers: Backend & Frontend

BloomAPI is small and rapidly growing healthcare startup. We're helping to unleash the full potential of Electronic Health Records by allowing practices to share data with trusted third parties instantly.

Interested in building out some unique technology that will impact the lives of tens of millions of patients?

* Work from anywhere!

* Make a difference

* Have a pivotal role

Get in touch: https://www.bloomapi.com/jobs

I really appreciated this comment. It puts (personal/startup) tragedies in perspective.

Doesn't look like any (major) modification to surrounding lines.

    if ((err = ReadyHash(&SSLHashSHA1, &hashCtx, ctx)) != 0)
        goto fail;

    if ((err = ReadyHash(&SSLHashSHA1, &hashCtx)) != 0)
        goto fail;

Diff35