Leonardo Fachini Martins

What countries have an 8-4 hour working time overlap with the US and a huge pool of Fullstack Engineers? 👇👇👇 🇧🇷 Brazil: 180,000 software engineers -> EST: 8 hours overlap -> PST: 5 hours overlap 🇦🇷 Argentina: 48,000 software engineers -> EST: 7 hours overlap -> PST: 4 hours overlap 🇲🇽 Mexico: 40,000 software engineers -> EST: 8 hours overlap -> PST: 6 hours overlap 🇨🇴 Colombia: 32,000 software engineers -> EST: 8 hours overlap -> PST: 6 hours overlap 🇨🇱 Chile: 18,000 software engineers -> EST: 7 hours overlap -> PST: 4 hours overlap ---------------------------------------------------------------------------- 💬 Drop a comment and I’ll shoot you a report on US startups hiring full-stack devs—where, how, and the $$$! ---------------------------------------------------------------------------- P.S. If you want to learn more about how YC, A16z, and other startups are climbing to the top, consider following me.

5

2 comentários

Drawing insights from my conversation with Thiago Bomfim, an experienced software engineer who made the leap from Brazil to Portugal, here are the 10 most crucial tips for developers considering a move to Portugal. Read more 👉 https://lttr.ai/ASUEe #RichCulturalHeritage #ExperiencedSoftwareEngineer #InternationalCareer #LifeChangingDecision #AttractiveDestination #DrawingInsights

5

Test Driven Development & Developer Advocacy - Interview With Guilherme Ferreira You're not a real developer unless you do TDD. Gui Ferreira is a TDD expert -- but no, not even he would tell you this. In our chat together, we covered a lot of ground. It was great to sit down with a fellow Dometrain course author to go over: - His career journey - Developer advocacy - Test-driven development - And MUCH more! Huge thanks to Gui for the talk, and I'd love to do more in the future! 👇Check the comments for the video link!👇

39

3 comentários

Eduardo Sanches Bocato is the man 🙇 When I watch all of these talks about iOS apps at scale, everything makes so much sense 💡 But for the past couple of days I was thinking to myself, it would be great if there was some project template which would showcase two main concepts from there: 1. “Interface” modules 📦 2. Navigation module for transparent navigation between feature modules 📱 Today, Eduardo pointed me that Bruno has covered both of these concepts in his navigation library which also has a demo application: https://lnkd.in/dwgtsjiC 🚀 This helped me so much in understanding how these concepts work on a practical example 🤘

87

4 comentários

🚀 Exciting News for New Developers! 🚀 I'm very happy to share my new GitHub repository: https://lnkd.in/dMiwj-t2 This project is designed to help new developers understand data algorithms through a functional programming approach using Elixir. 🌟 To kick things off, I've implemented the classic Bubble Sort algorithm. This is a great starting point for anyone looking to grasp the fundamentals of sorting algorithms while learning Elixir's functional style. Feel free to check it out, contribute, and let me know your thoughts! Happy coding! 💻✨ #Elixir #DataStructures #Algorithms #OpenSource #Programming

43

1 comentário

Is Node.js still the go-to choice for developers, or is it losing its appeal? This question has sparked quite a discussion lately. I came across an insightful article that really breaks down the current landscape of Node.js and its popularity. It highlights how shifting trends and the emergence of alternative frameworks influence its standing in the developer community. Reflecting on my own experiences, I remember when Node.js was the hot topic in developer circles, with everyone eager to explore its potential. However, as new technologies pop up, it's crucial to stay informed and adaptable. This article tackles the very idea that sometimes, what is widely popular might not be the best fit for every project. The key takeaway here is the importance of evaluating tools based on the specific needs of your project, rather than following trends blindly. Keeping an open mind to alternatives can lead to more effective solutions tailored to business goals. What’s your take on the current standing of Node.js? Let's discuss! https://lnkd.in/gnZCY6Au

1

🚀 My First Node.js Script: Hello World! 🚀 When I first started exploring Node.js, I wanted to see how it works, so I decided to create the classic "Hello World" script. It was a simple start, but it helped me understand how JavaScript runs on the server side. Here’s how I did it: 1. Installing Node.js I downloaded Node.js from nodejs.org and got it set up on my system. Creating the script I opened my code editor and created a file named app.js. I added this line of code: console.log('Hello, World!'); 2. Running it in the terminal In the terminal, I navigated to the folder where I saved app.js and ran: bash node app.js And there it was – Hello, World! printed in my terminal! 🎉 Even though it’s a simple script, seeing it work gave me a sense of how powerful Node.js is. It’s fast, non-blocking, and ideal for building scalable applications. This small experiment marked the beginning of my journey into server-side JavaScript, and I’m excited to dive deeper into it. If you're just starting, this is a great way to get your feet wet. Let me know if you’ve tried it or if you have any tips for working with Node.js! 😊 #Nodejs #WebDevelopment #JavaScript #Coding #HelloWorld #LearningJourney

11

3 comentários

🚀 New Blog Post Alert! 🚀 I'm excited to announce the first part of my latest blog series: "Building a Finance Web Application with React, TypeScript, Styled-Components, and REST API (Part 1)". In this article, I dive into: - Setting up the project with React and TypeScript - Styling the application with Styled-Components - Integrating a REST API for real-time financial data Whether you're an experienced developer or just getting started, this series will guide you through building a robust finance web application step-by-step. Check it out and let me know your thoughts! 💬 👉 Link: https://lnkd.in/dWWZFQCV #React #TypeScript #StyledComponents #RESTAPI #WebDevelopment #FinanceApp #Coding #JavaScript #Developer

13

1 comentário

𝗗𝗼 𝘆𝗼𝘂 𝘄𝗮𝗻𝘁 𝘁𝗼 𝗯𝘂𝗶𝗹𝗱 𝗲𝗳𝗳𝗶𝗰𝗶𝗲𝗻𝘁 𝗱𝗮𝘁𝗮 𝗽𝗶𝗽𝗲𝗹𝗶𝗻𝗲𝘀 𝗶𝗻 𝗝𝗮𝘃𝗮𝗦𝗰𝗿𝗶𝗽𝘁? I'm excited to share an NPM package I developed for data processing. With over 8 years of experience in the field, I've noticed a significant gap in libraries that offer a performant and easy-to-integrate solution for data processing, to address this, I created Caminho - an NPM package that abstracts essential concepts like: • Concurrency • Parallelism • Batching • Backpressure • Logging • Reduce Last week, I benchmarked Caminho against an open-source package that Emplifi uses for ingesting data from social networks. The results were shocking - Caminho outperformed the existing solution, being 𝟭𝟬𝟬 𝘁𝗶𝗺𝗲𝘀 𝗳𝗮𝘀𝘁𝗲𝗿 with significantly better memory management. Does this mean your data pipelines will be 100 times faster with Caminho? Not exactly. Data pipelines are largely driven by I/O operations, which aren’t influenced by the processing tool, however, using an efficient tool optimizes resource usage and enhances performance, allowing you to maximize usage of your hardware while giving you an ease to maintain codebase. Caminho is compatible with Node.js, Bun, Deno, and browsers, offering a user-friendly API to simplify your workflow. I’d love for you to try it out, share your feedback, and help boost its visibility - 𝗚𝗶𝘁𝗛𝘂𝗯 𝘀𝘁𝗮𝗿𝘀 are greatly appreciated. Thank you for your support! #JavaScript #NodeJS #TypeScript #NPM #WebDevelopment #SoftwareEngineering #DataProcessing #OpenSource #TechInnovation

47

1 comentário

Two years ago, I posted a guide on DEVTO explaining when to use rem, em, or pixels in web development. I initially created this guide because I couldn’t find an easy explanation on the web, so I wrote it in Portuguese to help others who had the same doubts as I did. Today, while reviewing some of my old posts, I noticed that this particular post had reached 10k views. So, I decided to recreate the post in English to help more people with this basic topic. Here’s a quick explanation: Pixel (px): An absolute unit representing a fixed size on the screen. In CSS, a pixel is not the same as a physical pixel but rather a reference pixel based on a 96dpi display. Usage: Ideal for fine-tuning and elements that require fixed dimensions, such as borders and precise positioning. It does not adapt to zoom settings or changes in the root font size. REM (Root EM): A relative unit based on the root font size of the document. By default, 1rem is equal to 16px but can vary if the root font size is changed. Usage: Great for ensuring accessibility and adaptability. When the root font size changes, all elements sized with rem adjust proportionally. It helps maintain a responsive and adaptable design. EM: A relative unit based on the font size of the parent element. Its size can vary depending on the context in which it is used, meaning it can inherit the size from its parent. Usage: Useful for defining font sizes, spacing, and line heights that are relative to the parent element’s font size. This allows the layout to adjust dynamically based on the text size of the parent element. Usage Tips: px: Use for fine adjustments and elements that do not need scalability. rem: Use for most of your layout to ensure flexibility and ease of accessibility maintenance. em: Ideal for properties that need to be dynamic relative to the parent element, such as internal spacing and font sizes. If you want to read the complete post check here: https://lnkd.in/dkuyw4Rn

5

Why NestJS Sucks (Or Does It?) 🤔 A Quick Look Before We Dive In" -> Opinionated vs. Flexible: 🤔 Express offers flexibility but can lead to inconsistent code. NestJS’s opinionated approach ensures a clean, scalable architecture. 🚀 -> TypeScript Built-In: 🛠️ NestJS integrates TypeScript by default, providing better debugging and strict typing from the start. . 📈 So, what makes NestJS worth learning? 1. Modular Architecture: 🧩  Organize your code with the @Module decorator.  2. Decorators:🏷️ Use @Controller and @Service for cleaner, more manageable code.  3. Dependency Injection:🔄 Leverage built-in dependency management for better organization. Curious to see what NestJS is all about? Stay tuned—we’ll be diving in soon! Check out the docs here - https://docs.nestjs.com #nestjs #nodejs

18

In my "1-Minute Tips with Diogo Machado" series, I share my favorite tools, libraries, and insights from over 13 years of software development. In this video, I'll dive into the incredible Lottie library - a tool I've successfully integrated with both React Native and Angular to improve animations and user experience. Tune in for a quick tip that could make a big difference in your next project! LottieFiles

6

3 comentários

Node.js API docs funny statement 😁 I found this on the official Node.js API docs because I wanted to send a reference to a friend, which made me chuckle! #Nodejs #DeveloperHumor #CodingLife #TechLaughs #ProgrammingFun #DevCommunity #APIDocs #CodingMemes #NodejsAPI

6

Five years ago, we started MuukTest with a question: Could we make "Great Software Testing and Automation" easier? My cofounder Renan Ugalde & I each have 20+ years of Software Development & QA experience. We've seen Bad Software Testing and Great Software Testing - way too much of the former, not enough of the latter: Bad Software Testing:  - Nonexistent professional testing team, expecting "developers to do all their own testing" (which 'works' until it doesn't) - Wild, non-disciplined, exploratory testing that doesn't help  - Testing that's treated as a second-class citizen in an engineering org, not as a partner - Reactive, under-resourced testing teams  - Testing with deficient coverage and no automation at all - Testing that's treated as the last step in an assembly line - Massive teams of testers, treated like a boiler room - Testing that slows engineering down I spent years of my life in Software QA and Testing roles like this… where I spent my Christmas holidays frantically, manually running regression tests across an entire application that *had* to be released yesterday. This is bad Software Testing. It is stressful for everyone and doesn't lead to good outcomes. Great Software Testing is:  - Proactive - A mix of (smart, disciplined, strategic) manual exploration and automation - Partner to engineering - Happens throughout the engineering cycle - Performed and coordinated by small teams of testing experts  - Employs amazing tools - Helps engineering move faster - Delivers insights, not more work Since 5 years ago, we have always believed that 'Great, Fast, Efficient Software Testing' will be made possible by AI. Bad testing happens because of bad ideas and bad tools, but with AI helping with a lot of the heavy lifting of test automation and maintenance, 'Great, Fast, Efficient Software Testing' is possible for more teams. Proud of our work in AI, making Great Software Testing possible for ANY software team. Great Software Testing means better software, faster development, happier customers, and better outcomes for all. 

25

Hey Developers! 🚀 As I said in the last post, today I'm going to tell you what really made me stop continuing the project I loved so much, creating events, helping the community, the feeling of "community" was something that really filled me. One of the biggest reasons I stopped was not consistency. Every project and everything you do, if it's not done consistently, falls apart. We held events every Saturday. Only on public holidays or if there were bridges would we not do it. I had excellent people who, when I couldn't, whether for personal reasons or illness, would be there to bring these events to a successful conclusion. I trusted and rely on the team I put together at the time. The problem was that the events started to be much the same, and we didn't create events just to talk about topics for beginners. We wanted more. Much more. But with this comes the problem: personal life. I began to see that it was taking up too much of my time. Even though I was growing, doing a lot of networking (we went to a lot of other events where people knew us from our own events), I started to think that I had to take some time for myself. 👪 I needed time for myself. For my family. Then the pandemic happened. I had to adapt, and we tried to do events online. We still did 1 online event, but it didn't taste like in-person to me. It's great to share knowledge, but the human part is missing... And that didn't make sense anymore. So I put this idea to one side. And then came the best and most beautiful phase of my life: my first daughter. 😛 And perhaps I'll continue a little more of my story in another post. If you have any questions about me, you can send me a message, comment, expose me without any problem. https://pedropcruz.pt #techcommunity #community #events #group #it #frontend #portugal #programmer #developer #coding #coder

1

🤔 We work A LOT with Node.js but... What is Node.js? ✨ 👉 https://nodejs.org/en 👈 🧠 Why is it so interesting? 🔷 Event-Driven, Non-Blocking I/O: Node.js's architecture allows for handling multiple connections efficiently, making it perfect for building scalable network applications. The asynchronous nature ensures that my applications are lightning-fast 🚀 🔷 JavaScript Everywhere: Using JavaScript for both frontend and backend streamlines the development process. It's amazing to use the same language across the stack, enhancing productivity and reducing context-switching. 🔷 Vast Ecosystem: The npm ecosystem is incredible, with over a million packages available. This means less time reinventing the wheel and more time focusing on what truly matters – delivering value to users. 🔷 Microservices and Serverless: Node.js integrates seamlessly with modern architectures. Whether I'm deploying microservices or leveraging serverless functions, Node.js offers the flexibility and performance needed. 🔷 Community and Support: The Node.js community is vibrant and active. From Stack Overflow to GitHub, there's no shortage of resources, tutorials, and support. It’s a fantastic feeling to be part of such a thriving ecosystem. 🔷 Real-Time Applications: Node.js shines with real-time applications like chat apps and online gaming. Socket.io, for instance, has made implementing real-time, bidirectional communication a breeze. Have you discovered anything new about this super used tool? Do you know anything more? Put it in the comments so everybody could learn something new!! #NodeJS #FullStackDevelopment #JavaScript #WebDevelopment #Programming #TechInnovation

2

I finally had time to write about my PRs to reduce the overhead of "npm run", I also talked about the feature I introduced in Node.js to profile what was slowing down npm, see more: https://lnkd.in/dfyjiRWR

33

4 comentários

🔧 Node.js at Scale: Engineering Beyond the Basics 🔧 Building applications with Node.js isn’t just about using it—it’s about mastering its advanced architecture patterns to achieve scalable, resilient, and high-performing systems. Here are some of the advanced techniques I use to push Node.js to its limits: 1️⃣ Event Loop Optimization: Understanding and controlling the event loop is critical for preventing bottlenecks. By profiling our applications and identifying “long-running tasks” (via tools like Clinic.js), I ensure we’re handling only short, non-blocking operations to maintain snappy response times even under heavy load. 2️⃣ Worker Threads for Heavy Lifting: While Node.js is single-threaded, using Worker Threads unlocks multi-threading for CPU-bound tasks. This avoids blocking the event loop and allows us to run complex computations (like data processing or encryption) without slowing down other operations. 3️⃣ Horizontal Scaling with Containers: Embracing containerization with Docker and Kubernetes allows for horizontal scaling of Node.js services across clusters. Combined with auto-scaling, we can dynamically allocate resources based on traffic demand while ensuring optimal usage of hardware. 4️⃣ GraphQL with Node.js: Moving beyond traditional REST APIs, I’ve integrated GraphQL to give clients more flexibility in querying their data, reducing over-fetching and improving API performance. Combined with DataLoader, I minimize redundant database queries, achieving both efficiency and speed. 5️⃣ Real-Time Applications with WebSockets: For real-time applications, especially chat systems, notifications, or live updates, WebSockets with Node.js is a game-changer. By leveraging libraries like Socket.io, I’ve built systems that maintain persistent, low-latency connections for millions of concurrent users. 6️⃣ CI/CD Pipelines for Automated Deployments: By setting up CI/CD pipelines with Jenkins, GitLab, or GitHub Actions, we automate testing, linting, and deployments. This ensures that our Node.js applications are not only up-to-date but also go live without breaking production. 7️⃣ Security Hardening with Helmet.js: Security is never optional. I ensure that Node.js apps are protected against common vulnerabilities by integrating Helmet.js, enforcing strict content security policies, and ensuring robust rate-limiting and input sanitization protocols. 8️⃣ Database Performance with Connection Pooling: Whether working with PostgreSQL, MongoDB, or MySQL, I maximize database efficiency by using connection pooling. This reduces overhead from constantly opening/closing connections and ensures the app can handle thousands of concurrent database operations smoothly. #Nodejs #ScalingNode #EventLoop #WorkerThreads #Security #CI_CD #Docker

5

I finished the Continuous Integration: pipelines and Automation Tests with the GitHub Actions course. What did I learn? 🤔 - Understand how to build a Go application. - How to identify compile errors. - How to set up the application using docker compose or makefile. - Discovered the power of Github Actions, and how fast it's quick off a pipeline, need to create a folder named '.github/workflows' inside a YAML file, this file is responsible for grouping the set of actions to build an application or running tests for example.

14