[awalsh128]

I have found it nice in the coding area to bang out snippets or auto complete the pattern for things like data structures and flow control. Sometimes even debugging but there is a large amount of oversight to massage the code to correctness. It saves me time on the meneal things but the higher level comprehension is nowhere near there yet. As far as getting through documentation, summarizing, and interrogating, it can be much better, especially if you put all the documents in the chat scope so it can use it.

My take is that it won't replace us but our roles will evolve to leverage these tools more and more to achieve human ends. There are so many considerations to take into account like production stance, fallback, data integrity, mitigation, privacy, security. I think we are a ways from that. When AI can start solving production issues post mortem and requirements implementation, then I would say we have hit a milestone. With that said, new engineers should still need to understand the fundamentals of CS, systems and how to properly use a language.

My main gripe is this push of AI in everything without fully understanding the value proposition and if it would be useful in the given case. I mostly ascribe this to leadership who don't really understand it and think it will just solve all of their problems and vastly increase productivity. What's worse is when it gets passed down the chain from C-suite and ends up being a hot mess by the time you get a project because there is no true direction of how it will apply to your product. It takes good leadership and identifying genuine usefulness for certain products.