Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

YOLO-Driven Development Manifesto

andersoncardoso.github.io

Post reply on HN
Print view View original

61–70 of 75 posts

Re: YOLO-Driven Development Manifesto

#61

Post by dier »

singlow wrote: post #56

I 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.

It is picking the adventure over playing it safe. "You only live once so you just as well pick the once in a lifetime, most exciting, or whatever experience." What an author finds exciting and YOLOs may be above your risk tolerance.

For this article it's "Life is short so I'm going to favor doing the things I enjoy (releasing something at "it works!", add a feature because it sounds fun, wear socks that don't match) and not the things I don't enjoy (documentation, tests, collaborating/compromising with others...)"

Re: YOLO-Driven Development Manifesto

#63

Post by deathanatos »

kiernanmcgowan wrote: post #45

Real engineers force push to production at 4pm on a Friday because they don’t write bugs

I know there's a giant "/s" at the end of that, but omg I am on vacation at the moment reading random HN while I wait for Rimworld to load, and this is too true.

Right before I left, I was getting paged at 7pm on Friday because of a brand new service pushed. Service didn't even start at first, because its image couldn't even be fetched… on Friday. At 7p.

… it's the joke hour(s) of deployments. But at the very least, as an SRE, it'd be appreciated to see at least a mad scramble to claim the page out of a feeling of embarrassment from having just paged the on-call at 7pm¹. But … no … inevitably the only people who do that are the same ones who avoid the 7p deploy…

¹… we used to have a "if you just deployed → you're now on-call for the next 15 min" automation. Miss that automation.

Re: YOLO-Driven Development Manifesto

#64

Post by frollo »

adamisom wrote: post #43
_jal wrote: post #35

Earlier quoted context omitted.

> Expressiveness is a really hard skill that take years to master It is worse than that. Being good at expressive, self-documenting code correlates with strong communication skills and empathy. So programmers who get good at it tend to increase the risk of managerial borgification.

Do you mean they’re more likely to become managers and thus no longer write great code, or something else?

In general, they tend to get snapped up by other corporate roles, either officially (which at least grants them the pay benefits associated with the role) or unofficially.

I know a lot of great coders who ended up doing anything but code because they were the technical people with communication skills.

Re: YOLO-Driven Development Manifesto

#65

Post by singlow »

dier wrote: post #61
singlow wrote: post #56

I 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.

It is picking the adventure over playing it safe. "You only live once so you just as well pick the once in a lifetime, most exciting, or whatever experience." What an author finds exciting and YOLOs may be above your risk tolerance. For this article it's "Life is short so I'm going to favor doing the things I enjoy (releasing something at "it works!", add a feature because it sounds fun, wear socks that don't match)…

I understand that if I only live once I don't want to waste the time I have on things that I don't enjoy. I don't understand when it means rushing into something that could cause immediate catastrophic failure.

In this case it is You Only Launch Once. If I can launch 50 times, I might skip a test since I can just launch again with a fix. If I only get one launch, I am sure as heck going to test it a few times over.

Re: YOLO-Driven Development Manifesto

#66

Post by luticar »

Interested in learn more about those tools. > 4. Duct Tape and WD-40 Are Your Allies

Complex problems require ingenious solutions. In YOLO-Driven Development, you’ll master the art of duct-tape programming and WD-40 debugging. Your codebase will be a monument to human ingenuity, even if it’s held together with virtual spit and glue.

Re: YOLO-Driven Development Manifesto

#67

Post by wheelerof4te »

agentultra wrote: post #18

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-code code is the best. It writes itself.

Re: YOLO-Driven Development Manifesto

#68

Post by neogodless »

singlow wrote: post #56

I 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.

Pragmatically, you will try to optimize the balance.

But throwing out YOLO is merely arguing against "no risk", and regardless of how long you stay alive, never really living. A modern take on "No risk, no reward" with a focus on adventure.

Re: YOLO-Driven Development Manifesto

#69

Post by stephc_int13 »

I read this as sarcasm.

So far I've seen and tested quite a few development methodologies, including a few flavors of Agile, and I've yet to be convinced of their usefulness.

We've been building software for more than half a century, but I think that the true nature of the beast is still not entirely understood.

Re: YOLO-Driven Development Manifesto

#70

Post by munk-a »

beanjuiceII wrote: post #41

as a contractor i enjoy when clients want yolo driven development

Contractors and YOLO code have an interesting relationship. A lot of near-shore contractors are folks who are extremely strong developers... but the main motivation for writing clean code (for non-junior developers) is that you'll need to return to that code in a few weeks months or years - and you've been burned by your own poorly written code in the past. This motivation doesn't really exist for contractors - write once code that does what it says on the tin (no matter how horrific it is internally) will get you your payday.

I've met highly skilled contractors that have produced extremely maintainable code and I've met extremely fast working contractors that have fulfilled the contract and left a pile of spaghetti code in their wake.

Post reply on HN