YOLO-Driven Development Manifesto
andersoncardoso.github.io
YOLO-Driven Development Manifesto
1–10 of 75 posts
Re: YOLO-Driven Development Manifesto
#2[deleted]
Re: YOLO-Driven Development Manifesto
#3I 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
#4I agree with most of these in general, but when combined to a Manifesto, I can't help but feel like this is somewhat satrical
[deleted]
Re: YOLO-Driven Development Manifesto
#5This is just "cowboy coding".
Re: YOLO-Driven Development Manifesto
#6I agree with most of these in general, but when combined to a Manifesto, I can't help but feel like this is somewhat satrical
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
#7>No Documentation, No Problem
>Who needs documentation when you have the power of intuition? YOLO-Driven Development encourages you to keep your genius solutions locked away in your head. After all, real developers don’t read documentation; they conjure it from thin air.
Apparently this style of development has already become very popular as almost none of the projects that I look at have any documentation at all.
Re: YOLO-Driven Development Manifesto
#8This goes great with my vibes-based coding style.
Re: YOLO-Driven Development Manifesto
#9>No Documentation, No Problem >Who needs documentation when you have the power of intuition? YOLO-Driven Development encourages you to keep your genius solutions locked away in your head. After all, real developers don’t read documentation; they conjure it from thin air. Apparently this style of development has already become very popular as almost none of the projects that I look at have any documentation at all.
sure they do, you have the sourcecode don't you?