My favorite YOLO-Driven Development practice (from a former employer) was Customers as QA. We would write code, build the code, and ship it to the customer, then the customer would run the code, file bugs for what broke, and we would have a new build ready next week.
It provides many benefits:
No need to hire QA engineers.
Focuses developer debugging time on features actually used by customers instead of corner cases that no customer is hitting.
Developers deliver features faster instead of wasting time writing automated tests.
Builds are faster because “test” stages are no-op.
One time a developer was caught writing automated tests (was not sure in the correctness of his code, a sign of a poor developer). Our manager took 15 minutes out of his busy day to yell at him about wasting company resources and putting release timelines in jeopardy.
Nah, industrial and infrastructure should mostly use BSD. And “Never see a command line” consumer OS’s should generally be forks from Linux or other FOSS. Most Linux distros have come a long way and are ready for gaming prime time, but fail the “80 year old grandma who wants to digitise her record collection but is a bit unclear on double-clicking” test.
Is the litmus test for programmers. When they start referring to “AI” as a clearly defined concept, you know they’re artlessly making shit up for a quick buck.
programmer_humor
Active
This magazine is from a federated server and may be incomplete. Browse more on the original instance.