News for hackers. Stuff that matters.
Re:YOLO-Driven Development Manifesto by markwu2001 on Thursday August 17, 2023 @12:35PM (#37164310)
I agree with most of these in general, but when combined to a Manifesto, I can't help but feel like this is somewhat satrical
Re:YOLO-Driven Development Manifesto by grumblingdev on Thursday August 17, 2023 @01:02PM (#37164772)
It's funny that its satirical, but I could make an argument why every point is actually a good thing.
Re:YOLO-Driven Development Manifesto by darkwater on Thursday August 17, 2023 @01:12PM (#37164958)
Really? In which context?
Re:YOLO-Driven Development Manifesto by acumenical on Thursday August 17, 2023 @01:36PM (#37165339)
Probably not what the parent poster was talking about, but fear is a great inhibitor. Excessively high standards for documentation and depth of scope might inhibit less experienced engineers, and nitpicking about scope is a pointless waste of time that ends up being a managerial excuse for more meetings especially if it's brought up endlessly when the core feature does not yet work. This promotes a culture of fear which can paralyze a team of engineers and all you end up getting out of them is the bare minimum.

Or something like that.

Re:YOLO-Driven Development Manifesto by tra3 on Thursday August 17, 2023 @01:22PM (#37165134)
The “move fast and break things” context. Ship it now, make butt load of money by over promising and under delivering. No need for testing or docs. Adding half baked features, you only live once.
Re:YOLO-Driven Development Manifesto by rco8786 on Thursday August 17, 2023 @01:22PM (#37165125)
Basically any startup
Re:YOLO-Driven Development Manifesto by samus on Thursday August 17, 2023 @01:52PM (#37165543)
Prototyping can be a great way to explore the solution space. Just make sure to learn as many lessons as possible and then burn the prototype with fire.

Startups almost by definition face a literal deadline. They critically depend on people who code 80h per week instead of partying.

The impact of UI changes can be hard to measure. If the deployment platforms are very heterogeneous, it's literally impossible to test all scenarios. In these cases it makes sense to roll out slowly and find ways to measure the impact. Or to limit the fallout.

Sometimes, simple solutions get the job done perfectly well and run for years with manageable upkeep. It's a slippery slope though.

It can be very difficult to capture the domain knowledge and the insight of developers and operations people in documentation. Documenting will bog them down instead of getting things done. Managing the bus factor and training up people ahead of time is crucial.

Re:YOLO-Driven Development Manifesto by reidjs on Thursday August 17, 2023 @02:24PM (#37165945)
I find it hard to believe that the most successful startups are the ones who code 80h per week unless you guarantee that the output of the code is big $$$
Re:YOLO-Driven Development Manifesto by samus on Thursday August 17, 2023 @02:31PM (#37166027)
You have to convince your stakeholders that further investment is worth it. But I also think that the "go big or go home" strategy comes from seriously messed-up incentives. It might be justified if the margin is very low or if aquiring a big user base for other purposes is the actual goal.
Re:YOLO-Driven Development Manifesto by jtsiskin on Thursday August 17, 2023 @01:54PM (#37165561)
https://levels.io is famously very successful with this approach
Re:YOLO-Driven Development Manifesto by DrDroop on Thursday August 17, 2023 @01:36PM (#37165330)
You can tell this is satire by the fact that it is a manifesto, it is a literary form only used by the other side, we yolo'er don't have time for those. There is a lot of nuance to breaking rules but most people can't think for themselves so they just shouldn't do that. Sort of like the saying the psychotic drawn in the water in which in mystic swim.