In general I would agree, but since you mentioned "never" I have to interject ; )
In this visualization, I was immediately able to pick out clusters around "i", "Apple", "touch" and so on .. and the interactivity helps me to quickly filter and explore. So, I think that for an exploratory tasks, a force-directed graph helps.
The training we had to do with our sound team dropped significantly, as we could load useful presets, do some preparatory work at home before the service etc. It was a great example for what a real "digital transformation" looks like ;)
I have no idea which side of the bed HN woke up today, but the comments here disparaging Martin Fowler's body of work really trouble me.
I really enjoy Martin's (and more recently his collaborators') blog posts on various trends. More often than not, they distill key concerns and references into a quickly readable summary. His books on software patterns collect a breadth of problem/solution pairs that have now been baked into so many frameworks that you probably don't even realise you are benefiting from them.
If you are totally new to Martin Fowler's books and writing, I would urge you to not brush them aside because of some snide comments on HN. There's a wealth of material that can surely enrich your thinking.
To get to the next level and scale of bigger programs, you need to leverage the tons of work information visualization researchers have done.
I always point people to Prof. Tamara Munzner's work[1][2] that allows you to skip over all the dead ends that people have tried over the decades and gives you a "thinking framework" on how to design visualizations.
It's time for the pendulum to swing back I guess ;)
The article give iOS 7 the credit for ushering in the 'flat' design trends ... But I remember the Windows Phone 7-8 'Metro' (later renamed to Modern) design language as the key influence. It blew away people with the attention to typography and proportional grid-based layouts.
> "the web is still clinging on to monolithic backends — with their high costs, slower speeds, and huge surface area for attacks"
Hmm .. I've observed that microservice architectures often end up having large deployment footprint, higher usage of the network and a larger surface area for attacks since the "edge" is orchestrating more of functionality..
Does investing in Netlify really warrant such BS bingo? It's a really neat product in its own right.
In case the Mender folks are here, have you looked into incorporating the concerns addressed bt The Update Framework (TUF) https://theupdateframework.github.io/
I'm really impressed with the new Peugot 3008 i-Cockpit system [https://youtu.be/5UapzN65V7Q?t=1m16s] and the general interior design. IMHO way ahead of the competition.
This is a really surprising development! The Peugeot leadership seems to be unafraid to think different, and I think great things are in store for the Ambassador brand. It was totally neglected for decades.
I admire the way DHH writes .. confident and persuasive.
However, I'd just like to point out that in the same span of time JavaEE has undergone significant simplification (omakase API standards, anyone ;)) and if you check out the work of Adam Bien, you'll quickly find old myths of bloated memory consumption and fiddly XML configuration debunked.
Java is also lucky to have a parallel full-featured stack in the Spring ecosystem. Projects like JHipster do an opinionated take on how to wire things up and take you to quickly to orbit.
So basically, I disagree with DHH that there is "Very little activity in integrated solutions."
> I stress that it’s not specifically JIRA itself which is guilty of this. All of the above is implicit in the notion of reducing software architecture and development to a set of “tickets.” JIRA’s great sin is only that of being the most successful and widespread ticketing system. The notion of specifying a software project with a set of tickets is itself the enemy.
https://www.youtube.com/watch?v=RjfbvDXpFls
Enjoy !