Introduction

In order to truly understand props in React, we first need to be clear on what components are. A component is a reusable piece of the user interface that encapsulates structure, styling, and behavior.

Instead of repeating the same code across a project, we can build small, independent components and compose them together to form complete pages or applications.

Jsx

At its core, a component in React is simply a JavaScript function that returns JSX. JSX is a special syntax extension that looks like HTML but runs in JavaScript. It allows us to describe what the UI (User interface) should look like while keeping the full power of JavaScript inside our markup.

It looks like the following

function Greeting() {
  const styles = {
    color: "blue",
    fontSize: "24px",
    fontFamily: "Arial, sans-serif"
  };

  return (
    <div>
      <h1 style={styles}>Hello, World!</h1>
      <p className="subtitle">Welcome to React components with JSX.</p>
    </div>
  );
}

Props

Introduction

In the context of React components, props (short for properties) are the way we pass data from a parent component down to a child component.

Think of them like function parameters:

• A component receives props as an argument.

• The props define how the component behaves or what it displays.

• Props are read-only (immutable inside the child), since the child cannot change them, only use them.

Code snippet

Let’s explore the following code snippet:

function Greeting(props) {
  return <h1>Hello, {props.name}!</h1>;
}

// Using the component with different props
function App() {
  return (
    <div>
      <Greeting name="Alice" />
      <Greeting name="Bob" />
    </div>
  );
}

What’s happening up here?

• The App component is the parent, since it’s the one that render another component inside its JSX. In our previous example, the App component uses <Greeting /> inside its return statement.

• It renders Greeting twice, passing a different name each time.

• Inside Greeting, we use props.name to display the correct value.

• The result on screen:

    Hello, Alice!
    Hello, Bob!
  

  ---

  Characteristics

  Read-Only

  Props are read-only. It means they cannot be modified by the child. If you try, React will warn you.

function Greeting(props) {
  // ❌ Avoid doing this!
  // props.name = "Changed"; // Error: props are read-only
  return <h1>Hello, {props.name}!</h1>;
}

The read-only characteristic enforces the one-way data flow in React: data flows from parent → child, not the other way around.

Props are meant to be used, not changed.

Any data type

Props aren’t limited to strings. You can pass numbers, booleans, objects, arrays, and even functions.

In the following code snippet, App renders <Profile user={user}…, React bundles everything inside an object, it does not matter how many objects or functions are inside.

So, inside `Profile`, we can access:

• props.user → an object ({ name: "Alice", age: 28 })

• props.onLogout → a function

function Profile(props) {
  return (
    <div>
      <h2>{props.user.name}</h2>
      <p>Age: {props.user.age}</p>
      <button onClick={props.onLogout}>Logout</button>
    </div>
  );
}

function App() {
  const user = { name: "Alice", age: 28 };

  function handleLogout() {
    alert("Logged out!");
  }

  return <Profile user={user} onLogout={handleLogout} />;
}

Default values

If a parent component does not pass a prop, you can define a default.

function Button({ label = "Click Me" }) {
  return <button>{label}</button>;
}

function App() {
  return (
    <div>
      <Button /> {/* Uses default: "Click Me" */}
      <Button label="Submit" /> {/* Uses passed prop */}
    </div>
  );
}

Spread

In React, you don’t always need to pass props one by one. You can use the spread operator, which is …, to pass all the properties of an object as props to a component.

Take a look at the following code snippet without spread

function UserCard({ name, age }) {
  return (
    <div>
      <h3>{name}</h3>
      <p>Age: {age}</p>
    </div>
  );
}

function App() {
  const user = { name: "Alice", age: 28 };

  return <UserCard name={user.name} age={user.age} />;
}

Now, the following with spread:

function App() {
  const user = { name: "Alice", age: 28 };

  // Spreads `user` into { name: "Alice", age: 28 }
  return <UserCard {...user} />;
}

Now, UserCard automatically receives props.name and props.age without you having to type them out one by one.

Keep in mind that spreading blindly can make it harder to know which props a component is using. It’s often best for cases like “pass all user data”.

Children

Every React component automatically has access to a special prop called children. It represents the content you place between the opening and closing tags of a component.

function Card(props) {
  return <div className="card">{props.children}</div>;
}

function App() {
  return (
    <Card>
      <h1>Welcome!</h1>
      <p>This text is inside the Card component.</p>
    </Card>
  );
}

So, everything between <Card> and </Card> is passed as props.children.

Conditional

Since props are just JavaScript values, you can pass conditional expressions.

function Status({ online }) {
  return <p>{online ? "🟢 Online" : "🔴 Offline"}</p>;
}

function App() {
  return (
    <div>
      <Status online={true} />
      <Status online={false} />
    </div>
  );
}

Done

Context

By default, Codespace is using the GITHUB_TOKEN env var (the “Codespaces token”), which can’t create repos.

It’s necessary to authenticate gh with a token/account that has the right scopes, or create the repo on the web first.

Objective

In this article, let’s focus on authenticating, setting the right scopes and creating the repo.

Solution

Initiate the project

In short: we’ll check status → create repo → stage everything → commit it.

git status || git init
git add .
git commit -m "init"

git status → shows the current state of the repository (which files are changed, staged, or untracked).

git init → initializes a new Git repository in the current folder.

git add . → stages all changes (new, modified, deleted files) in the current folder for the next commit.

git commit -m "init" → creates a commit with the message "init".

Check the environment

In short: we’ll log out of the GitHub CLI, then clear the token stored in our environment.

gh auth logout -h github.com
unset GITHUB_TOKEN

• gh auth logout -h github.com → logs you out from GitHub CLI (gh) specifically for the host github.com.

• unset GITHUB_TOKEN → removes the GITHUB_TOKEN environment variable from your current shell session.

Login

In short: you log in via browser, then check if the login worked.

gh auth login -h github.com -p https -w
gh auth status

• gh auth login -h github.com -p https -w → logs you in to GitHub CLI (gh) for the host github.com, using HTTPS as the protocol (-p https), and opens a web browser (-w) to complete the authentication.

• gh auth status → shows your current GitHub CLI authentication status (which account you’re logged in with, token details, active host, etc.).

Double check login

gh auth status
gh api user

Create and push

In short: this creates a new private repo on GitHub and immediately pushes your local project there.

gh repo create alexcalaca/profile-card --private --source . -
-remote origin --push

Output

Done

Here it is:

git commit --allow-empty-message -m ""

Explanation

To create a Git commit without a message, or with an empty message, you can use the --allow-empty-message flag with the git commit command.

git commit --allow-empty-message -m ""

Breaking it down:

• git commit: This is the standard command for creating a new commit.

• --allow-empty-message: This flag explicitly tells Git to allow a commit with an empty message.

• -m "": This specifies an empty commit message. You must still include the -m flag, even if the message content is an empty string.

Done

Cleanup phase

This phase’s goal is to removes existing containers, volumes, networks and images

Stop and remove volumes

docker compose down --volumes --remove-orphans

The previous command stops and removes containers, networks, and default volumes created by docker compose up.

• --volumes: also deletes named and anonymous volumes attached to the containers.

• --remove-orphans: removes any containers from earlier Compose runs that are not in the current docker-compose.yml.

Remove any stopped containers

docker compose rm -fsv

The previous command explicitly removes any stopped containers from this project. This ensures no containers are left behind

• -f: force removal (no confirmation prompt).

• -s: stop the container if it’s running.

• -v: remove any anonymous volumes attached to these containers.

Delete unused volumes

The following command deletes all unused volumes across the whole Docker host (not just our project), so, use it cautiously.

docker volume prune -f

-f: skips the confirmation prompt.

Remember. Be careful: this can delete volumes from other projects if they’re not in use.

Delete unused networks

The following command delete all unused networks across the Docker host.

docker network prune -f

-f: skips confirmation.

Again, safe unless you have manually created custom networks you still need.

Delete dangling images

The following command deletes dangling images, which are images without a tag or not referenced by any container).

docker image prune -f

-f: skips confirmation.

Only cleans dangling images, not all unused images. For a deeper clean, you’d need docker image prune -af.

Rebuild phase

This phase forces a clean rebuild and restart.

Rebuild images

The following command rebuilds all images defined in your Compose file.

 docker compose build --no-cache

• --no-cache: ignores Docker’s layer cache, forcing every instruction in the Dockerfile(s) to run again. It guarantees you’re building fresh images without reusing cached layers.

Start the containers

The following command starts the containers in detached mode (-d = runs in the background). `-d` is optional.

docker compose up -d

Now, it’ll use the freshly rebuilt images. It’ll recreate networks and attaches containers as defined in the Compose file.

Done

Stop the service

It’s not mandatory, but before uninstalling, it's a good practice to stop any running Docker services.

sudo systemctl stop docker

Remove docker packages

It’s used to completely and forcefully remove a list of specified packages from a Debian-based Linux system like Pop!_OS. All the following packages are docker related.

In short, this command aims to leave no trace of the specified Docker packages, which is an essential step for a complete and thorough uninstallation.

sudo apt-get purge -y docker-engine docker docker.io docker-ce docker-ce-cli containerd runc

and also

sudo apt-get purge -y docker-compose-plugin

Clean up leftover files

In summary, the command is a non-interactive, forced, and recursive deletion of all major Docker-related data and configuration directories. This is an essential step for a complete uninstallation.

sudo rm -rf /var/lib/docker/ /var/lib/containerd/ /etc/docker ~/.docker/

Remove docker group

When you install Docker, it creates a docker group. This group is created for security and convenience, allowing users to run Docker commands without needing sudo every time.

In this case, since we don’t need it anymore, we’re going to delete the docker group.

 sudo groupdel docker

Remove docker repository entry

By deleting this file, you are essentially telling your system to stop looking for Docker updates from the official Docker repository. This is an important step in a complete uninstallation, as it ensures that apt-get update no longer tries to connect to a repository for a program that you no longer want on your system.

sudo rm /etc/apt/sources.list.d/docker.list

Remove dependencies

In summary, the goal is to remove old, useless downloaded package files to free up disk space, but it does not remove any installed software.

It is a maintenance command that is good to run periodically after uninstalling software or upgrading your system.

sudo apt-get autoremove -y --purge docker-ce docker-ce-cli
sudo apt-get autoclean

Verify the installation

docker --version
docker compose --version
docker

Output

Functions are one of the most important concepts in JavaScript. They allow us to organize code, avoid repetition, and make programs easier to maintain.

Introduction

What’s a Function?

A function is a block of code designed to perform a specific task. Instead of writing the same instructions multiple times, you can group them into a function and call it whenever you need.

Let’s break it down in a very simple way: a function is a piece of code that you’d like to use many times. Instead of writing that piece of code over and over again, you create a function. Then, whenever you need it, you simply call or invoke the function.

Key terms:

• Function → A block of code.

• Invoke/Call → Run the function.

Example:

function sayHello() {
  console.log("Hello, world!");
}

sayHello(); // Function call

🔹 2. Parameters and Arguments

Functions can receive input values.

• Parameters → Placeholders in the function definition.

• Arguments → Real values passed when calling the function.

Example:

function greet(name) { // "name" is the parameter
  console.log("Hello, " + name + "!");
}

greet("Alice");   // "Alice" is the argument
greet("Bob");     // "Bob" is the argument

🔹 3. Return Values

Functions can produce and return results using the keyword return.

• Without return, functions only perform actions.

• With return, they can give back a value to be reused.

Example:

function add(a, b) {
  return a + b;
}

let result = add(5, 3);
console.log(result); // 8

🔹 4. Reusability (Avoiding Repetition)

One of the main reasons for using functions is to avoid repeating code.

Without a function:

console.log("Hello, Alice!");
console.log("Hello, Bob!");
console.log("Hello, Charlie!");

With a function:

function greet(name) {
  console.log("Hello, " + name + "!");
}

greet("Alice");
greet("Bob");
greet("Charlie");

✔️ Easier to maintain, more organized.

🔹 5. Function Expressions

Functions can also be stored inside variables. This is called a function expression.

Example:

const multiply = function(x, y) {
  return x * y;
};

console.log(multiply(2, 4)); // 8

🔹 6. Arrow Functions

JavaScript provides a shorter syntax for functions, called arrow functions.

• Often used for simple one-line functions.

Example:

const square = (n) => n * n;

console.log(square(6)); // 36

🔹 7. Functions in Real Use

Functions are everywhere in JavaScript, for example, when working with arrays or handling events.

Example with arrays:

let numbers = [1, 2, 3, 4];
let doubled = numbers.map(num => num * 2);

console.log(doubled); // [2, 4, 6, 8]

Example with events:

document.querySelector("button").onclick = function() {
  alert("Button clicked!");
};

Recap of Key Terms

• Function → Block of code.

• Call/Invoke → Run the function.

• Parameters → Inputs defined in the function.

• Arguments → Real values passed when calling.

• Return → Sends a value back.

• Function Expression → Function stored in a variable.

• Arrow Function → Short syntax for writing functions.

Practice

Practice your knowledge with the following exercises:

• Function that prints your name.

• Function that doubles a number.

• Function that squares a number.

• Arrow function that checks if a number is even.

• Mini-project: Calculate rectangle area.

Flameshot

Flameshop is a powerful yet simple to use screenshot software.

Features

• Customizable appearance;

• Easy to use.

• In-app screenshot editing.

• DBus interface.

More features

Pre-installation

Check your OS (optional)

This step is just to make sure you have Pop!_OS installed.

uname -a
hostnamectl
lsb_release -a
cat /etc/os-release

Output

Update packages info

sudo apt-get update

Running sudo apt-get update is an important step before installing or upgrading packages on your system because it ensures that you have the most up-to-date information about available packages.

Without updating the package index, you might not see the latest versions of software or be able to install new packages that have been added to the repositories since the last update.

Solution

Installation

sudo apt-get install flameshot -y

You should be able to see something like the following

Double check

Let’s check if the installation was successful.

Path installation

which flameshot

Package installation

dpkg -l  grep flameshot

Binary

 which flameshot

Software’s help

flameshot --help

Run

In the terminal

flameshot

In your tray icon area, on your right side, You should be able to see something like this:

Done

Check your OS (optional)

This step is just to make sure you have Pop!_OS installed.

uname -a
hostnamectl
lsb_release -a
cat /etc/os-release

Output

Update packages info

sudo apt-get update

Running sudo apt-get update is an important step before installing or upgrading packages on your system because it ensures that you have the most up-to-date information about available packages.

Without updating the package index, you might not see the latest versions of software or be able to install new packages that have been added to the repositories since the last update.

Download the .deb file

Go to the downloads page and and choose the installer PCoIP & DCV.

Install it

sudo apt-get install ./Downloads/new_workspacesclient_focal_amd64.deb

Just make sure to locate the file.

Double check

Path installation

which workspacesclient

Package installation

dpkg -l | grep workspacesclient

Binary

which workspacesclient

Output

Run

Menu

Terminal

Done

Factory not registered: "your_factory_name" (KeyError)
lib/active_support/hash_with_indifferent_access.rb:192:in `fetch': key not found: "your_factory_name" (KeyError)

Context

This error typically happens in the Rails console when you're using FactoryBot and try to build or create a factory that hasn't been defined, loaded or registered.

Solution

Require dependencies

Check if dependencies/libraries are already loaded

defined?(FactoryBot)
defined?(Faker)

If you get `nil`, you should require them.

irb(main):001> defined?(FactoryBot)

=> nil
irb(main):003> defined?(Faker)
=> nil
irb(main):004> require 'factory_bot'
=> true
irb(main):005> require 'faker'
=> true
irb(main):006> defined?(Faker)
=> "constant"
irb(main):007> require 'factory_bot'
=> false
irb(main):008>

Output

Check the factories

Let’s check if the factories really exist

FactoryBot.factories.map(&:name)
FactoryBot.find_definitions
FactoryBot.factories.map(&:name).include?(:your_factory_name)

OUtput

• FactoryBot.factories.map(&:name)

This command lists all registered factory names in FactoryBot as symbols (e.g., :user, :order). It’s useful for checking which factories are currently available, especially when debugging missing factory errors.

if you get an empty array, it’s because nothing is loaded or there are no factories.

• FactoryBot.find_definitions

This tells FactoryBot to load all factory definitions from the default spec/factories (or test/factories) directory.
It's essential in environments like the Rails console, where factories aren’t auto-loaded like they are in test runs.

The output should be something like

["/srv/www/current/factories",
 "/srv/www/current/test/factories",
 "/srv/www/current/spec/factories"]

• FactoryBot.factories.map(&:name).include?(:your_factory_name)

This checks if a specific factory (like :your_factory_name) is already registered and available in FactoryBot.

It’s a quick way to verify the presence of a factory before trying to build or create it, avoiding KeyError exceptions.

If you get true, then, you should celebrate because your factory is loaded and registered.

Test again

irb(main):019> FactoryBot.method(:build)
=> #<Method: #<Class:FactoryBot>(FactoryBot::Syntax::Methods)#build(name, *traits_and_overrides, &block) /srv/www/current/vendor/bundle/ruby/3.3.0/gems/factory_bot-6.2.1/lib/factory_bot/strategy_syntax_method_registrar.rb:27>
irb(main):020> FactoryBot.method(:create)
=> #<Method: #<Class:FactoryBot>(FactoryBot::Syntax::Methods)#create(name, *traits_and_overrides, &block) /srv/www/current/vendor/bundle/ruby/3.3.0/gems/factory_bot-6.2.1/lib/factory_bot/strategy_syntax_method_registrar.rb:27>
irb(main):021>

Output

Both method object for a given method if it's defined in the current scope:

• Useful to inspect or call the method later

• Raises a NameError if the method is undefined.

Done

Conclusion

When facing the error Factory not registered: "your_factory_name", it’s usually because the factory hasn’t been loaded, defined, or registered properly — especially in the Rails console, where automatic loading doesn't happen like it does during tests.

By systematically checking if FactoryBot and related dependencies are loaded (defined?), ensuring your factories are found (FactoryBot.find_definitions), and confirming your specific factory is present (FactoryBot.factories.map(&:name).include?(:your_factory_name)), you can quickly isolate and resolve the issue.

Finally, verifying method availability using FactoryBot.method(:build) or method(:create) gives you full confidence that FactoryBot is ready to use.

Context

In a Ruby on Rails application, ensuring optimal database performance is crucial for delivering a responsive and efficient user experience.

Checking if a specific column has an index is a fundamental step in achieving this optimization.

Indexes

Indexes are special database objects that improve the speed of data retrieval operations, much like an index in a book helps you quickly find the page you're looking for.

In the context of Ruby on Rails, understanding how to list and manage these indexes is crucial for optimizing database performance.

Solution

Process

Basically, the goal is to retrieve all indexes for one specific table through the connection.indexes method and it iterates over the list in specific column is present there.

Rails console

Start by opening the Rails console with the following command.

rails console

Retrieve the indexes

Let's use the connection.indexes method from ActiveRecord to retrieve the indexes for the desired table.

indexes = ActiveRecord::Base.connection.indexes(:your_table)

Connection adapters

This will return an array of ActiveRecord::ConnectionAdapters::IndexDefinition objects, each representing an index on the your_table table.

Besides, this will print the name, columns, and uniqueness of each index on the users table.

Check if a Specific Column is Indexed

The any? method is used to iterate through each index and check if the columns array of the index includes the specified column name.

indexes.any? { |index| index.columns.include?('my_column_name')}

Check all columns

indexes = ActiveRecord::Base.connection.indexes(:your_table)
indexes.map(&:columns).flatten

Done

Conclusion

By following these steps, you can easily visualize how to check if a specific column has an index in a Ruby on Rails application.

Celebrate

Reach me out

• Github

• LinkedIn

• Hashnode

• Youtube

Final thoughts

Thank you for reading this article.

If you have any questions, thoughts, suggestions, or corrections, please share them with us.

We appreciate your feedback and look forward to hearing from you.

Feel free to suggest topics for future blog articles. Until next time!

Introduction

In the world of web development, databases play a critical role in storing and managing the data that powers applications. Within a database, tables organize this data into rows and columns, making it easier to retrieve and manipulate. However, as tables grow larger, finding specific pieces of information can become slow and inefficient. This is where indexes come into play.

Indexes

Indexes are special database objects that improve the speed of data retrieval operations, much like an index in a book helps you quickly find the page you're looking for.

Rails console

rails console

Connection indexes

Let's use the connection.indexes method from ActiveRecord to retrieve the indexes for the desired table.

ActiveRecord::Base.connection.indexes(:your_table)

Connection adapters

This will return an array of ActiveRecord::ConnectionAdapters::IndexDefinition objects, each representing an index on the your_table table.

Besides, this will print the name, columns, and uniqueness of each index on the users table.

Done

Conclusion

By following these steps, you can easily visualize how to list all indexes of a specific table in a Rails application.

Celebrate

Reach me out

• Github

• LinkedIn

• Hashnode

• Youtube

Final thoughts

Thank you for reading this article.

If you have any questions, thoughts, suggestions, or corrections, please share them with us.

We appreciate your feedback and look forward to hearing from you.

Feel free to suggest topics for future blog articles. Until next time!

On May 28th, 2024, we reached 10000 views on my blog, with 232 published articles so far.

Other milestones include:

• 9000 views on May 17th, 2024;

• 5000 views on November 05th, 2023;

• 4000 views on September 06th, 2023;

• 3000 views on June 01st, 2023;

• 2000 views on April 26th, 2023;

• 1000 views on December 06th, 2022.

Thank you all for the support!

It might be simple, but I believe it's worth celebrating.

Life is worth living!

Let's become friends

• Github

• LinkedIn

• Hashnode

• Youtube

Participe da 34ª edição do GURU-CE!

📅 Data: 01/06
🕣 Horário: 8:30
📍 Local: Internacional Trade Center, Rua Ary Barroso, 70, Torre 2, Auditório 02, Andar 62 (G2)

Os ingressos estarão disponíveis a partir das 18h de hoje!
Garanta o seu no link: https://bit.ly/GURUCE34

Descrição da Vaga:

Buscamos um Analista de Desenvolvimento Web Pleno especializado em Ruby on Rails para integrar nossa equipe. O profissional será responsável por desenvolver, manter e otimizar aplicações web de alto desempenho, colaborando com nossa equipe multifuncional para entregar soluções inovadoras.
Aplicar à vaga

Habilidades Técnicas Requeridas:

• Experiência mínima de 4 anos de experiência com desenvolvimento web.

• Experiência mínima de 2 anos com desenvolvimento em Ruby on Rails.

• Familiaridade com bancos de dados relacionais, como PostgreSQL ou Oracle.

• Capacidade de escrever consultas SQL otimizadas e entender problemas de performance.

• Experiência na escrita e manutenção de testes unitários e de integração utilizando RSpec, Capybara ou ferramentas similares.

• Domínio de ferramentas de controle de versão, especialmente Git.

• Habilidade em desenvolver e consumir APIs RESTful e/ou GraphQL.

• Familiaridade com padrões de projeto, princípios SOLID e convenções do Ruby on Rails.

• Experiência em trabalho com metodologias ágeis, como Scrum ou Kanban. Aplicar à vaga

Diferencial

• Familiaridade com sistemas de cache como Redis.

• Conhecimento em WebSockets ou ActionCable.

• Noções de TDD (Test Driven Development) ou BDD (Behavior Driven Development).

• Conhecimento em tecnologias front-end, como HTML5, CSS3 e JavaScript.

• Familiaridade com frameworks e bibliotecas como Bootstrap, jQuery, React ou Vue.js

• Conhecimento em plataformas de CI/CD.
  Aplicar à vaga

Qualificações:

• Graduação em Ciência da Computação, Engenharia da Computação, Sistemas de Informação ou áreas correlatas.
  Aplicar à vaga

Benefícios:

• Equipamento: Notebook, Teclado, Mouse.

• Auxílio Home Office: R$150,00 (200h/Mensal)

• Plano de Saúde: Unimed (Goiânia) / Bradesco (Demais Cidades) em Acomodação Enfermaria. É possível fazer a inclusão de dependentes (cônjuge e filhos), sendo o valor da mensalidade pago integralmente pelo funcionário, com desconto em folha de pagamento, consulta de valores na ocasião da admissão.

• Benefício Social Familiar (Instituído pela CCT)

• Vale Cultura – R$ 50,00 (opcional, conforme Lei 12.761/2012)

• Vale Alimentação/Refeição (Sodexo) – R$1.001,00 com dedução de 10% (R$ 100,10) na folha de pagamento *instituído pela CCT.

• Seguro de Vida (PASI)

• DAY-OFF (folga) justificada ao trabalho no dia do seu aniversário. A data é intransferível, não podendo ser compensada com outros dias.

• Programa de saúde e bem-estar ↓

• Gympass Core (Wellhub) – Funciona por meio do aplicativo onde é possível frequentar academias e estúdios com diversas modalidades esportivas, por um preço mais em conta do que a mensalidade comum.

• Conexa Saúde – Direito a 1 consulta de telemedicina de pronto-atendimento por mês.Não cumulativo. Psicologia Viva – Direito a 1 consulta de telepsicologia por mês pelo.Não cumulativo.
  Aplicar à vaga

Detalhes

Agenda para o 1º Encontro Trem on Rails - 08/06

Olá Pessoal do Trem on Rails!

Estamos animados para compartilhar a agenda do nosso próximo encontro, que acontecerá no dia 08 de junho. Estejam prontos para uma sessão informativa e envolvente, repleta de aprendizado e colaboração. - by ChatGPT (me recusei a não usar isso! rs

Detalhes do Evento:
Data: 08 de junho de 2024 - Sabado
Horário: Das 10:00 às 12:00
Local: Alloyal - Rua Domingos Vieira, 120, 4ºandar, Santa Efigênia

Agenda:

Introduções (10:00 - 10:15)

• Organização e margem para quem se atrasou mesmo.

Apresentação (10:15 - 11:00)
Reduzindo custos de operação com rearquitetura e otimizações por Gabriel Sobrinho
Como ajudei um cliente a economizar milhões em infraestrutura por meio de rearquitetura, refatoração e escalabilidade, além da otimização na troca de serviços utilizados.

Discussão Aberta e Networking (11:00 - 11:45)

• Uma oportunidade para networking informal e tomar uma cerveja.

Palestrante:
Gabriel é o CEO da Code1, com vasta experiência como desenvolvedor sênior. Seu foco está em transformar tecnologia em resultados de negócios tangíveis, destacando-se pela habilidade de liderar equipes e implementar soluções inovadoras.

Observações:

• Um leve lanche e bebidas serão fornecidos.

• Sinta-se à vontade para convidar outros programadores Ruby interessados para se juntarem a nós!

• Por favor, confirme sua presença até 07/06 para que possamos fazer os preparativos necessários.

Confirmar inscrição

Stripe and Shopify both use Ruby. Stripe has described itself as a Ruby monolith, and Shopify CEO Tobi Lutke contributed to Ruby in open-source before founding the firm.

Using Ruby in their stacks, both fintechs handled a lot of volume. Stripe processed over 303m transactions from the Friday to Monday, giving over 31k businesses their best ever day using Stripe. Shopify meanwhile processed over 5 terrabytes of data per minute on Friday. This is all the more impressive given one of the most common slights against the language is that it doesn't scale, and Lutke's response was notably sassy on that topic.

So should you learn Ruby if you want a job at either of these fintechs or just fintech in general? Not necessarily. A developer from Stripe says, "knowing Ruby won't help you get a job here one bit," and that the only real benefit you'd get from learning it comes after you're hired.

The developer also notes that "half of Stripe uses Java and Go." Java at least is a far better option for employment prospects, given its stalwart status in the top 4 of the TIOBE index. Go isn't quite as popular, but still ranks higher than Ruby (13th compared to 19th) and is used at major tech firms like Uber and Netflix.

Ruby may not be particularly fun to code in, either. One engineer on Hacker News said they "got burnt out on Rails after the third app in a row that I was responsible for upgrading." One Amazon engineer said they used to code in Ruby, but were lucky to have stopped and moved on.

Stripe, however, doesn't use the popular Ruby on Rails framework, opting to build its own, which some employees have called "relaxing" and "delightful" to work with.

Article written by Alex McMurray at https://www.efinancialcareers.com/news/2023/12/ruby-jobs-fintech

Thank you for your support!

On May 17th, 2024, we reached 9000 views on my blog, with 225 published articles so far.

Other milestones include:

• 5000 views on November 05th, 2023;

• 4000 views on September 06th, 2023;

• 3000 views on June 01st, 2023;

• 2000 views on April 26th, 2023;

• 1000 views on December 06th, 2022.

It might be simple, but I believe it's worth celebrating.

Life is worth living!

Let's become friends

• Github

• LinkedIn

• Hashnode

• Youtube

Job description

Estamos buscando um Desenvolvedor Backend com conhecimentos em Ruby on Rails para um dos nossos clientes no Brasil.

Nesta posição, você será fundamental no desenvolvimento e manutenção de sistemas robustos e escaláveis, utilizando tecnologias como Ruby on Rails, Javascript, PostgreSQL, Elasticsearch e implementando boas práticas de arquitetura de software. Clique aqui para aplicar.

Responsabilidades:

• Desenvolver e manter aplicativos backend escaláveis e de alto desempenho

• utilizando Ruby on Rails.

• Projetar, implementar e otimizar APIs RESTful para suportar requisitos de frontend e integrações com outras aplicações.

• Trabalhar com bancos de dados PostgreSQL, incluindo otimização de consultas e modelagem de dados.

• Implementar e manter funcionalidades de busca utilizando Elasticsearch.

• Colaborar com equipes de frontend e UX/UI para projetar e implementar soluções eficazes.

• Contribuir ativamente para a arquitetura de software, oferecendo insights e soluções técnicas inovadoras.

• Implementar práticas de deploy automatizado e integração contínua (CI/CD).

• Manter a qualidade do código através de testes unitários e integração. Clique aqui para aplicar.

Requisitos:

• Experiência sólida em desenvolvimento backend, preferencialmente com Ruby on Rails.

• Proficiência em Javascript para desenvolvimento backend.

• Experiência com bancos de dados PostgreSQL e otimização de consultas.

• Conhecimento prático em Elasticsearch ou tecnologias similares.

• Experiência em design e desenvolvimento de APIs RESTful.

• Familiaridade com práticas de deploy automatizado e integração contínua.

• Sólidos conhecimentos em arquitetura de software, incluindo design de sistemas escaláveis e eficientes.

• Excelentes habilidades de comunicação e capacidade de trabalhar em equipe.

• Capacidade comprovada de oferecer insights técnicos e soluções arquiteturais inovadoras.

• Graduação em Ciência da Computação, Engenharia de Software ou área relacionada (desejável). Clique aqui para aplicar.

Importante:

Esta posição é em tempo integral, sob modalidade de contrato. Tem duração de 12 meses. O processo de seleção pode consistir em até 3 etapas: video-entrevista inicial com a Workana (Hireflix), prova tecnica (Tech assessment) e entrevista técnica e fit cultutal.

Se você estiver interessado(a) nesta posição e acredita que é o(a) indicado(a), aguardamos sua inscrição. Em caso de seleção para continuar, alguém da equipe de Talentos da Workana entrará em contato com você :)

Clique aqui para aplicar.

AWS CLI

AWS CLI (Amazon Web Services Command Line Interface) is a unified tool provided by Amazon for managing AWS services from the command line.

It allows users to interact with various AWS services and resources directly through text-based commands, making it easier to automate tasks, script actions, and integrate AWS services into workflows.

Configure the AWS SSO

aws configure sso

AWS SSO is a service provided by Amazon Web Services that makes it easy to centrally manage access to multiple AWS accounts and business applications and to provide users with single sign-on access to them.

Provide a session name

Set the SSO start URL

The Single Sign-On (SSO) start URL is a specific URL provided by AWS Single Sign-On that directs users to the SSO login page or the SSO portal where they can sign in and access their assigned AWS accounts and applications.

This URL is unique to your AWS account and is generated by AWS SSO.

Choose a region

Scope

Authorize device

A web page is going to open.

In the terminal

In the browser

Allow boto-core-client-dev

Botocore is the low-level library that powers the AWS CLI (Command Line Interface) and provides the foundation for the AWS SDKs (Software Development Kits) for Python.

It's responsible for handling the underlying communication with AWS services, such as sending requests and receiving responses.

Set default client region

After the approval of botocore-client-dev

Come back to the terminal and set the default client region

Set CLI default output format

Check

Visualize your profile

As soon as you hit enter after the last part, you'll see your profile.

Test

aws sts get-caller-identity --profile your_profile_name

Done

Conclusion

By following these steps, you can easily set up your AWS command line interface.

Celebrate

Reach me out

• Github

• LinkedIn

• Hashnode

• Youtube

Final thoughts

Thank you for reading this article.

If you have any questions, thoughts, suggestions, or corrections, please share them with us.

We appreciate your feedback and look forward to hearing from you.

Feel free to suggest topics for future blog articles. Until next time!

Only available for Latin America

What is it like to work at Nearsure?

A remote team never felt so close 🌐 Join our LATAM team and stay connected while working remotely. We value our team members and candidates interested in our vacancies. Enjoy fun activities like coffee breaks, tech talks, and games with our developers and management teams during your stay with us.

Who needs micromanagement? 🍃For us, communication is key, so we focus on working autonomously, with honesty, and respecting diversity. Micromanagement is not part of our corporate values.

Worklife Balance ⚖️Your well-being is our priority with our People Care team, available from day one to offer support and help with anything from needing someone to talk to, requesting time off or a holiday, or using any of our offered benefits.

Additionally, our Accounts Management team ensures a smooth and effective stay with our clients, fostering a harmonious relationship with both the client and the project. Apply now.

Here you’ll get:

• USD 💲 Salary compensation.

• 100% remote work 🏢 but if you feel like connecting with people you can visit coworking spaces all over LATAM allowing you to expand your professional network.

• Paid time off according to your country’s law without affecting your monthly salary to ensure that you have plenty of time to rest and recharge.

• Your country’s national holidays 🌴 allow you to celebrate important events and traditions with your loved ones.

• Sick or medical leave 😷 when needed so that you can take a day off to take care of your health, and have wellbeing without worrying about work.

• Refundable annual credit 💸 for you to spend on your favorite perks.

• Teambuilding activities 🤜🤛 such as coffee breaks, tech talks, and after-work gatherings with your Nearsure colleagues, to feel close to our community.

• A day off during your birthday week 🥳🎂 to enjoy with your family and friends, ensuring that you have a chance to make memories on your special day. Apply now

About the project:

As a Senior Ruby on Rails Developer, you will work collaboratively across Engineering, Product, Operations, and Marketing to architect, build, and enhance consumer applications, APIs, internal administration tools, and more. Apply now

You will be able to:

• Participate in initiatives around new libraries and technologies to improve and scale capabilities.

• Architect and build out new services using technology best suited for the job.

• Work collaboratively to develop and enhance the backend system, including cleaning and refactoring existing code.

• Rewrite legacy code and build new services to handle increasing traffic as continues to grow.

• Maintain and contribute to existing test suites to ensure that applications are reliable and work as intended.

• Utilize advanced PostgreSQL to meet the high load on the database.

• Contribute to compliance-related initiatives including state regulations and SOC audits. Apply now

What will help you succeed in this role:

• Bachelor's Degree in Computer Science, Engineering, or a related field.

• 8+ Years of experience working with software development.

• 5+ Years of experience working with Ruby on Rails.

• 1+ Years of experience working with Elixir.

• 1+ Years of experience working with Python.

• 1+ Years of experience working with Node.

• 1+ Years of experience working with APIs.

• 1+ Years of experience working with SQL.

• 1+ Years of experience working with JavaScript.

• Advanced English Level is required for this role as you will work with US clients. Effective communication in English is essential to deliver the best solutions to our clients and expand your horizons. Apply now

Here's what you can expect from our hiring process:

• We'd love to discuss your experience in an interview with our recruiters.

• If all goes well, we'll arrange a technical interview with our top developers to evaluate your skills.

• If you advance to the next stage, you'll have a chance to meet our client and potentially become a part of our amazing team! Apply now

Would you like to work alongside top Latin American talent?

Work remotely from Latin America for US clients with Nearsure, a staff augmentation company that values people and culture. Gain cross-cultural expertise and improve your English skills with daily communication in English.

We're excited to have you on board and can't wait to learn more about you.

Apply now