I've recently shifted from a straight engineering job to a job with a "dev/ops" title. What I have discovered in operations land depresses me. The shoemaker's children are going unshod. Operations software is terrible.
What's driving me craziest right now is my monitoring system.
What I have right now is Nagios.
| /* | |
| A Goroutine safe pattern using channels that abstracts away the channels | |
| This is a concept of creating a goroutine safe object that uses channels under the covers to communicate | |
| with the internal map[string]string structure. I know that typically this kind of solution may done | |
| with mutexes but the excercise was in using channels on purpose although they are heavier. | |
| Note a couple of points: | |
| - When using channels, you can still build a public-facing api that nicely abstracts them away, therefore |
Ideas are cheap. Make a prototype, sketch a CLI session, draw a wireframe. Discuss around concrete examples, not hand-waving abstractions. Don't say you did something, provide a URL that proves it.
Nothing is real until it's being used by a real user. This doesn't mean you make a prototype in the morning and blog about it in the evening. It means you find one person you believe your product will help and try to get them to use it.
| #!/usr/bin/python | |
| import sys | |
| code = """#!/usr/bin/python | |
| import sys | |
| code = {0}{1}{0} | |
| def initial_solution(): |