21–30 of 75 posts
Gotta go fast. Somewhere out there a competitor is eating your lunch. Now is better than later. Later is better than never. Avoid anything that slows you down: thinking, testing, fixing bugs, writing code.
>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.
Gotta go fast. Somewhere out there a competitor is eating your lunch. Now is better than later. Later is better than never. Avoid anything that slows you down: thinking, testing, fixing bugs, writing code.
im building an app that just generates an email signup and spams crunchbase with a weirdly worded pdf / sales deck.
Gotta go fast. Somewhere out there a competitor is eating your lunch. Now is better than later. Later is better than never. Avoid anything that slows you down: thinking, testing, fixing bugs, writing code.
Earlier quoted context omitted.
It's funny that its satirical, but I could make an argument why every point is actually a good thing.
Really? In which context?
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.
Earlier quoted context omitted.
It's funny that its satirical, but I could make an argument why every point is actually a good thing.
Really? In which context?
>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.
it may be difficult, but sometimes things are difficult
free and open source but private and paid for documentation???