That's at odds with the more agile way people develop software today.
Plus they almost never match up to reality. Good for planning the sequence of things, but don't expect them to be accurate over the long term.
The nice thing about Gantt is that it can show up your expectations as being too optimistic, very quickly.
Most software development projects lack those properties. Many software projects live or die by how well the "last 90%" of development goes (as opposed to a public works project which has much more critical initial work), but a Gantt chart usually represents that entire effort with one bar.
Having team members sign up for brief work items (2-3 days max), charting it out, then watching where it strains is useful and often humbling.
[1]https://en.wikipedia.org/wiki/Gantt_chart