When UML concept was introduced to me at university I was astonished by it and thought that it's really brilliant - I perceived it as parallel concept to constr

When UML concept was introduced to me at university I was astonished by it and thought that it's really brilliant - I perceived it as parallel concept to construction and architectural blueprints. I noticed how it helped to plan software development, spot hidden issues, missing functionality, revisit functional requirements with general design of software before even trying to write any code - it also was obvious for me that it is a tool for people with a lot of experience under the belt, aware of best practices, possibilities, common pitfalls etc. I really liked whole concept, I'm sad that it isn't common practice now - probably just too expensive to do instead of just bashing keyboard buttons and stitching together some libraries However I think that it will return in some form at some point - software as a craft is incredibly young compared to for example construction AND "everything old is new again" is incredibly popular in this field of work ;)