oh god how did this get here i am not good with computer

 


 

Background music:
Click here because I can't put an audio widget in the profile

 

The scenes with the shark are usually very intense and disturbing.

 

I use Arch BTW

 

Fun fact: Neo-Nazi dipshit cartoonist Stonetoss is in fact Hans Kristian Graebener of Spring, Texas


vogon
@vogon

the unfortunate things they don't tell you about You Aren't Gonna Need It are that:

a) you might actually need it though
b) the longer before you realize you actually needed it -- the closer you get to being right that You Weren't Gonna Need It -- the harder the work to unwind the assumption will be
c) being wise enough to think in the moment that You Weren't Gonna Need It doesn't get you a discount on that work


DecayWTF
@DecayWTF

"YAGNI" is so rarely actually the right answer, at least by itself.

  • How much is it going to cost to do it now vs later (see points a, b c)?
  • Is implementing it vs not implementing it going to change whether you need it?
  • Conversely, what if it's something you absolutely never, ever want to happen? Maybe it's worth investing in something else so that no one ever needs it.

You must log in to comment.

in reply to @vogon's post:

i have a notes file in every hobby project labeled "the stuff that gathers at the bottom of the sink" and it's just every code block I deleted that i might need an easier way to find than digging through git.

Yeah XP is absolutely garbage for pulling single principles from, all of their ideas strongly depend on the other ideas being implemented at the same time and scale. YAGNI only works well if you're constantly refactoring as you go and make allowances for that in estimations, which is way harder to convince leadership to budget time for, so you end up with just the corner-cutting bits.

That's a great way to put it, dang.
It's been such an uphill battle convincing people to actually do the refactoring part, but I never connected the two together.

tbh i find myself explaining yagni as: please don't write a plugin system, or a subclass hierarchy, or anything where you find yourself saying "we can just extend it"

as well, those are the things people keep writing that no-one needs

d) entire generations of programmers raised on YAGNI being this cherished wisdom have been enculturated to believe that any time they invoke it, they are automatically Right, even in cases when they're very much not (because culturally, professional programming is often about projecting competence and intelligence even and especially when you're just winging it and/or insecure about your abilities)

in reply to @DecayWTF's post: