Alex Ribeiro

Head of Application & Generative AI at NuageIT

[Alex Ribeiro @alexribeirodev]

@kapilansh_twt Lua 😬

[Alex Ribeiro @alexribeirodev]

@Redbeeea Eles usam a informação de dispositivos Android ou com google conectado concentrados na mesma proximidade.

[Alex Ribeiro @alexribeirodev]

@PratikSinhatwt Cloudflare tem meu coração.

[Alex Ribeiro @alexribeirodev]

Apesar do preconceito no nível enterprise com LLMs Chinesas, eu tenho conseguido uma ótima experiência.

Tenho utilizado o modelo Minimax m2.5 para alguns agentes operacionais e ele é extremamente obediente.

Qual modelo vocês tem usado para tarefas operacionais ou rotinas?

[Alex Ribeiro @alexribeirodev]

@karthikponna19 C, C#, PHP and Lua.

[Alex Ribeiro @alexribeirodev]

@piyush784066 Base debian é mais desenrolada. Caso seja desenrolado com Linux, vai de Arch sem medo.

[Alex Ribeiro @alexribeirodev]

@CodeEdison Por esse valor, Codex vai conseguir render mais se for para codificação pesada. Gemini/Antigravity tinha um contexto bem grande, mas mudou.

[Alex Ribeiro @alexribeirodev]

@vibeonX69 Zsh com Oh My Zsh ou fish

[Alex Ribeiro @alexribeirodev]

A Google não está para brincadeira! 🤯 Com a implementação agressiva de IA Generativa, como o Nano Banana Pro, a concorrência ligou o alerta máximo. 🚨 A evolução na geração de imagens com texto é insana.

Se preparem!

#IAGenerativa #Google #NanoBananaPro #Tecnologia #Inovação

[Alex Ribeiro @alexribeirodev]

@sseraphini Pensando rápido e sem profundidade aqui...
+ Dinheiro - Conhecimento = Contratar dev + IA (Lovable, Bolt, Cursor e etc)
+ Dinheiro + Conhecimento = Contratar IA boa dedicar mais tempo escrevendo as especificações
- Dinheiro - Conhecimento = Trabalha para quem sabe e aprende

[Alex Ribeiro @alexribeirodev]

@ludo_zz Tem sido a melhor opção para mim. Múltiplos projetos, múltiplos ambientes e múltiplos tipos de banco de dados. Ele me ajuda a organizar muito bem tudo isso.

[Alex Xu @alexxubyte]

Explaining 9 types of API testing. The method to download the high-resolution PDF is available at the end.

🔹 Smoke Testing
This is done after API development is complete. Simply validate if the APIs are working and nothing breaks.

🔹 Functional Testing
This creates a test plan based on the functional requirements and compares the results with the expected results.

🔹 Integration Testing
This test combines several API calls to perform end-to-end tests. The intra-service communications and data transmissions are tested.

🔹 Regression Testing
This test ensures that bug fixes or new features shouldn’t break the existing behaviors of APIs.

🔹 Load Testing
This tests applications’ performance by simulating different loads. Then we can calculate the capacity of the application.

🔹 Stress Testing
We deliberately create high loads to the APIs and test if the APIs are able to function normally.

🔹 Security Testing
This tests the APIs against all possible external threats.

🔹 UI Testing
This tests the UI interactions with the APIs to make sure the data can be displayed properly.

🔹 Fuzz Testing
This injects invalid or unexpected input data into the API and tries to crash the API. In this way, it identifies the API vulnerabilities.

Subscribe to our newsletter to download the 𝐡𝐢𝐠𝐡-𝐫𝐞𝐬𝐨𝐥𝐮𝐭𝐢𝐨𝐧 𝐜𝐡𝐞𝐚𝐭 𝐬𝐡𝐞𝐞𝐭. After signing up, find the download link on the success page: https://t.co/Zx9BH4M3Qm

[Alex Xu @alexxubyte]

IBM MQ -> RabbitMQ -> Kafka ->Pulsar, How do message queue architectures evolve?

🔹 IBM MQ
IBM MQ was launched in 1993. It was originally called MQSeries and was renamed WebSphere MQ in 2002. It was renamed to IBM MQ in 2014. IBM MQ is a very successful product widely used in the financial sector. Its revenue still reached 1 billion dollars in 2020.

🔹 RabbitMQ
RabbitMQ architecture differs from IBM MQ and is more similar to Kafka concepts. The producer publishes a message to an exchange with a specified exchange type. It can be direct, topic, or fanout. The exchange then routes the message into the queues based on different message attributes and the exchange type. The consumers pick up the message accordingly.

🔹 Kafka
In early 2011, LinkedIn open sourced Kafka, which is a distributed event streaming platform. It was named after Franz Kafka. As the name suggested, Kafka is optimized for writing. It offers a high-throughput, low-latency platform for handling real-time data feeds. It provides a unified event log to enable event streaming and is widely used in internet companies.

Kafka defines producer, broker, topic, partition, and consumer. Its simplicity and fault tolerance allow it to replace previous products like AMQP-based message queues.

🔹 Pulsar
Pulsar, developed originally by Yahoo, is an all-in-one messaging and streaming platform. Compared with Kafka, Pulsar incorporates many useful features from other products and supports a wide range of capabilities. Also, Pulsar architecture is more cloud-native, providing better support for cluster scaling and partition migration, etc.

There are two layers in Pulsar architecture: the serving layer and the persistent layer. Pulsar natively supports tiered storage, where we can leverage cheaper object storage like AWS S3 to persist messages for a longer term.

Over to you: which message queues have you used?

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

[Alex Xu @alexxubyte]

Explaining 8 Popular Network Protocols in 1 Diagram. The method to download the high-resolution PDF is available at the end.

Network protocols are standard methods of transferring data between two computers in a network.

1. HTTP (HyperText Transfer Protocol)
HTTP is a protocol for fetching resources such as HTML documents. It is the foundation of any data exchange on the Web and it is a client-server protocol.

2. HTTP/3
HTTP/3 is the next major revision of the HTTP. It runs on QUIC, a new transport protocol designed for mobile-heavy internet usage. It relies on UDP instead of TCP, which enables faster web page responsiveness. VR applications demand more bandwidth to render intricate details of a virtual scene and will likely benefit from migrating to HTTP/3 powered by QUIC.

3. HTTPS (HyperText Transfer Protocol Secure)
HTTPS extends HTTP and uses encryption for secure communications.

4. WebSocket
WebSocket is a protocol that provides full-duplex communications over TCP. Clients establish WebSockets to receive real-time updates from the back-end services. Unlike REST, which always “pulls” data, WebSocket enables data to be “pushed”. Applications, like online gaming, stock trading, and messaging apps leverage WebSocket for real-time communication.

5. TCP (Transmission Control Protocol)
TCP is is designed to send packets across the internet and ensure the successful delivery of data and messages over networks. Many application-layer protocols build on top of TCP.

6. UDP (User Datagram Protocol)
UDP sends packets directly to a target computer, without establishing a connection first. UDP is commonly used in time-sensitive communications where occasionally dropping packets is better than waiting. Voice and video traffic are often sent using this protocol.

7. SMTP (Simple Mail Transfer Protocol)
SMTP is a standard protocol to transfer electronic mail from one user to another.

8. FTP (File Transfer Protocol)
FTP is used to transfer computer files between client and server. It has separate connections for the control channel and data channel.

–
Subscribe to our newsletter to download the high-resolution PDF. After signing up, find the download link on the success page: https://t.co/keu1P0hhKI

[g1 @g1]

Luto no cinema: Morre Michael Gambon, ator de Harry Potter https://t.co/f8jnF7jGyn #g1

[Alex Ribeiro @alexribeirodev]

Can anyone invite me to https://t.co/7aU2310yPH?

cc @TextsHQ

[Alex Ribeiro @alexribeirodev]

@CapacitiesHQ @memdotai mem it

[Alex Ribeiro @alexribeirodev]

@dickiebush @memdotai mem it

[Alex Ribeiro @alexribeirodev]

@steffenBle @memdotai mem it

[Alex Ribeiro @alexribeirodev]

@erickwendel_ @memdotai mem it