1 |
[q]dude. i totally would, but im invested in something else rn. [/q]
|
1 |
[q]dude. i totally would, but im invested in something else rn. [/q]
|
2 |
\n
|
2 |
\n
|
3 |
(I feel ya, just don't forget that reading others' code can take a lot of personal energy, especially if your audience is themselves invested in something else ;). Finding ways to lower the energy cost for others (eg, visualizations!) is helpful because it builds context (or narrative, or expectation, pick your poison) at a relatively low energy cost.
|
3 |
(I feel ya, just don't forget that reading others' code can take a lot of personal energy, especially if your audience is themselves invested in something else ;). Finding ways to lower the energy cost for others (eg, visualizations!) is helpful because it builds context (or narrative, or expectation, pick your poison) at a relatively low energy cost.
|
4 |
\n
|
4 |
\n
|
5 |
Made
the
same
mistake
just
this
Monday
at
work
by
posting
a
bunch
of
data
analysis
with
minimal
context
to
help
build
a
mental
picture
to
understand
the
underlying
context
--
the
stuff
that
my
audience
is
normally
used
to.
So
even
though
the
analysis
was
compelling
to
*me*,
just
on
its
own,
it
was
like
sifting
through
mud
for
my
audience.
And
now
my
week
has
been
working
on
the
"fluff"
stuff.
.
RIP.
|
5 |
Made
the
same
mistake
just
this
Monday
at
work
by
posting
a
bunch
of
data
analysis
with
minimal
context
to
help
build
a
mental
picture
to
understand
the
underlying
context
--
the
stuff
that
my
audience
is
normally
used
to.
So
even
though
the
analysis
was
compelling
to
*me*,
just
on
its
own,
it
was
like
sifting
through
mud
for
them.
And
now
my
week
has
been
working
on
the
"fluff"
stuff.
.
RIP.
|
6 |
\n
|
6 |
\n
|
7 |
It sucks, but them's the bends.)
|
7 |
It sucks, but them's the bends.)
|