3 ms·
heh, i get you that scope negotiation is outside of the scope (pun intended) of even more advanced automation techniques, same with the tradeoffs you've mention
by bmiselis 2y ago
heh, i get you that scope negotiation is outside of the scope (pun intended) of even more advanced automation techniques, same with the tradeoffs you've mentioned.
however! analyzing and understanding codebase enough to decide what to do next... this sounds tempting to dive deeper into.
can i ask what role do you have in your project/company? is it more managerial, or more technical?
- nojvek 2y agoTech lead. Analyzing code isn’t the biggest problem. It’s understanding what’s not in code. Like the customers who depend on a certain behavior. Or why a certain piece of code was added. If it’s still used by some paying tenant. Or how various services interface with each other via aws services in middle. The complexity of systems is so much larger than code when they run, and especially when 1000s of users are hitting various code paths and edge cases.
- bmiselis 2y agoi love your examples, you know why @nojvek? it's because they clearly show next-level challenges in tech projects, not easily replaceable or automatable. i've always believed that as the world keeps automating, we need to climb the ladder of abstraction - that way you stay (relatively) safe :)