I can't tell if this is a joke or not. Help.
Most of it is. Minus the documentation part.
YOLO-Driven Development Manifesto
51–60 of 75 posts
Re: YOLO-Driven Development Manifesto
#52Earlier quoted context omitted.
so long as we can read the source code AND debug the program, it's ok. it may be difficult, but sometimes things are difficult free and open source but private and paid for documentation???
The React Flow library has free documentation, but more extensive tutorials on how to use their library are part of their paid offering. (More about their model here: https://reactflow.dev/blog/asking-for-money-for-open-source/ .)
this actually may help me clear out a subtle distinction:
the documentation has the same socialpolitical problem as any other artistic expression encoded into a digital asset
but the code has a subtly different socialpolitical problem that goes a little bit further than the one of 'mere' digital assets.
I don't expect to be understood, I just wrote this to think to myself... albeit in public.
Re: YOLO-Driven Development Manifesto
#53Absent the part about sprints, this describes the majority of professional software development that I've been a part of. Not all of it, but most. There are two sides to the coin of #1. At a certain point, you just have to dive into the problem to actually understand the true nature of it. Some programmers will over-plan things and end up astonished when they actually start coding and find a bunch of edge cases nobod…
> If you don't want to read comments, then use an IDE that can collapse all the comments at once.
This will almost ensure that code and comments get out of sync!
Re: YOLO-Driven Development Manifesto
#54Honestly, this is the way most early stage startups operate, other than this one:
> 2. All Nighters over All Sprints
(and some early stage startups operate that way too)
These practices are all bad as a company scales - you need tests to prevent regressions as the code base grows, documentation to avoid repeating yourself, product managers making informed product decisions, etc. But when you have just a handful of employees, and a handful of customers, and are trying to rapidly find product market fit before your angel round runs out, YOLO-Driven Development is where it’s at.
Re: YOLO-Driven Development Manifesto
#55Earlier quoted context omitted.
New girl where I work did automated doc generation, good class coverage, gitlab wiki uploaded on CI. All alone. I was ecstatic.
[flagged]
There’s far too much sexism in our industry for this to even begin to be a joke to be made, let alone that it shouldn’t be made in the first place.
Re: YOLO-Driven Development Manifesto
#56I have never quite understood YOLO as it is used. Why would I do something especially risky while realizing I only live once? If I had 10 lives, I would take many risks, but since I only live once, I will try to make a reasonable balance between risk and reward.
Re: YOLO-Driven Development Manifesto
#57Developing software is hard. That's why they pay people money to do it.
Re: YOLO-Driven Development Manifesto
#58Honestly, this is the way most early stage startups operate, other than this one: > 2. All Nighters over All Sprints (and some early stage startups operate that way too) These practices are all bad as a company scales - you need tests to prevent regressions as the code base grows, documentation to avoid repeating yourself, product managers making informed product decisions, etc. But when you have just a handful of em…
Yep — scope creep is the only other one I’d say early stage startups should avoid.
But everything else is fine. Just talk to users too.
Re: YOLO-Driven Development Manifesto
#59Earlier quoted context omitted.
Some problem domains are inherently complex and the code written for them needs documentation. Some are not but get complicated during the design process and perverted into abominations that wouldn't have required documentation if the design and source were more readable. I'm inclined to say that if you name things obviously and avoid cutesy idioms (AOP/reflection magic, ridiculous object hierarchies, etc) that code…
That’s the theory. In real life, code is written by teams with different levels of skills over multiple periods of time. Expressiveness is a really hard skill that take years to master and that few people have and that you can only learn by yourself.
I don’t think it’s that hard to learn actually. This works:
1. Before writing a class or a function write comments about what the code will do (unless it’s absolutely trivial)
2. Check if the comments make sense
3. Write the code
That simple practice almost guarantees understandable code.
Re: YOLO-Driven Development Manifesto
#60Earlier quoted context omitted.
[flagged]
There’s far too much sexism in our industry for this to even begin to be a joke to be made, let alone that it shouldn’t be made in the first place.
Why is this sexism? It's a damn joke.
If a woman made this same exact comment about "smashing" a male colleague, would you label it as sexist, too?
Or are only men ever "sexist"?