3 ms·
> "insta-legacy": now you're responsible for a bunch of code you didn't write that by definition nobody you have access to understands. Also known as: • Getti
by BHSPitMonkey 4y ago
> "insta-legacy": now you're responsible for a bunch of code you didn't write that by definition nobody you have access to understands.
Also known as:
• Getting hired at a software company that already exists
• Having co-workers leave the project
• Importing frameworks or libraries you didn't write
- kristopolous 4y agoNo, yes, no. (1) and (3) are different. In (3) you have access to the people, documentation, things are versioned and bugs are fixed and there's forums of people using identical software. In (1) the people are still there, you can open tickets against them, go and talk to them, etc (2) is correct and that's not a good thing. It's snowflake code where you can't do the other things. The point is you're producing this worst case scenario that good companies try to avoid at great cost, instantly.