Inheritance in OOP (Interfaces and Composition with Delegates are the better parts of OOP and yet we're still teaching the whole Dog extends Animal to newbies). The best OO code I've seen uses the least inheritance.
UML
XML
Thin Client vs Thick Client debate: mobile apps nuked this whole paradigm
Flash, ActionScript
AR/VR: believe me, I think it's cool but it's still just all hype for a fraction of a percent of the market (This is an area I hope I'm wrong in, but I wouldn't bet on AR/VR)
Domain Specific Languages: like, they're fine and useful, but 2010 hype was that they were going to Change the World
I recall the opposite, where coworkers would print out GIANT UML diagrams of our code for new hires and interns. Looking back it was probably just a weird flex.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Inheritance in OOP (Interfaces and Composition with Delegates are the better parts of OOP and yet we're still teaching the whole Dog extends Animal to newbies). The best OO code I've seen uses the least inheritance.
UML
XML
Thin Client vs Thick Client debate: mobile apps nuked this whole paradigm
Flash, ActionScript
AR/VR: believe me, I think it's cool but it's still just all hype for a fraction of a percent of the market (This is an area I hope I'm wrong in, but I wouldn't bet on AR/VR)
Domain Specific Languages: like, they're fine and useful, but 2010 hype was that they were going to Change the World
DSL's...uggg. I have yet to see a situation that would not be better served using an established language/markup.
UML is actually very useful to visualize existing code.
But it must be done properly.
UML, that's a nightmare from the past :D
I remember Eclipse had a functionality that generated Java code from UML.
😅
I recall the opposite, where coworkers would print out GIANT UML diagrams of our code for new hires and interns. Looking back it was probably just a weird flex.