News for hackers. Stuff that matters.
Re:How the Boeing 737 Max disaster looks to a software Devel... by ken on Thursday April 18, 2019 @06:00PM (#19695180)
We seem to have very different experiences. Every manager I ever had (including one at Boeing) has pushed me to ship software that wasn't at all ready, on the basis that the UI of the prototype looked good.
Re:How the Boeing 737 Max disaster looks to a software Devel... by inflatableDodo on Thursday April 18, 2019 @06:43PM (#19695449)
I am terrified these days of showing anything that looks like something that works to a project manager or client, without covering it in warning graphics.

Even photoshop mockups of UIs, introduced as, "Here's a photoshop mockup of the UI, what do you think?" will get some people to demand that it be shipped immediately.

Re:How the Boeing 737 Max disaster looks to a software Devel... by outworlder on Thursday April 18, 2019 @08:45PM (#19696110)
One thing that I've learned (from someone else) is that unfinished software should look unfinished. Even if you have to muck around with CSS, disable some buttons here and there, maybe add something out of place.

If the UI looks perfect, then everyone will deem it to be finished, even people who should know better.

Yes, I'm advocating knowingly crippling demos. Your master branch may have something prettier, but take a sledgehammer and uglify the bastard before showing to decision makers.

Re:How the Boeing 737 Max disaster looks to a software Devel... by WalterBright on Thursday April 18, 2019 @06:19PM (#19695309)
If you were your own manager for your own code, you'd do it to. I'm unaware of any data showing managed software development is buggier than programmers working by themselves, and my experience is it is less buggy.

Programmers by default tend to want to work on the fun stuff in a program, and neglect the unfun pedestrian stuff. This is where managers step in to improve things.