118 karma · joined January 31, 2014
This all reminds me of Makeshift Patriot by Sage Francis.
IMO, we should just do away with nullability and use the optional/maybe approach as wrappers for potential values. Null shouldn't really exist ideally, especially in OO because it is a unit value and also the parent value for all objects. I appreciate nullability being introduced but it causes a fork in types by two branches at the top of the hierarchy in most cases and more conceptually just associates these optionals with this flawed concept.
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.
Google search is decent at code examples but again too much text and not as concise.