Login
You're viewing the functional.cafe public feed.
  • Sep 18, 2026, 9:57 PM

    @jrdepriest

    One of the reasons I chafed at things like AGILE and other stuff was that, while the basic core ideas were solid, there were far, far too many ways that those ideas could be corrupted. "Points" and "Sizes" may be meaningless to us, but to anyone else, they're measurements.

    Likewise, call it what you want ("spike" or whatever) but by the end of the two week sprint, you had to have something to show for your effort that someone else can judge and critique you for. That does not lend itself well to thoughtful design work.

    🙎‍♂️"So, Bob, why did you spend half the sprint changing the design you specified last week?"
    👨‍🦰"Well, I learned a bunch of things last week that required redesigning those things."
    🙎‍♂️"That's not very efficient of you."
    👨‍🦰"Neither would spending several months designing something that doesn't work."
    🙎‍♂️"I don't see your point."

    💬 1🔄 1⭐ 0

Replies

  • Sep 19, 2026, 3:03 AM

    @jrconlin @jrdepriest

    I gather it's been demonstrated multiple times that open-ended, un-mandated research tends to be far more productive in the long run than specific, targeted research aimed at achieving specific goals.

    Unfortunately the latter tends to be favored by the people with the money to •fund• the research....

    💬 0🔄 0⭐ 10
  • Sep 19, 2026, 3:14 AM

    @cavyherd @jrdepriest

    Not really sure I agree, at least not within this context. Open research is different than directed problem solving. Most code is generated toward problem solving, or at least task resolution. That said, even those sorts of things need to be well understood before action is taken.

    If you're just adding a set of numbers, the problem space is pretty limited and sure, you can probably jump right to the code.

    If you're developing a new cryptographic library, things are quite a bit different, and you'd be far better off making sure that you really do understand the problem space and the sorts of ways that those things fail.

    Likewise, if you're building a markup language parser, knowing that there are probably already several dozen out there is probably going to save you a fair bit of effort.

    💬 1🔄 0⭐ 0
  • Sep 19, 2026, 3:16 AM

    @jrconlin @jrdepriest

    Fair. I was thinking research generally, not so much in a coding context. The latter does seem like a suboptimal context for "throw it at the wall & see what sticks."

    💬 0🔄 0⭐ 5
  • 💬 1🔄 1⭐ 0
  • 💬 0🔄 0⭐ 7