| This is very much alive for internal tools, but the importance of design from a product perspective has proven important, which is why you don’t see much in products anymore. This is revisionist history. Desktop environments had become so complex and fragmented that just writing HTML & CSS seemed incredibly appealing. "the importance of design from a product perspective has proven important" is unsubstantiated, and is justification after the fact. Those are just buzzwords, what exactly do you mean by this? A focus on information vs a focus on 'engagement'. Knowledge vs addiction. Feeling better after using a computer as opposed to feeling worse. SQL is alive and well, granted newer programmers don’t learn it as early as they should Unfortunate use of words on my behalf, see: https://news.ycombinator.com/item?id=38243753 static memory allocation The tigerbeetle database is all statically allocated and (as I understand) makes no memory allocations as a response to use requests. They seem to be having great success with this approach. https://tigerbeetle.com/blog/a-database-without-dynamic-memo... Another buzz term. Software is constantly designed and the design of software is constantly discussed. What exactly do you mean by this? Who forgot what? I don't feel like this is a buzz term. Agile or whatever one wants to call sprint based work flows means no serious design gets up front anymore, and so we constantly try and code our way out of anemic or non-existent designs. |
2. That’s fair.
3. This looks interesting, but also very academic. Did that pattern ever see wide production usage?
4. A single project both doesn’t refute my point and refutes yours.
5. That just isn’t true. There’s room for good design. We do technical specs where I work along with some agile methodology. We just recognize that time spent hammering designs up front rarely produces better or more maintainable results in the same amount of time. Though I suspect this is very domain dependent.