From: Arne Babenhauserheide <arne_bab@web.de>
To: Tristan Colgate <tcolgate@gmail.com>
Cc: guile-user@gnu.org
Subject: Re: How do you earn money with Guile?
Date: Tue, 12 Jul 2016 22:05:36 +0200 [thread overview]
Message-ID: <87y45662r3.fsf@web.de> (raw)
In-Reply-To: <CAPGZSGK1ZrXfQx232rx5MQT2K-ruEf2QzeKsxAX0_86Q8r4TKA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1998 bytes --]
Tristan Colgate writes:
> To play the game a bit, I earned money writing guile, or rather, I wrote
> guile to earn money. I wrote guile-snmp to manage several large networks.
> guile-snmp was developed to run parts of the NHS.net network (I re-wrote
> several tools back to perl net-snmp for the benefit of colleagues, but
> tools were developed with guile-snmp first, far more quickly, and concisely
> that I could have achieved otherwise). I used and extended it for a 5 or 6
> years and it became by far the best SNMP reporting tool I've ever used
> (yes, I'm biased). I'm no longer in the network management business, and
> SNMP has (unjustly) fallen out of favour, so sadly I don't really do much
> with it any more.
This is really cool!
> More importantly, I learnt an enormous amount about functional
> programming, learned to really lovee lisp (and scheme, and guile). That
> knowledge definitely made me a better programmer. It made me really "get"
> various aspects javascript development that I'd have struggled with
> otherwise. Got me interested in SML and haskell (the alternatives to the
> cult of lambda).
>
> So my time with guile has, indirectly, gotten me plenty of jobs, even if
> the people that hired me didn't know it.
I don’t know how to put that, yet, but this isq a pretty strong
quote. May I quote you on it? (though I’ll for starters only do that on
GNU social and twitter, because it’s easiest there)
I started using Guile to expand the limits of what I can do elegantly in
programming, and I feel that that expanded what I can do — writing three
witches¹ showed me where Programming could be and how much of what I
once considered as how programming works was actually ceremony, even
with Python — though Python still is the "rational" choice for many
problems I face.
Best wishes,
Arne
¹: http://www.draketo.de/english/wisp/shakespeare
--
Unpolitisch sein
heißt politisch sein
ohne es zu merken
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 818 bytes --]
next prev parent reply other threads:[~2016-07-12 20:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-03 9:32 How do you earn money with Guile? Arne Babenhauserheide
2016-06-03 17:33 ` Nala Ginrut
2016-07-12 20:44 ` Arne Babenhauserheide
2016-06-03 17:57 ` Christopher M. Hobbs
2016-06-03 19:24 ` Tristan Colgate
2016-07-12 20:05 ` Arne Babenhauserheide [this message]
2016-07-12 20:30 ` Arne Babenhauserheide
2016-07-12 21:11 ` Amirouche Boubekki
2016-06-07 8:05 ` Jean Crépeau
2016-06-26 21:31 ` Arne Babenhauserheide
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87y45662r3.fsf@web.de \
--to=arne_bab@web.de \
--cc=guile-user@gnu.org \
--cc=tcolgate@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).