I'm going to have to ask you to put quotes around "engineering".
Had a colleague that interned at Oracle and was proud of how he learned to make better Powerpoint slidesets there.
His tips included "Always make slide headings full sentences including full stops". He would rename a slide titled "System architecture overview" to "The system architecture is distributed in four microservices.". (This would be above the chart showing the actual architecture)
Turns out Oracle execs famously print out slidesets, don't read them, but do read the headings, so this was what he had to do to ..."succeed".
Wow, that's the exact opposite advice I got doing an internship for an oil company a decade ago. They emphasized shorter (and hidden + animated bullet) points so that audience has to listen and engage with you, the presenter. Otherwise they just read your slides and put their brain in park.
I'd take the oil companies suggestions to heart, not Oracle's.
> Otherwise they just read your slides and put their brain in park.
I believe this is the point of the strategy. Imagine the presenter is hired in as a consultant, but the audience are the ones footing the bill without any knowledge of the actual work, timeline, etc. involved.
All they want is a white dude in a shirt, tie and suit to talk a lot and sound smart. The easier it is to convince the audience of that, the more suitable to purpose the presentation is.
Yeah, Oracle built some of the best Database and Datawarehouses and kicked serious ass. There is a reason it powered almost all fortune 500 companies in the 90s to pretty much 2015.
I based my half-joking statement on knowing exactly one colleague who worked at Oracle who couldn't program his way out of a wet paper bag, but could give you a 2-hour presentation with encompassing 80 slides on how many consultants you should hire to investigate the role of paper bags in your company.
Better communication to your audience is an important engineering skill. Although I don't think headings should universally be full sentances, having the top level detail could be useful: System Architecture - Four Microservices could be much more useful than just System Architecture.
Had a colleague that interned at Oracle and was proud of how he learned to make better Powerpoint slidesets there.
His tips included "Always make slide headings full sentences including full stops". He would rename a slide titled "System architecture overview" to "The system architecture is distributed in four microservices.". (This would be above the chart showing the actual architecture)
Turns out Oracle execs famously print out slidesets, don't read them, but do read the headings, so this was what he had to do to ..."succeed".