The Lounge is rated Safe For Work. If you're about to post something inappropriate for a shared office environment, then don't post it. No ads, no abuse, and no programming questions. Trolling, (political, climate, religious or whatever) will result in your account being removed.
A movie from 1929 that shows the launch of a three stage rocket to fly to the moon. Earlier in the movie they even showed the flight path of the rocket through the Lagrangian point[^]. And the movie uses a countdown for the first time.
One of my childhood books was the 1963 vintage "The NEW Junior Book" from the Readers Diggable. It might be something published by the Norwegian publishers of the Diggable, but I assume that it was published all over the US dominated world, in different translations (like most books in this class were, in those days).
One of the digests in this book is "Summary of 'First Men to the Moon', (c) Werner von Braun 1958, 1959, 1960", filling no less than 14 large-format pages. I was immensely disappointed when I first discovered that this was a made up history - noone had ever been on the moon! And then, people did land on the moon, but it wasn't at all like the story from Readers Diggable! ...
Then, with Apollo 13, history took revenge! The Werner von Braun story of the meteorite punctuatinhg the space ship created a drama not that different from Apollo 13!
The Diggable book says nothing about where the Werner von Braun story had been published earlier. Maybe it was created for this book alone, 3-5 years earlier, and never published anywhere else.
I can see the overall point. It would be nice to have more technically-minded people in what are traditionally considered non-technical roles since the duties of those roles are inextricably linked to some degree with technical details, but I disagree with shoving PM+BA duties entirely onto lead devs in all but the smallest of projects. There are only 24 hours in a day.
Good point. If a lead who is a software engineer cannot distill the PM and BA duties down to about 30% of their time, then they are not right for a “Soup to nuts” lead.
I know this approach is feasible because I have done it and known others who did it, and did it well. But many, perhaps more than half of, software engineers just do not have (or want) the multidisciplinary knowledge, skills, and abilities to do it well.
Seriously? The entire march of history is about economic specialization. If someone is great at software, why saddle them with product management, project management, or other things suggested in this article? Those roles should be filled by people who are also good at those roles, but they don't make someone a software team lead from a technical standpoint.