Stop IPv6 Google traffic
alter3d at alter3d.ca
Sun Apr 10 21:00:15 UTC 2016
I don't think it's "groupthink" so much as it is "the mark of
experienced tech people who are good at their job".
At $DAYJOB, a HUGE part of my time is spent as a "technical firewall" --
stopping the company from blindly implementing something based on
incomplete information. When someone comes to me and says "I need to do
$X in the dev/QA/prod environment", my first question is "What are you
trying to accomplish?" A good percentage of the time, it turns out
that Group A didn't talk to Group B, and the requirements were
misunderstood -- after discussion, we end up NOT implenting their
original request, and either implement it in a different way, implement
a solution to a completely different problem, or do nothing at all.
All of the really good technical people I know have learned to do this
through experience, and the habit of asking "What are you REALLY trying
to do here?" is ingrained in their response to any question.
The only thing worse than a half-baked question is running full tilt
into a wall with a half-baked solution to a half-baked question.
On 4/10/2016 3:33 PM, bzs at theworld.com wrote:
> <RANT level=MINOR>
> Ya know, this is the problem with this kind of list groupthink.
> Who cares what his motivations are unless he asks for help with that
> underlying problem?
> Do you (plural, whoever is replying) know the answer to his question
> or where to find the answer or not?
> It seems like every technical list is over-run with
> meta-conversations, how do I (blah), WHY WOULD YOU WANT TO (blah)?!?!
> Often in a sort of accusatory tone, only someone dumb would want to
> I think the answer is to disable IPv6 in the web server config or
> startup (see flags) but hey I just thought I would meta the meta.
> Sorry but I went through about an hour of looking for some way to
> trace systemd and all I found on various lists in answer to others
> asking the same thing was why would you want to trace systemd? Is this
> a standard package causing problems if not then use the standard
> package and if there is none then don't use that software (wow what a
> good answer...not), or a lot of "it must just be something simple you
> don't need to trace anything" (which was probably true but kind of
More information about the NANOG