- Tests Pass - Code must work correctly
- Reveals Intention - Self-documenting, readable code with clear names
- No Business Logic Duplication - Eliminate redundant business logic (code repetition OK for clarity)
- Fewest Elements - Keep solutions simple
| package main | |
| import ( | |
| "fmt" | |
| "log" | |
| "os" | |
| "os/exec" | |
| ) | |
| const ( |
En Alea Soluciones buscamos nueva compañera o compañero para relación estable dentro del equipo de desarrollo/sistemas; nos gustaría que dicha relación esté basada en la confianza, transparencia, empatía y en la pasión que todos compartimos por nuestra profesión.
TL;DR Como explicamos más adelante, buscamos un perfil principalmente técnico, por favor abstenerse perfiles de gestión, marketing y similares.
Estos son los valores que como equipo más apreciamos, aunque por supuesto, no son los únicos
- Transparencia
- Respeto
- Colaboración
| #!/usr/bin/env python | |
| import boto, boto.jsonresponse | |
| conn = boto.connect_sts() | |
| e = boto.jsonresponse.Element() | |
| boto.jsonresponse.XmlHandler(e, conn).parse(conn.make_request('GetCallerIdentity',{},'/','POST').read()) | |
| e['GetCallerIdentityResponse']['GetCallerIdentityResult']['Account'] |
Hi there!
The docker cheat sheet has moved to a Github project under https://github.com/wsargent/docker-cheat-sheet.
Please click on the link above to go to the cheat sheet.
| Latency Comparison Numbers (~2012) | |
| ---------------------------------- | |
| L1 cache reference 0.5 ns | |
| Branch mispredict 5 ns | |
| L2 cache reference 7 ns 14x L1 cache | |
| Mutex lock/unlock 25 ns | |
| Main memory reference 100 ns 20x L2 cache, 200x L1 cache | |
| Compress 1K bytes with Zippy 3,000 ns 3 us | |
| Send 1K bytes over 1 Gbps network 10,000 ns 10 us | |
| Read 4K randomly from SSD* 150,000 ns 150 us ~1GB/sec SSD |
This gist is part of a blog post. Check it out at:
http://jasonrudolph.com/blog/2011/08/09/programming-achievements-how-to-level-up-as-a-developer
A database where you PUT/POST documents to trigger replications and you DELETE to cancel ongoing replications. These documents have exactly the same content as the JSON objects we used to POST to /_replicate/ (fields "source", "target", "create_target", "continuous", "doc_ids", "filter", "query_params".
Replication documents can have a user defined "_id". Design documents (and _local documents) added to the replicator database are ignored.
The default name of this database is _replicator. The name can be changed in the .ini configuration, section [replicator], parameter db.