 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Tom Austin wrote:
> It sounds like you are getting / are very involved with Haskell and know
> at least more than me about its inner workings.
>
> FWIW Why not start writing some of the things that you just mentioned
> down and make them available.
>
> You could provide a web site with simple articles explaining some of
> these things.
>
> You could turn it into a <gasp> published book </gasp>.
I have written one or two small things...
http://blog.orphi.me.uk/archives/332
http://blog.orphi.me.uk/archives/49
http://blog.orphi.me.uk/archives/40
http://blog.orphi.me.uk/archives/37
http://blog.orphi.me.uk/archives/38
http://blog.orphi.me.uk/archives/39
http://blog.orphi.me.uk/archives/34
http://blog.orphi.me.uk/archives/32
...just the odd item. I stopped when I realised that nobody ever reads
any of this stuff, because I am the only human alive who gives a ****
about Haskell.
--
http://blog.orphi.me.uk/
http://www.zazzle.com/MathematicalOrchid*
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Orchid XP v8 wrote:
> Tom Austin wrote:
>
>> It sounds like you are getting / are very involved with Haskell and
>> know at least more than me about its inner workings.
>>
>> FWIW Why not start writing some of the things that you just mentioned
>> down and make them available.
>>
>> You could provide a web site with simple articles explaining some of
>> these things.
>>
>> You could turn it into a <gasp> published book </gasp>.
>
> I have written one or two small things...
>
> http://blog.orphi.me.uk/archives/332
> http://blog.orphi.me.uk/archives/49
> http://blog.orphi.me.uk/archives/40
>
> http://blog.orphi.me.uk/archives/37
> http://blog.orphi.me.uk/archives/38
> http://blog.orphi.me.uk/archives/39
>
> http://blog.orphi.me.uk/archives/34
> http://blog.orphi.me.uk/archives/32
>
> ....just the odd item. I stopped when I realised that nobody ever reads
> any of this stuff, because I am the only human alive who gives a ****
> about Haskell.
>
I see that they are under a blog entry for Haskell.
There are 12 entries - but I bet you could write up a bunch more if you
thought about it.
Now, set up a web site that is dedicated to Haskell.
Web site hosting is cheap & setting up an actual site isn't too hard either.
I am saying this because I believe that your interest in Haskell can do
something for you besides being a nerdy pastime.
I am encouraging you to take something that you enjoy and have a passion
for and make it into something.
Who knows, you may actually be able to contribute some significant material.
Now, if I can only take my own advice.
Tom
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
> I see that they are under a blog entry for Haskell.
> There are 12 entries - but I bet you could write up a bunch more if you
> thought about it.
>
> Now, set up a web site that is dedicated to Haskell.
> Web site hosting is cheap & setting up an actual site isn't too hard
> either.
More to the point, I already have a web host. (Guess where my blog is...)
I guess I should work on getting Indoculate working properly again...
Then I can set about writing stuff. ;-)
> Now, if I can only take my own advice.
Well isn't *that* the thing? ;-)
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Invisible wrote:
>> I see that they are under a blog entry for Haskell.
>> There are 12 entries - but I bet you could write up a bunch more if
>> you thought about it.
>>
>> Now, set up a web site that is dedicated to Haskell.
>> Web site hosting is cheap & setting up an actual site isn't too hard
>> either.
>
> More to the point, I already have a web host. (Guess where my blog is...)
>
> I guess I should work on getting Indoculate working properly again...
> Then I can set about writing stuff. ;-)
>
I do believe that you have a wealth of knowledge that others can benefit
from - more than just on a blog or forum.
>> Now, if I can only take my own advice.
>
> Well isn't *that* the thing? ;-)
And having others encourage me and point out some directions makes it
all that much easier.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Tom Austin wrote:
> I do believe that you have a wealth of knowledge that others can benefit
> from - more than just on a blog or forum.
Heh. The hard part is figuring out how to take a big heap of knowledge
and structure it into something coherant with a logical order to is that
somebody else might even be able to follow. ;-)
> And having others encourage me and point out some directions makes it
> all that much easier.
Amen!
Damn, if I had more friends, I'd probably get a whole lot more done... ;-)
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Invisible wrote:
> Tom Austin wrote:
>
>> I do believe that you have a wealth of knowledge that others can
>> benefit from - more than just on a blog or forum.
>
> Heh. The hard part is figuring out how to take a big heap of knowledge
> and structure it into something coherant with a logical order to is that
> somebody else might even be able to follow. ;-)
>
you know the types of things you already have
some blog entries
some programs
etc...
Start putting together some data structure that you can 'copy' your
current data into and then add to at will.
databases
files
etc...
Don't worry to much about making it look perfect - just get the data out
there and have your backend fully functional. You can always change
what a web page looks like - CSS, but it can be a PITA to change how you
store the data.
>> And having others encourage me and point out some directions makes it
>> all that much easier.
>
> Amen!
>
> Damn, if I had more friends, I'd probably get a whole lot more done... ;-)
you do have friends here
you just don't know what they look like ;-)
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
>> Heh. The hard part is figuring out how to take a big heap of knowledge
>> and structure it into something coherant with a logical order to is
>> that somebody else might even be able to follow. ;-)
>
> you know the types of things you already have
>
> Start putting together some data structure that you can 'copy' your
> current data into and then add to at will.
>
> Don't worry to much about making it look perfect - just get the data out
> there and have your backend fully functional. You can always change
> what a web page looks like - CSS, but it can be a PITA to change how you
> store the data.
Hence Indoculate - my tool that accepts a markup language I invented
which exactly matches the structure I want, and turns it into something
that a computer will accept. (Basically HTML or PDF.) But it's currently
broken... *sigh*
>> Damn, if I had more friends, I'd probably get a whole lot more done...
>> ;-)
>
> you do have friends here
>
> you just don't know what they look like ;-)
For somebody as lacking in motivation and self-belief as me, a much
higher level of encouragement would be useful... :-S
I could have written something today, but I've basically spent my entire
day sitting reading web comics because I couldn't be bothered to start
anything. "Who's going to read it anyway?"
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Invisible wrote:
> Tom Austin wrote:
>
>> I do believe that you have a wealth of knowledge that others can benefit
>> from - more than just on a blog or forum.
>
> Heh. The hard part is figuring out how to take a big heap of knowledge
> and structure it into something coherant with a logical order to is that
> somebody else might even be able to follow. ;-)
Tip: don't structure it yet. Start with some content, once you have
something written you may have a clearer view of how to structure it.
I doubt anyone starts writing a book from the index.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Invisible wrote:
> Heh. The hard part is figuring out how to take a big heap of knowledge
> and structure it into something coherant with a logical order to is that
> somebody else might even be able to follow. ;-)
Yes, that's the hard part. :-) It's one of the problems with open source
software that's doing something totally new, where there's two or three
people who know how it works inside and out, and they don't know how to
explain it to someone who doesn't already know what they're talking about.
It's a tremendously useful skill to have: the ability to explain to grandma
(or your boss) what she needs to know about the technology. (That's probably
one reason I use too many analogies - I find they work well with
non-technical people.)
It's also one of the important skills you learn from a PhD.
I'll second the notion that if you can sit down and write something like you
post here, and just churn it out, do so. Getting the ideas down is good.
After that, if you want to go further, sit down and make an outline (as in
"table of contents" type outline). Break it down until the structure has an
entry for each idea, where "each idea" is covered in a paragraph or two.
Then read the outline and make sure someone else could understand it on the
first read through. Then you just fill in the outline.
--
Darren New, San Diego CA, USA (PST)
The NFL should go international. I'd pay to
see the Detroit Lions vs the Roman Catholics.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
>> Heh. The hard part is figuring out how to take a big heap of knowledge
>> and structure it into something coherant with a logical order to is that
>> somebody else might even be able to follow. ;-)
>
> Tip: don't structure it yet. Start with some content, once you have
> something written you may have a clearer view of how to structure it.
>
> I doubt anyone starts writing a book from the index.
Some people might...
Heh, this tends to be *exactly* how I write programs, BTW. But then,
writing documentation is rather like programming... except that instead
of operating with the internal state of a machine, it's a human. But you
still have the same problems of figuring out the best way to structure
things, etc.
I have lost count of how many times I've written an authoritative tome
on Haskell, only to get about 8% of the way through the material and
think "meh, that's a silly approach, I should start by explaining X
first instead of starting from Y..." I've started and restarted writing
so many times I can't even count!
I've said it before and I'll say it again: The trouble with explaining
Haskell is that there's lots of interrelated concepts that you seemingly
need to grasp all at the same time, with no logical "place to start".
--
http://blog.orphi.me.uk/
http://www.zazzle.com/MathematicalOrchid*
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
