danlourenco

Code is clean if it can be understood easily – by everyone on the team. Clean code can be read and enhanced by a developer other than its original author. With understandability comes readability, changeability, extensibility and maintainability.

---

General rules

1. Follow standard conventions.
2. Keep it simple stupid. Simpler is always better. Reduce complexity as much as possible.
3. Boy scout rule. Leave the campground cleaner than you found it.
4. Always find root cause. Always look for the root cause of a problem.

Design rules

danlourenco

Summary of book "Clean Architecture" by Robert C. Martin

Uncle Bob, the well known author of Clean Code, is coming back to us with a new book called Clean Architecture which wants to take a larger view on how to create software.

Even if Clean Code is one of the major book around OOP and code design (mainly by presenting the SOLID principles), I was not totally impressed by the book.

Clean Architecture leaves me with the same feeling, even if it's pushing the development world to do better, has some good stories and present robust principles to build software.

The book is build around 34 chapters organised in chapters.

danlourenco

const withHOC  = (WrappedComponent) => {

  return class WithHoc extends React.Component {
  
    // custom methods to augment wrapped component
    
    render() {
      return <WrappedComponent {...this.props} />
    }
  }

danlourenco

I really liked @tjvantoll article Handling Failed HTTP Responses With fetch(). The one thing I found annoying with it, though, is that response.statusText always returns the generic error message associated with the error code. Most APIs, however, will generally return some kind of useful, more human friendly message in the body.

Here's a modification that will capture this message. The key is that rather than throwing an error, you just throw the response and then process it in the catch block to extract the message in the body:

fetch("/api/foo")
  .then( response => {
    if (!response.ok) { throw response }
    return response.json()  //we only get here if there is no error
 })

danlourenco

Browsers

Chrome/MS Edge

• Redux Extension
• React Extension

Terminals

• iTerm (Mac OSX)
• Solarized Dark Theme

danlourenco

Eric Elliott's "Master the JavaScript Interview" Series

A collection of links to the "Master the JavaScript Interview" series of medium stories by Eric Elliott.

Not part of the series but a good grounding.

• The Two Pillars of JavaScript - Part 1
• The Two Pillars of JavaScript - Part 2
• 10 Interview Questions Every JavaScript Developer Should Know

Master the JavaScript Interview

danlourenco

A curated list of AWS resources to prepare for the AWS Certifications

A curated list of awesome AWS resources you need to prepare for the all 5 AWS Certifications. This gist will include: open source repos, blogs & blogposts, ebooks, PDF, whitepapers, video courses, free lecture, slides, sample test and many other resources.

---

danlourenco

const myObject = {
  a: 1,
  b: 2,
  c: 3
};
const { a, ...noA } = myObject;

console.log(noA); // => { b: 2, c: 3 }

danlourenco

{
    "Version": "2012-10-17",
    "Statement": [
        {
            "Sid": "PublicReadGetObject",
            "Effect": "Allow",
            "Principal": "*",
            "Action": "s3:GetObject",
            "Resource": "arn:aws:s3:::bucket-name-here/*"
        }

danlourenco

Cypress.Commands.add('login', (overrides = {}) => {
  Cypress.log({
    name: 'loginViaAuth0',
  });

  const options = {
    method: 'POST',
    url: Cypress.env('auth_url'),
    body: {
      grant_type: 'password',