- learn blockchain concepts
- learn ethereum
- learn how to use metamask
- learn how to use hardhat (https://hardhat.org/)
- learn how to deploy and interact with a smart contract
- learn common smart contract standards like ERC20 (token), ERC721 (nft), ERC1155 (opensea)
- learn ipfs
- learn how to read blockchain explorers like https://etherscan.io/
- learn how to use web3 and etherjs
- learn solidity
"""Turtle module http://cursodepython.com.br""" | |
import turtle | |
turtle.bgcolor("black") | |
turtle = turtle.Turtle() | |
turtle.shape("turtle") | |
turtle.speed(3) | |
turtle.width(10) | |
turtle.color("blue", "yellow") | |
turtle.pencolor("red") |
Looking for the First Job
This is a very common state for people in college, people before/after a bootcamp, or people from another area.
The first job will be the hardest one to get, but it will get easier over time.
The interview will be harder than the job itself
- learn about basic database modelling, use excalidraw
- learn how to connect to a database and performe queries
- learn how to expose a CRUD API REST and/or GraphQL
- learn how to document the API using Swagger, swagger-jsdoc is the best for it
- learn how to test your API using Postman, and also automated using jest and supertest
- learn how to consume other APIs using fetch
Also check Docker Learning Path and Lambda Learning Path
You first need to undestand the concept of frontend tests.
You should not test the implementation but the behavior
You test like the end user
For instance, imagine a login screen with email and password inputs and a submit button
The test should input the email and the password, then click in the submit button.
version: '3' | |
services: | |
web: | |
image: udovicic/echo:apache-php7.1 | |
container_name: web | |
restart: always | |
volumes: | |
- "./:/var/www/html" #remeber to change this path yo tour own | |
ports: | |
- "8083:80" |
Some thoughts I've gathered over the years on what I think about GraphQL. All of this is subject to change of course, and some of it may be "hot-take"-ish, but at the end of the day, I've made decisions regarding GraphQL with my customers, users, and fellow developers in mind and with the mantra that if it ultimately doesn't make a big difference for any of those people and justify the work that it requires, it's not the best investment of time. It's more important to please your users, ship products in a timely manner, and use tools that keep processes simple and familiar.
- A majority of the world still runs on REST and probably will for a while.
- The challenges of larger companies that originally benefitted from GQL are not everyones challenges and they likely never will be.
- I don't want to require my API users to have knowledge of GQL.
- Strongly typed APIs are good, but I don't particularly enjoy the tools in the ecosystem right now to use them via GQL
- GraphQL seems to have been born out of the req
const path = require('path'); | |
const webpack = require('webpack'); | |
const WebpackNodeExternals = require('webpack-node-externals'); | |
const ReloadServerPlugin = require('reload-server-webpack-plugin'); | |
const cwd = process.cwd(); | |
module.exports = { |