teleren/devto huggingface dataset:
Stop Fearing Failure
Published: 2022-01-03 23:17:20

I am going to let you in on a little secret... The best developers are the ones that fail the most.

While this sounds counterintuitive, because people often assume the best developers never fail; I assure you failure is the one of the best teachers in the software engineering industry.

As a developer your job is to solve new and interesting solutions to problems that haven't been solved. When a company assigns you a ticket to complete some task to solve a specific problem, one should anticipate failure multiple times. The company doesn't know exactly how to build it, and you the programmer won't know exactly how to build it.

When I create a new react component and there is not a single error message in my terminal I generally assume I did something wrong. The point of sharing this is that everyone makes many mistakes a day when writing code, and to not make some sort of mistake within newly written code is a rarity. We are humans and its very easy to make wrong assumptions about the data we are manipulating.

My message to any new developers: Do not be scared of failure. When you see an error message break it down to its smallest pieces and use the knowledge you already possess to find a solution. If something peculiar is going on then use your resources, google, stack overflow, or friends to figure out what is going. The only real failure is when you give up completely and FAIL YOURSELF.

In any process of building a technology there are millions of possible solutions. The job for you the developer is to find the solution that is most efficient and right to you...and not to break production. But that is a whole other topic.

My suggestion to new developers who struggle and lose confidence when they receive errors is to get a rubber duck to talk to about your errors. This might sound foolish but tell the duck what you are anticipating should happen, why your code should be working, and why the error should not be happening. During this process you will often figure out what really is going wrong with your code. With this methodology as well as consistent testing solving any problem seems surmountable.

Remember, if developing wasn't stressful and difficult then there would not be a surplus need for developers! Failure is a daily occurrence in our lives and is completely normal. Do not be discouraged and allow errors to help you not only build your developing skills, but your grit and persistence as well.

We are taught in school that failure is the worst thing that can occur to us; however, in development failure in just a stepping stone towards the path of success.

I hope you enjoyed this motivational post and if you are new to this industry you take away the key message I am trying to present.

Have a great New Year, and keep on coding.
Are you ready for your FAANG interview?
Tags: programming, interview, career
Published: 2022-01-03 22:46:11

## Questions to ask yourself

* From 1-10, how confident are you on the different DSA topics?
* For any above an 8, have you tried teaching this concept to anyone else? How confident were you in your class?
* Have you conducted Mock interviews? How many? Do you find yourself getting nervous? Have you been tracking your results?
* What topics give you extra trouble?
* Do you have a structure to how you approach interviews?
* Have you done a mock behavioral interview with someone? From 1-10, How confident are you when it comes to speaking about your experience?
* How many days a week are you solving a programming interview problem?
* (Mid Level and above) From 1-10, How confident are you in System Design?
* (Mid-level and above) From 1-10, Would you consider yourself an expert in the language you plan to interview in?
* How long do you have before your interview?

## Questions I do NOT ask

* How many leetcode problems have you solved?

* How many languages do you know?



You can read a breakdown of the questions[here](https://fangprep.substack.com/p/are-you-ready-for-your-faang-interview)
Insights into a working day of a developer in a project
Tags: codenewbie, productivity, career, motivation
Published: 2022-01-03 22:36:56

Today was my first day on the new project team. Although today's focus was on the setup, I already learned a lot of (useful) things and tools that I didn't know before. (I guess that's the great part of always working in other project teams).

Let me describe today in more detail 🤓

**Daily Scrum Meeting**
I attended the usual Daily for the first time today. The project has been going on for several months and I'm new to it (this is common, people coming and going during the project). All the devs talked about their issues and the latest status.

I had been assigned a mentor 🥰 with whom I set up my laptop. By the way, this is an additional laptop, there is an extra laptop for each project for security reasons. I was given all the access to the tools they use, Microsoft Teams, GitLab, etc.

**Jira**
New for me was that we work with [Jira](https://www.atlassian.com/software/jira), an agile management tool, with Scrum board (there are also other boards like Kanban). There all current issues are entered in the Scrum Backlog, active ones were assigned to a Dev, in the Product Backlog you can find the whole list of all issues. Jira is a very clear and good tool to work effectively as a Scrum team.

As you can see, **[Scrum](https://www.scrum.org/)** is very present, so I recommend you to get familiar with the framework before your first job. It will definitely come across well in the interview if you have already dealt with it. 

**Jenkins**
Furthermore, we use Jenkins, also new for me, with which I guess you can build, deploy and automate the software. I haven't used it yet, so I don't know anything about it.

**CMD Shortcuts**
Shortcuts I learned today in the CMD 📝: when you type 'cd ', you can tab through all the existing folders in your current folder to select the one you want and don't have to remember exactly what the folders are called. And if you want to run an already executed command again, you can tab through all the previous commands and select the one needed with the up arrow key. Very handy, I wish I had known it earlier.

**GitLens**
GitLens was also recommended to me to use. It is an extension in VSC that allows you to run git commands very quickly. It shows available branches, which one has merged into which one and much more. 😵 I have never seen so many branches in one project.... My issue has the number 875 😅

**NVM**
I also had to install NVM, a node version manager. I heard about it for the first time. We use it because webpack doesn't always have the same version in the different branches. And for everything to work, you have to select which node version you want to work with in each branch using e.g. `nvm use 16.13.1`.


Today was great. 🥳 I learned so many new things without writing a single line of code. I'm really looking forward to finally getting started with my issue. 

---
![Thank you](https://docs.google.com/uc?export=download&id=166Ecq6uBl61U14OUlkHOHIBv2ArKoumJ)

_Thanks for your reading and time. I really appreciate it!_
Venmo Search
Tags: atlashackathon
Published: 2022-01-03 22:36:24

### Overview of My Submission
I loaded over 300,000 Public Venmo Transactions into a Mongo Atlas database and use Atlas' Full Text Search to search by transaction memo.
Venmo transactions are interesting for full text search because users have to leave a public memo on every transaction. What relationships can you infer between Venmo users, based on their transaction memo? Are they friends, roommates, family, coworkers, lovers, or something else? 

Deployed Application: 

https://reidjs.github.io/venmo-search-frontend/



### Submission Category: 

Choose Your Own Adventure

### Link to Code

Frontend Repo:

{% github https://github.com/reidjs/venmo-search-frontend %}


### Additional Resources / Info

Backend Repo:

{% github https://github.com/reidjs/venmo-search-server %}

![Deployed application](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/85il9vumlsiht6nhmbap.gif)
Top 7 soft skills that make you a Great Developer
Tags: webdev, productivity, career, beginners
Published: 2022-01-03 22:27:15

To be a great developer you don't need just knowing how to code , and hard tech skills, but also you must have a good soft skills ,so I share with you a list of 7 soft skills that will help you in your work.

**1 - Problem-solving:** you need to have the ability to know  the reason that caused  the probleme , then searching on solution and  fix it .

**2 -Communication:** is most important skill for any developer, becuase you need  to speak  with your colleagues,  managers, customers ,  and also  in meeting , for that  you need to speak clearly with confidence ,therefor spend mush time listening to others persones  and don’t interrupt while somebody is talking,adding to this you need to be patient and focused.

**3 - Time management:** before start your work should to write your to- do-list and set the the priority goals and period time of any task ,moreover take a balance between a work and personal live.

**4 - Creativity:** to be a creative developer you need to try and discover 
different things you never do it before ,such as writing, art, crafts,  cooking,and also practice a lot .

**5 - Patience:** you need to be able to keep calm When your code isn’t working and you can’t figure it out, Or when a code review is taking a long time,  and also when you start to  learn something  new .

**6 - Teamwork:** as a developer, you will work with a wide variety of teams and people for that you need to have a good social skills and communication ,rather than a good speaker and listener.

**7 - Help other:** helping your colleagues and customers is the most thing that make you building a good reputation and relationship in your work .

Do you have other soft skills ? share it with us.

If you enjoyed this article you can follow me on[ Twitter](https://twitter.com/chemlali_assia) where I tweet about web development and freelancing.
Welcoming myself 
Tags: devops, devjournal, devlife
Published: 2022-01-03 22:22:55

Welcoming myself to the community.

Hello everyone, hope you enjoyed your holidays and had some rest to start this year, motivated and full of excitement.

Allow me to introduce myself, my name is Jean Pierre, and I am a computer science student working as a mid-level IT Support. I've started this channel alongside a professional Instagram page, check it out [here](instagram.com/codewithjp), after seeing many developers posting their progress and their setup.

I’ll be sharing my progress over here, alongside some useful tips, just to make sure that I’ll be consistent with my learning phase and progress, you can say that’s my 2022 resolution, to become a better developer and to open up to this lovely dev community.

In case you wish to know what are my skills and what I’ve already learned, I started to learn Java, since they highly recommended at the university to cover the essential of object-oriented languages, and you can say now that I became intermediate in it.

After learning the basic of Java, they started with HTML, CSS and some basic JavaScript, which we used it as a front-end language. Following this, we’ve learned PHP, which I totally forgot, and they made us to develop a fully functional website connected to a database and running on a local host.

During this time, I wasn’t motivated enough, but for an unknown reason, I wouldn’t mind coding all night to finish a project or an assignment, until everything changed a few months ago where I started from 0. I followed freeCodeCamp’s curriculum and finished all the challenges that are related to responsive web design and got an online certificate. After that, I started with JavaScript and learned the basic of ES6, regex and currently learning algorithm, a subject that I already covered during my first years in the university, but I had to pass to it again to refresh my mind, since it’s very important.

So that’s all, now you know everything, I’ll start to post each two weeks, hoping I’ll be able to do the same each week, showing you my progress and sharing some useful tips that you might use during your career.

Enough about me, I would like to know more about you in the comment section, and if you have a professional account you would like me to follow-on Instagram, don’t be shy to share it !
How to setup a RADOS Gateway for an S3 API in Ceph
Published: 2022-01-03 22:22:26

---
title: How to setup a RADOS Gateway for an S3 API in Ceph
published: true
description: We look into how to install the Ceph RADOS Gateway to enable the S3 API on our ceph cluster. Using a gateway in order to simplify the object handling is a usual practice but we will also look into how to setup a region / zone and what is required to sync your data centers.
tags:
cover_image: https://i.ytimg.com/vi/6uX23Q3y_SU/maxresdefault.jpg
---

{% youtube 6uX23Q3y_SU %}

We look into how to install the Ceph RADOS Gateway to enable the S3 API on our ceph cluster. Using a gateway in order to simplify the object handling is a usual practice but we will also look into how to setup a region / zone and what is required to sync your data centers.
Como animar un corazón con keyframes (Básico)
Tags: webdev, beginners, css, animacion
Published: 2022-01-03 22:05:47

Mi intención con esto es explicar como animar el corazón sin tener que dibujarlo con CSS3, en este caso es solo importar un icono o una imagen, esto va más que todo orientado a las personas que están comenzando a probar keyframes ya posteriormente en otro post explicaré como crear el corazón con puro CSS.
Empezamos con lo más simple de todo, el HTML, en este caso yo estare importando de [Font Awesome](https://fontawesome.com/) y tomando este icono `<i class="fas fa-heart"></i>` con esto ya tendremos el HTML.

![Imagen en con fondo blanco y un corazón negro en la esquina superior izquierda](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/672zv2pl52vgnl9khrwq.png)

Ahora, como soy medio flojo agarre un color gradiente de una página web llamada [CSS Gradient](https://cssgradient.io/) y seleccione el que más me gusto, ustedes pueden hacer lo mismo, luego al **body** le di estos estilos para poder centrar el elemento. 
` height: 100vh;
  display: flex;
  justify-content: center;
  align-items: center;`
Hasta este momento vamos de esta forma:

![Imagen con un corazón en el centro de la pantalla de color negro con un fondo que tiene un color gradiente](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/bels0kog96k7xad61uj9.png)

Siguiendo con el corazón, usaré la clase que ya trae cuando importamos el icono para así darle su estilo y luego poder animarlo.
Solo le daremos dos estilos a la clase 
`.fa-heart {
  font-size: 6rem;
  color: #ee2130;
}`

Ya tenemos un corazón.

![Corazón rojo en medio de la pantalla y el fondo es de un color gradiente](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/1ewbchjxs3x8yvkn1rl1.png) 

Pasemos a la etapa final que es animarlo para que parezca que está latiendo.
Para poder usar el keyframe necesitamos darle un nombre al corazón dentro del **CSS** utilizando la misma clase anterior.
También le indicaremos que la animación dure 1s y que se repita de forma infinita.
`.fa-heart {
  font-size: 6rem;
  color: #ee2130;
  animation-name: heart;
  animation-duration: 1s;
  animation-iteration-count: infinite;
}`
Sigamos ahora con el keyframe y le diremos que cuando tenga un 25% tenga una propiedad transform y que escale 1.2 su tamaño original.
`@keyframes heart {
    5% {
        transform: scale(1.2);
}`

{% codepen https://codepen.io/boudgnosis/pen/VwMXNJo %}

Ya con esto parecerá que está latiendo como un corazón normal, como pueden ver es algo sencillo y para nada difícil emplear una animación bien simple.
***
**Pueden seguirme en mis redes sociales por este enlace.**
* [Twitter](https://twitter.com/juan_ariasd)
* [Codepen](https://codepen.io/boudgnosis)
* [Linktr](https://linktr.ee/Boudgnosis)

***
El banner que use [Pankaj Patel](https://unsplash.com/@pankajpatel?utm_source=unsplash&utm_medium=referral&utm_content=creditCopyText) está en la plataforma de [Unsplash](https://unsplash.com/)
y la imagen puntualmente es esta: [banner](https://unsplash.com/photos/SXihyA4oEJs)
Pull or not to pull
Tags: git, agile, programming, codequality
Published: 2022-01-03 22:05:19

Pull requests like they are known from GitHub gets more and more popular in enterprise software development. This workflow also known as dictatorship or with his adaption to dictator-lieutenant, is a well proven process for open source projects. But in my perception - I always ask my self: We do really want this in commercial projects? I don’t think so. Because we already had in the past a tool called IBM Synergy with an equal approach. It was very heavy weighted and companies who used Synergy was looking quite fast to replace the software for better solutions.

Well, pull request now integrated into close to every DevOps tool, for Example Microsoft Azure and so on. Of course they absolutely more light weighted than the IMB Synergy workflow. But there is a big misunderstanding in commercial projects. Tools like Git, Subversion or Bazaar are just a storage for developer collaboration. Not a quality gate. The reason is quit easy explained.

A build manager is usually not be able to decide if a implementation fits well to the architecture. This are tasks for an Architect. In my humble opinion, I think a better and less time consuming strategy in enterprise projects, are code reviews shortly before a sprint is closed or directly after the sprint. Then, all the code is integrated and the metric tools deliver better results on test coverage, code smells and code duplication. Pull requests stresses developers more than they increase their implementation skills.

Before you start a lot of activities in the hope as overall result you project reach a better quality, you should wait and think twice. Don't run - take a breath and think about what you really wish to make better in your project. There many aspects about quality. B. W. Boehm published in 1975 a research paper how to define quality and how it can measured. May you want to have a look on my DZone article about [software quality](https://dzone.com/articles/non-functional-requirements-quality).

If you have the idea to use pull request to secure the quality for your off shore vendor team, you might be wrong. You should select well educated developers for a higher price, which delivers better code because of their experience. There is a great book about how to work together with off shore development teams, written from [Nick Krym “Outsource It!”](https://www.amazon.com/gp/product/193778505X/ref=as_li_tl?ie=UTF8&camp=1789&creative=9325&creativeASIN=193778505X&linkCode=as2&tag=elmardott-20&linkId=c9f8933426a5dcd22c75b529cf65b57a). [2012, The Pragmatic Programmers, ISBN-13: 978-1-93778-505-5]
"What's Here" for Ruby Array
Tags: ruby, array, documentation
Published: 2022-01-03 22:03:42

---
title: "What's Here" for Ruby Array
published: true
description:
tags: ruby, array, documentation
---
One of my projects over at the Ruby documentation is creating "What's Here" sections for certain classes.

The section provides a categorized overview of the methods, giving a 1-line description for each.  So here's the [What's Here for Array](https://ruby-doc.org/core-3.1.0/Array.html#class-Array-label-What-27s+Here).
Cáritas Diocesana de Madrid recibe 

Published: 2022-01-03 21:55:02


Cáritas Diocesana de Madrid ha recibido el Premio “Noche Teleco de Madrid a la Transformación Digital” en el marco de la V Noche de las Telecomunicaciones, organizada por la Delegación en Madrid de la Asociación Española de Ingenieros de Telecomunicación, que se celebró ayer en el Auditorio Rafael del Pino en formato híbrido.

La Junta Directiva de la AEIT Madrid ha decidido otorgar este premio a Cáritas Madrid por su proyecto de lucha contra la brecha digital mediante la distribución de donaciones de equipos informáticos y accesos a redes de datos, además de facilitar la capacitación en competencias digitales a los menores de familias en situación de vulnerabilidad social.


[leer mas](https://diariomallorca.es/)
El sector funerario apuesta por la digitalización y se adentra en el ecommerce

Published: 2022-01-03 21:49:55


La digitalización se posicionaba como un objetivo importante para las empresas que han tenido que priorizar a raíz de la pandemia. Las relaciones sociales se han visto alteradas así como las laborales e, incluso, aquellas entre clientes y empresas. Los hábitos de los consumidores han cambiado y cada vez son más los que realizan sus compras a través de internet evitando el contacto con grandes multitudes de personas y aprovechando la inmediatez y la comodidad que el comercio electrónico les ofrece.

Durante los últimos tiempos, debido al riesgo de contagio, las actividades online se han convertido en parte imprescindible del día a día. Herramientas como las videollamadas, el uso de las plataformas de streaming, y también las ventas online se han visto incrementadas y han sido muchas las empresas que han tenido que acelerar sus planes de transformación digital.
[leer mas](https://diariomallorca.es/)
Advent of PBT 2021 - Day 16
Tags: challenge, testing, webdev, javascript
Published: 2021-12-16 08:13:49

---
title: Advent of PBT 2021 - Day 16
published: true
description: Advent of Property Based Testing - Day 16
tags: challenge,testing,webdev,javascript
//cover_image: https://direct_url_to_image.jpg
---

> _Advent of PBT 2021 — Learn how to use property based testing and [fast-check](https://github.com/dubzzz/fast-check) through examples_

Our algorithm today is: **reversed**.
It comes with the following documentation and prototype:
```ts
/**
 * Produce a copy of the array but reversed
 * @param data - Reversed array
 */
declare function reversed<T>(data: T[]): T[];
```

We already wrote some examples based tests for it:
```ts
it("should be able to reverse the empty array", () => {
  expect(reversed([])).toEqual([]);
});
it("should be able to reverse an array with only one item", () => {
  expect(reversed([10])).toEqual([10]);
});
it("should be able to reverse an array with multiple items", () => {
  expect(reversed([10, 5, 2, 800])).toEqual([800, 2, 5, 10]);
});
```

How would you cover it with Property Based Tests?

In order to ease your task we provide you with an already setup CodeSandbox, with examples based tests already written and a possible implementation of the algorithm: https://codesandbox.io/s/advent-of-pbt-day-16-2uutt?file=/src/index.spec.ts&previewwindow=tests

You wanna see the solution? Here is the set of properties I came with to cover today's algorithm: https://dev.to/dubzzz/advent-of-pbt-2021-day-16-solution-3a4c

---

[Back to "Advent of PBT 2021"](https://dev.to/dubzzz/advent-of-pbt-2021-13ee) to see topics covered during the other days and their solutions.

More about this serie on [@ndubien](https://twitter.com/ndubien) or with the hashtag [#AdventOfPBT](https://twitter.com/search?q=%23AdventOfPBT).