Why did I join source{d}? Francesc #177
Conversation
| title: "Why did I join source{d}? - Francesc Campoy" | ||
| draft: true | ||
| description: "The first post of a series on why multiple employees joined source{d}. This one is by Francesc Campoy." | ||
| categories: ["why-i-joined"] |
There was a problem hiding this comment.
Should this post appear in our landing, under the "culture" category?
If so, it should be also categorized as culture
| date: 2018-01-15 | ||
| title: "Why did I join source{d}? - Francesc Campoy" | ||
| draft: true | ||
| description: "The first post of a series on why multiple employees joined source{d}. This one is by Francesc Campoy." |
There was a problem hiding this comment.
The article lacks image, what breaks our listings. What if we ask our designer for a header to this kind of posts?
There was a problem hiding this comment.
I copy pasted and totally forgot about the images, good catch!
Adding them now.
| [proposal](https://github.com/golang/go/issues/14595) after an analysis of | ||
| how many times we could find an equivalent piece of code on GitHub. | ||
|
|
||
|  |
| - ML: building and training models that can power complex applications. | ||
| - applications: finding the use cases that allows us to prove the power of the platform, while providing as much benefit to the community as possible. | ||
|
|
||
|  |
| - building tools powered by ML on code, and of course | ||
| - using those developer tools to analyze and improve source code. | ||
|
|
||
| source{d} is building a platform by *developers* where *developers* can build tools for *developers* [[1]](https://www.youtube.com/watch?v=KMU0tzLwhbE). |
There was a problem hiding this comment.
what if we embed the video? would it be too funny? :P
There was a problem hiding this comment.
I think it's better to keep it as a surprise, people click without knowing what they're gonna get and...
|
About links: could we consider using descriptive links, as it was suggested by Ricardo? or does it only affects our documentation? |
|
Feedback applied, thanks @dpordomingo |
|
Thank you for summarizing the links! The only thing I miss is the post image (otherwise it will break our listings) |
|
Maybe @ricardobaeta can suggest an image that we can use for all the "why I joined source{d}" blog posts to come? |
|
Sure @campoy! Let me read the article for insights on a rationale. Thanks for the mention :) |
|
@campoy I think I get the picture. I'll work on some approaches tomorrow - because we have the 15th as a deadline :) |
|
Hi Francesc! I’m sorry but today was underwater. I will work on the image Monday Morning. What would be the best time for you to publish the post?
…On 11 Jan 2018, 22:01 +0000, Francesc Campoy ***@***.***>, wrote:
Maybe @ricardobaeta can suggest an image that we can use for all the "why I joined source{d}" blog posts to come?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
|
|
We can also publish this a bit later, I'm currently working on the schedule for the blog |
|
@campoy You can view the changes in our Slack #design channel. |
|
Cool! I love it. Could you send a PR adding the image somewhere in the blog so we can use it in the future? |
|
@dpordomingo I've created this image to address this need. The only remark is that I found it impossible to work on a canvas of 90px height like we have now. So the approved image has 157px height. Is it possible to adapt the code of the blog to, as from now, display images with this size? I would say that it's an improvement. What do you think?
@campoy Here's the mockup with the template image. Let's just wait for David's feedback to move forward to the PR.
|
|
Hey @ricardobaeta please avoid links to private resources (such as a private slack channel) from public repos :) |
|
What did just happen here? I pushed a new version to my fork and this happens? 😕 |
|
Please review #189 |
required by #175
It can be reviewed in staging at https://blog-staging.srcd.run/post/why-i-joined-sourced-francesc/