Hacker News Reader

Comment by wayneftw | Hacker News Reader

Pffft. Right - because code is not completely mutable at any time during development.

Have you considered that the analogy breaks after the obvious bit?

How does the analogy break? Do you think you can't tear up landscaping? To add a ramp you have to do work to undo the existing landscaping, install the ramp, and then redo the landscaping in a way that fits with the ramp.

The analogy breaks because code is able to be changed at any time almost as easily as writing new code. There is no such thing as landscaping in code. It's all easy to change.

Tearing out code that has already been written (which would be required here) is analogous to tearing out landscaping that has already been installed. You either don't understand accessibility, analogies, or both.

You seem to think that it's completely free of effort and cost to change code. That is absolutely not the case. Some things can be incredibly difficult to add in to a codebase that wasn't designed to expect that kind of change.

> Some things can be incredibly difficult to add in to a codebase that wasn't designed to expect that kind of change.

In a 3 week old code base? Please... You can write the entire thing over again in a week and add what you want during that time.

The commenters here should do that too! It would probably take less effort than bitching about someone's side project that they'll probably never even use here on HN.

And then pee on the floor and do jumping jacks, run in circles, then read a magazine, then install an upside-down lectern in the living room only to realize... you forgot the television.

God save us all!

Reply on news.ycombinator.com