On 11/18/14 06:12, Adam Moskowitz wrote:
Would you please take a few moments to send me a description of the
programs you've written in the last 3 or 6 or 12 months? Specifically,
would you please send me the following:
* language used
* number of lines
* very brief description (< 140 chars? :-) of what
the program does
* who runs the program:
1) you, from the command line
2) people in your group, from the command line
3) people outside your group, from the command line
4) "the system" via anything from cron to whatever
config management system you use
5) it's a web app
6) other
last 12 months:
Language Used: Python, Go, Perl.
Number of Lines: Hard to say. A good 2-3k probably, all told. That's a
lot less than I wanted to do, I've got a lot of projects sitting on the
back burner that I've been unable to get to due to the complexities of
region launches etc. I'm a problem solver, I love getting my hands
dirty, but at the same time I'm lazy and I want to write stuff to reduce
how much work I have to do when I am problem solving.
Brief(ish) Description:
Perl has mostly been for log diving, which it is ideally suited for.
Not many of the sysadmins I work with have any grasp of perl, so it
tends to fall to me. Learnt a bunch about profiling and writing high
performance code.
Python (the preferred language for scripting in my team) is all stuff I
can't talk about, it's mostly enhancements for existing tooling, and a
significant number of lines has been adding and expanding tests for
existing scripts (tests are good. We should write more tests.)
Golang has mostly been side projects at work, re-writing various
existing utility scripts from ruby or perl, like a command line
histogram generator (orders of magnitude faster, which is valuable when
you're dealing with large scale data). As much as anything, though,
it's mostly been an exercise for me in learning a new language, and
getting to grips with a typed, statically compiled, language. One of
the advantages of doing it on work stuff is that it has to go through a
code review process, and that typically involves developers as well as
sysadmin types.
Who runs the program(s): sysadmins, developers and managers.
Everything I've written has been a command line tool, most of it to
solve a particular problem. With on-call and ops burden shared by the
entire team that means almost everyone will have used my scripts at some
point or another. I've plans to work on some web based tools next year,
and some time already pencilled in for the purpose.
Paul
_______________________________________________
Tech mailing list
Tech@lists.lopsa.org
https://lists.lopsa.org/cgi-bin/mailman/listinfo/tech
This list provided by the League of Professional System Administrators
http://lopsa.org/
