Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add spanish readme and first intro #35

Merged
merged 3 commits into from
Apr 8, 2019
Merged

Add spanish readme and first intro #35

Show file tree
Hide file tree
Changes from 2 commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
9e5b65e
Add spanish readme and first intro
marc-gr Apr 4, 2019
7e4e6c8
Change spanish version with suggestions
marc-gr Apr 5, 2019
5f032f3
Change spanish version with more suggestions
marc-gr Apr 8, 2019
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
33 changes: 33 additions & 0 deletions README-es.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,33 @@
# go-perfbook

[![Cómprame un café](https://www.buymeacoffee.com/assets/img/custom_images/orange_img.png)](https://www.buymeacoffee.com/dgryski)

Este documento describe las mejores prácticas para escribir código de alto rendimiento en Go.

Las primeras secciones cubren cómo escribir código optimizado en cualquier lenguaje.
Las secciones posteriores cubren las técnicas específicas de Go.
marc-gr marked this conversation as resolved.
Show resolved Hide resolved

### Versiones en varios idiomas

* [English](README.md)
* [中文](performance-zh.md)
* [Español](README-es.md)

### Tabla de contenidos

1. [Escribir y optimizar código en Go](performance-es.md#escribir-y-optimizar-codigo-en-go)

### Cómo contribuir

Este es un libro en desarrollo sobre rendimiento y optimización en Go.
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Este es un libro en desarrollo de software especializado en rendimiento y optimización en Go

Copy link

@grevych grevych Apr 6, 2019 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think the word desarrollo actually refers to the state of the document. The document is under development.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As I understood in the original text, the work-in-progress refers to the book itself. I find the suggestion changes the original meaning in this case. WDYT?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🤔 I think the current version is clear enough about the book been under development.


Hay diferentes maneras de contribuir:

    1) agregar o resumir los recursos en el fichero [TODO](TODO)
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Agregrar o resumir los recursos en el archivo/folder

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As much as I like archivo way better than fichero, in Spanish the right translation for file is fichero (to the best of my knowledge). I wouldn't use folder.

    2) agregar puntos o nuevos temas a cubrir
    3) completa las secciones en el libro escribiendo el contenido
marc-gr marked this conversation as resolved.
Show resolved Hide resolved

Eventualmente se necesitarán ejercicios y ejemplos de programas para optimizar (tal vez).

La coordinación se realizará en el canal #performance del slack de Gophers.

1 change: 1 addition & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -11,6 +11,7 @@ The later sections cover Go-specific techniques.

* [English](performance.md)
* [中文](performance-zh.md)
* [Español](README-es.md)

### Table of Contents

Expand Down
22 changes: 22 additions & 0 deletions performance-es.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,22 @@
# Escribir y optimizar código en Go
marc-gr marked this conversation as resolved.
Show resolved Hide resolved

Este documento describe las mejores prácticas para escribir código de alto rendimiento en Go.

Si bien se discutirán maneras de optimizar servicios individuales (almacenamiento en caché, etc.), el diseño de sistemas distribuidos de alto rendimiento está fuera del alcance de este trabajo. Ya hay buenos textos sobre monitorización y diseño de sistemas distribuidos. Este tema abarca un conjunto completamente diferente de investigación y concesiones en el diseño.
marc-gr marked this conversation as resolved.
Show resolved Hide resolved

Todo el contenido está sujeto a licencia bajo CC-BY-SA.

Este libro está dividido en diferentes secciones:

1. Consejos básicos para escribir software que no sea lento.
* Temas básicos de Ciencias de la Computación
2. Consejos para escribir software rápido.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

s/rápido/veloz/. While they are synonyms, software rápido sounds more like fast software, whereas software veloz to me sounds more like performant software.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I doubt about this one, since the original text is fast software here. If in any case makes for a better understanding I am ok changing it.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

WDYT about this one @rocajuanma?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Right, fast software == software rápido but escribir software rápido could be interpreted as write software in a fast way.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@inkel has a very good point here. I personally like ‘software rápido’, but it could be misleading.

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What about something like: Consejos para escribir software eficiente?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I opted for eficiente in the end as a middle ground as @grevych suggested

* Secciones específicas de Go sobre cómo obtener lo mejor del lenguaje
3. Consejos avanzados para escribir * software realmente * rápido
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Again, I'd replace rápido with veloz.

* Para cuando tu código optimizado no es lo suficientemente rápido.
marc-gr marked this conversation as resolved.
Show resolved Hide resolved

Podemos resumir estas tres secciones como:

1. "Sé razonable"
2. "Sé deliberado"
3. "Sé peligroso"