Didier Murillo

Statistician. R developer 🇨🇴-🇵🇷-🇺🇸. All models are wrong, but some are useful. George E. P. Box

[CNBC @CNBC]

Can ChatGPT find ‘hidden gems’ for trips in Europe? Yes, if you use these prompts https://t.co/Ay9oT9Tr8T

[𝗰𝘆𝗰𝗹𝗼𝗽 @nobrainflip]

The biggest bull run in crypto history is near, and u need to be ready.

Many will hate me for sharing this for FREE, as these secrets will sort winners from losers.

🧵: 7 years in crypto in one ultimate trading guide (will delete it soon) 👇

[Rubén Villahermosa @RubenVillaC]

🚨 #BITCOIN

Continúa el desarrollo del potencial esquema distributivo.

Acaba de alcanzar el VAL del perfil de toda la estructura, podría encontrar ahí cierta reacción por parte de los compradores.

El mapa de ruta sigue siendo el mismo 👇

https://t.co/qWhgKYn2SK

[Miles Deutscher @milesdeutscher]

Cosmos is home to some of the most lucrative airdrops in the space.

People made thousands from $TIA, $INJ, $OSMO, $KUJI etc.

But 2024 is shaping up to be the biggest airdrop year yet.

🧵: Your ULTIMATE guide to receiving Cosmos airdrops.👇

[Mac 🐺 @MacnBTC]

This is how you find #crypto winners such as:

$MATIC +45,000%,
$SOL +50,000%,
$TIA +700%,
$ORDI +2100%

How I made millions by keeping track of new altcoins and narratives 👇🏼

[Dr Milan Milanović @milan_milanovic]

𝗕𝗲𝘀𝘁 𝗣𝗿𝗮𝗰𝘁𝗶𝗰𝗲𝘀 𝗶𝗻 𝗔𝗣𝗜 𝗗𝗲𝘀𝗶𝗴𝗻

A well-defined API should be easy to work with, concise, and hard to misuse.

Here are some general recommendations:

𝟭. 𝗨𝘀𝗲 𝗻𝗼𝘂𝗻𝘀 𝗶𝗻𝘀𝘁𝗲𝗮𝗱 𝗼𝗳 𝘃𝗲𝗿𝗯𝘀

Verbs should not be used in endpoint paths. Instead, the pathname should contain the nouns that identify the object to which the endpoint we are accessing or altering belongs.

E.g., instead of using /𝚐𝚎𝚝𝙰𝚕𝚕𝙲𝚕𝚒𝚎𝚗𝚝𝚜 to fetch all clients, use /𝚌𝚕𝚒𝚎𝚗𝚝𝚜.

𝟮. 𝗨𝘀𝗲 𝗽𝗹𝘂𝗿𝗮𝗹 𝗿𝗲𝘀𝗼𝘂𝗿𝗰𝗲 𝗻𝗼𝘂𝗻𝘀

Use the plural form for resource nouns because this fits all types of endpoints.

E.g., instead of using /𝚎𝚖𝚙𝚕𝚘𝚢𝚎𝚎/:𝚒𝚍/, use /𝚎𝚖𝚙𝚕𝚘𝚢𝚎𝚎𝚜/:𝚒𝚍/

𝟯. 𝗕𝗲 𝗰𝗼𝗻𝘀𝗶𝘀𝘁𝗲𝗻𝘁

When we say to be consistent, this means to be predictable. When we have one endpoint defined, others should behave similarly. So, use the same case for resources, and the same auth methods for all endpoints, headers, status codes, etc.

𝟰. 𝗞𝗲𝗲𝗽 𝗶𝘁 𝘀𝗶𝗺𝗽𝗹𝗲

We should make naming all endpoints resource-oriented, as they are. If we want to define an API for users, we would describe it as:

/𝚞𝚜𝚎𝚛𝚜
/𝚞𝚜𝚎𝚛𝚜/𝟷𝟸𝟺

So, the first API gets all users, and the second one gets a specific user.

𝟱. 𝗨𝘀𝗲 𝗽𝗿𝗼𝗽𝗲𝗿 𝘀𝘁𝗮𝘁𝘂𝘀 𝗰𝗼𝗱𝗲𝘀

This one is super important. There are many HTTP status codes, but we usually use just some. Don't use too many, but use the same status codes for the same outcomes across the API, e.g.,

- 200 for general sucess
- 201 for succesfull creation
- 400 for bad requests
- 401 for unauthorized requests
- 403 for missing permissions
- 404 for missing resources
- 5xx for internal errors

𝟲. 𝗗𝗼𝗻'𝘁 𝗿𝗲𝘁𝘂𝗿𝗻 𝗽𝗹𝗮𝗶𝗻 𝘁𝗲𝘅𝘁

REST APIs should accept JSON for request payload and respond with JSON because it is a standard for transferring data. Yet, more is needed to return a body with JSON-formatted string; we need to specify a Content-Type header to be application/json.

𝟳. 𝗗𝗼 𝗽𝗿𝗼𝗽𝗲𝗿 𝗲𝗿𝗿𝗼𝗿 𝗵𝗮𝗻𝗱𝗹𝗶𝗻𝗴

Eliminate confusion when an error occurs, so we must handle errors properly and return a response code that indicates what happened (from 400 to 5xx errors).

𝟴. 𝗛𝗮𝘃𝗲 𝗴𝗼𝗼𝗱 𝘀𝗲𝗰𝘂𝗿𝗶𝘁𝘆 𝗽𝗿𝗮𝗰𝘁𝗶𝗰𝗲𝘀

Protect all communication between a client and a server. It means that we need to use SSL/TLS all the time, with no exceptions. Also, allow auth via API keys, which should be passed using a custom HTTP header with an expiration day.

𝟵. 𝗨𝘀𝗲 𝗽𝗮𝗴𝗶𝗻𝗮𝘁𝗶𝗼𝗻

Use pagination if our API needs to return many data, as this will make our API future-proof. Use page and page_size is recommended here.

E.g., /𝚙𝚛𝚘𝚍𝚞𝚌𝚝𝚜?𝚙𝚊𝚐𝚎=𝟷0&𝚙𝚊𝚐𝚎_𝚜𝚒𝚣𝚎=𝟸0

𝟭𝟬. 𝗩𝗲𝗿𝘀𝗶𝗼𝗻𝗶𝗻𝗴

It is important to version APIs from the first version, as our APIs could have different users.

#api

[Brennan Schlagbaum, CPA @Budgetdog_]

When I paid off my mortgage my credit dropped by 115 points.

Today, I finally hit 800 again.

Here's everything I've learned about maximizing credit in my 10 year career:

[Ashish Pratap Singh @ashishps_1]

Two months ago, I created a System Design repo on Github, and I'm excited to share that it recently reached over 3000 stars.

Thanks to everyone who has starred or forked the repository!

The repository contains a collection of resources to study:
- Around 40 System Design concepts
- Around 50 System Design problems categorized by difficulty level

My goal with this repo is to curate the best resources to learn System Design and prepare for interviews.

If you find it valuable, consider giving it a star.

Check it out here: https://t.co/pkVpi6LxSV

[BrutalBTC @BrutalBTC]

Going to start $1K to $100K Challange from 1st January 2024.
Let's achieve 2024 goals together 🔥

[RektProof. @RektProof]

#PriceAction

The Standard Setup

Simple setup that you can easily use in any market. Takes the emphasis of using Ranges, Supply/Demand alongside what a three tap is

Small write up to cover:

- How to format ranges
- Demand/Supply
- Three tap importance

Lets get into it

[Dr Milan Milanović @milan_milanovic]

𝗙𝗥𝗘𝗘 𝗘-𝗕𝗢𝗢𝗞: 𝗦𝗼𝗳𝘁𝘄𝗮𝗿𝗲 𝗘𝗻𝗴𝗶𝗻𝗲𝗲𝗿𝗶𝗻𝗴 𝗮𝘁 𝗚𝗼𝗼𝗴𝗹𝗲

The Software Engineering at Google book is not about programming, per se, but about the engineering practices utilized at Google to make their codebase sustainable and healthy.

What you can learn from this book:

𝟭. 𝗪𝗵𝗮𝘁 𝗶𝘀 𝘁𝗵𝗲 𝗱𝗶𝗳𝗳𝗲𝗿𝗲𝗻𝗰𝗲 𝗯𝗲𝘁𝘄𝗲𝗲𝗻 𝗦𝗼𝗳𝘁𝘄𝗮𝗿𝗲 𝗘𝗻𝗴𝗶𝗻𝗲𝗲𝗿𝗶𝗻𝗴 𝗮𝗻𝗱 𝗣𝗿𝗼𝗴𝗿𝗮𝗺𝗺𝗶𝗻𝗴

Programming is about writing code. You take a task and write code to solve it. Software engineering is when you take that piece of code and consider how this task will grow, how you can understand this code in the future, what happens if the business becomes more extensive, how it scales, etc.

𝟮. 𝗕𝗲𝘆𝗼𝗻𝗰𝗲 𝗿𝘂𝗹𝗲 𝗮𝗻𝗱 𝗛𝘆𝗿𝘂𝗺'𝘀 𝗹𝗮𝘄

Hyrum's Law says that with a sufficient number of users of an API,
it does not matter what you promise in the contract: all observable behaviors of your system will be depended on by somebody.

The Beyonce rule says that if Joe liked that bug, he should put a test on it. When you fix the bug, his test breaks, and you say, "Oh shit, gotta fix Joe's code too."

𝟯. 𝗦𝗵𝗶𝗳𝘁 𝗹𝗲𝗳𝘁

The earlier you find a mistake, the easier it is to fix:

✅ Run static analysis in your editor.
✅ Write fast unit tests.
✅ Write integration tests; they can catch edge cases.
✅ Code review is a great way to share knowledge and learn from others.
✅ QA takes a few hours or days to ensure everything works together as expected.

𝟰. 𝗔𝘂𝘁𝗼𝗺𝗮𝘁𝗲 𝗰𝗼𝗺𝗺𝗼𝗻 𝘁𝗮𝘀𝗸𝘀

When your team grows, it is similar to scaling a software system. So we need to automate Code formatters, linters, codemods, continuous integration pipelines, and anything you can use to take work off people's plates.

𝟱. 𝗦𝘁𝘂𝗯𝘀 𝗮𝗻𝗱 𝗺𝗼𝗰𝗸𝘀 𝗺𝗮𝗸𝗲 𝗯𝗮𝗱 𝘁𝗲𝘀𝘁𝘀

Your tests are only as good as your mocks. They hide the actual behavior of your system, drift away from reality, and take much effort to maintain. Google recommends using fakes instead.

𝟲. 𝗦𝗺𝗮𝗹𝗹 𝗳𝗿𝗲𝗾𝘂𝗲𝗻𝘁 𝗿𝗲𝗹𝗲𝗮𝘀𝗲𝘀

A minor release is easier to manage. A minor release is more accessible to revert. A minor release is easier to understand.

𝟳. 𝗨𝗽𝗴𝗿𝗮𝗱𝗲 𝗱𝗲𝗽𝗲𝗻𝗱𝗲𝗻𝗰𝗶𝗲𝘀 𝗲𝗮𝗿𝗹𝘆, 𝗳𝗮𝘀𝘁, 𝗮𝗻𝗱 𝗼𝗳𝘁𝗲𝗻

It's the same deal as releases. The smaller the change, the easier to manage. Upgrading from 4.5.8 to 4.5.9 is no big deal. Going from 4.5.8 to 4.8.0 might require a few changes. You can run around and update.

Read more in the book (find the link in the comments).

#softwareengineering #programming #learning #book #programming

[Diego | Revisiones de productos @diego_ia85]

Amazon me paga más de 4.000 euros al mes

Y, sin embargo, NO trabajo para Amazon

Simplemente utilizo 2 sitios de IA muy potentes

Te mostraré cómo puedes hacer lo mismo:

🧵THREAD🧵

[Michael Pyrcz🌻 @GeostatsGuy]

When I taught principal component analysis (#PCA) for #MachineLearning-based #dimensionality reduction a bunch of students asked, 'What do the component loadings look like?'.

So, I coded up an interactive #Python @matplotlib #dashboard! Vary the strength of the correlation and watch the loadings & variance explained change! Super cool!

On #GitHub @ https://t.co/8kuicemoFO ∀. #DataScience

[CNBC @CNBC]

5 things to know before the stock market opens Monday https://t.co/nhg7poSFoK

[Astrojoc @astrojoc]

Mejora tu pronunciación en inglés con este ejercicio 🗣️

1) ve el video y lee los subtítulos mentalmente 💭
2) velo de nuevo y ahora lee en voz alta, imitando lo más que puedas 🧐
3) velo por tercera vez pero sin audio. Imagina que tú eres el narrador. Lee y exagera tu pronunciación 🎤
4) también puedes grabarte y comparar con el audio original

[Jan Mraz @janm_uiux]

These are essential aspects of achieving a clean and smooth UI design! 🦄🖥️📱

[Alex Xu @alexxubyte]

My recommended materials for cracking your next technical interview:

Coding
- Leetcode
- Cracking the coding interview book
- Neetcode

System Design Interview
- System Design Interview book 1, 2 by Alex Xu
- Grokking the system design by Design Guru
- Design Data-intensive Application book

Behavioral interview
- Tech Interview Handbook (Github repo)
- A Life Engineered (YT)
- STAR method (general method)

OOD Interview
- Interviewready
- OOD by educative
- Head First Design Patterns Book

Mock interviews
- Interviewingio
- Pramp
- Meetapro

Apply for Jobs
- Linkedin
- Monster
- Indeed

Over to you: What is your favorite interview prep material?

–
Subscribe to our weekly newsletter to get a Free System Design PDF (158 pages): https://t.co/uc5M7Cdq84

[Santiago @svpino]

AI will not replace you. A person using AI will.