News for hackers. Stuff that matters.
Re:Ask HN: Engineering managers, how do you onboard new hires? by aantix on Monday May 22, 2023 @08:29AM (#36030551)
One of the hardest parts for onboarding is determining which code is relevant.

If you're dumping a 300K line codebase in your newly hired engineer's lap, you're failing them.

This is one of the reasons why I developed Call Stacking - it records all of the method calls for a given endpoint (trace).

This is the perfect documentation for new hires - because they can look at these traces and get an instant idea of what is happening on the backend.

https://callstacking.com/

Re:Ask HN: Engineering managers, how do you onboard new hires? by anonzzzies on Monday May 22, 2023 @08:52AM (#36030797)
The reason I don't really want to work with languages that are not statically typed is that my (very well paid) projects almost always start on day #1 with 'here is 300-500k lines of code and a list of crap it doesn't do but should, cheers!'. With C#/Java, but definitely with F#/Haskell, this is not a big issue. With Python, JS, Ruby, indeed, I need callstacking like tools or it will take a lot longer. Usually the original devs already left (often they were never employees, but contractors from big firms who peddled juniors for senior prices).
Re:Ask HN: Engineering managers, how do you onboard new hires? by aantix on Monday May 22, 2023 @10:00AM (#36031575)
How does typing help with determining relevant code paths?
Re:Ask HN: Engineering managers, how do you onboard new hires? by aantix on Monday May 22, 2023 @10:10AM (#36031670)
If anyone is interested in writing the PHP, Node.js or Java client implementation for Call Stacking, reach out to me so that we can chat.

You'll have a reference implementation with the Ruby client, so there will be a clear path forward in terms of what is needed functionly.

[email protected]