Chris Lopes

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.

4

2 Comments

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 Comments

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 Comments

I completed the fourth module (UI + Presentation) of the iOS Lead Essentials program 🥳! Here's a summary of what I learned so far 👇 - The fundamentals of good system design and architecture. How to think, design, and draw diagrams like a software architect. - Networking best practices to develop, maintain, and test a clean networking layer in iOS apps with key frameworks such as URLSession, URLProtocol, Decodable, and third-party code. Also, how to work effectively with backend teams. - Persistence best practices to effectively develop, maintain, and test a clean persistence layer in iOS apps using URLCache, CoreData, FileManager, Codable, and other key persistence frameworks. - UI, UX, and Presentation best practices, and how to develop, maintain, and test a clean UI and Presentation layer in iOS apps. How to use MVC, MVVM, MVP, and their variants, prototyping techniques, localizing apps, working effectively with designers, and how to create reusable UI/Presentation components. Click to see more: https://lnkd.in/dR9AD_nw

18

1 Comment

I developed a Ruby gem called InssCalculator to compute the Brazilian Social Welfare Contribution on the salary. Although it’s tailored specifically for the Brazilian context, I take pride in applying object-oriented programming principles to its design. Inspired by Sandi Metz’s book “Practical Object-Oriented Design in Ruby,” I followed the guideline that “if it has data and behavior, it might be a strong candidate to become a class.” The calculation method follows a progressive approach: the first salary level contributes a specific percentage, while subsequent levels have their own contribution rates. To enhance accuracy and maintain clarity, I structured the gem so that each salary level corresponds to a separate class. This design choice facilitates error detection during testing. I encourage you to explore the Git logs to witness my test-driven development (TDD) process in action. Through TDD, I aimed for precision in the calculations, surpassing some online solutions. Interestingly, I discovered that certain websites accumulate decimal results between salary levels, contrary to Brazilian rules, which mandate consideration of only two decimal places. I’m pleased that the gem’s test suites are accessible to new developers, enabling them to quickly grasp the underlying rules. https://lnkd.in/d22hjG-4 #ruby #rubyonrails #developer #backend #TDD #tdd

13

2 Comments

🚨 Navigating the X Ban in Brazil: A Technical Perspective 🚨 (message me if you are interested in implementing software to continue your business.) As many of you may know, the recent ban of X (formerly Twitter) in Brazil has sparked significant challenges, particularly within the programming and tech community. This platform, which many of us rely on for real-time updates, networking, and knowledge sharing, is now inaccessible in a critical market. **Adaptability in the Face of Change** Adaptability is a necessity. While the sudden loss of access to X presents real difficulties, it also offers an opportunity for us to innovate and explore alternative solutions. 🔧 Technical Solutions to Stay Connected Alternative Platforms: Exploring other social platforms like [LinkedIn, Mastodon, etc.] to stay connected with the community and receive updates. Custom APIs and Aggregators: Implementing custom APIs to pull in data from various sources, ensuring that I don’t miss out on critical industry news and insights. This includes setting up RSS feeds and using Zapier to automate the aggregation of relevant content. Communication Tools: Using encrypted messaging services and VPNs to maintain communication with peers and clients who are also affected by this ban (while respecting the laws and being careful not to advise VPN usage for the Brazilians themselves as it is labeled as illegal). ⚙️ Problem-Solving in Action In this case, I'm ensuring that my productivity and ability to deliver quality work remain unaffected or the effects minimalized. This situation underscores the importance of being resourceful and having a toolkit of technical skills ready to deploy when traditional methods are no longer available. 🤝 Supporting the Community It's crucial that we stand together and share knowledge during times like these. I’d love to hear how others are navigating this disruption. What tools or strategies are you finding effective? Let’s keep the conversation going and find ways to overcome these challenges together. If you are interested in the technical workarounds, message me and we can go over your options as companies and individuals.

3

1 Comment

When the codebase grows, it can become complex and unwieldy. Modularization can significantly simplify the development process. As the codebase expands, it can turn into a monstrous beast. That's where modularization shines, allowing you to organize business logic, functions, objects, and variables into well-defined modules. By leveraging CommonJS or ESM strategies, you can export these modules and keep your codebase clean, maintainable, and scalable.

1

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

Are there any #informationarchitects or #ux designers in my network here that could consult with me on improving the IA of the Node.js Learn section? At the recent Collab Summit in Dublin, we discussed the need to refactor our linear journey. Matteo Collina got the ball rolling, which we are tracking at https://lnkd.in/g4UhiMVV My instincts as an once-proficient-now-amateur UX practitioner are as follows: - inventory the content - think through a card sort strategy, from maintainers, BUT ALSO, users - re-org easy wins - identify gaps, breakout issues - recruit writers to help fill in gaps - testing??? This is another great example of the multi-disciplinary work an open source project benefits from. It's not all code, and never was, as we have grown and found each other. https://lnkd.in/gNPUEVDB tries to make a strong case for this, and it's been fun to reflect on how to embody it. #opensource #nodejs #contentdesign #technicalwriting

18

🤔 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

Finally Breaking My Silence (Why I Decided to Start Sharing My Journey) After 20+ years in tech, from selling ice cream in Rio's favelas to building distributed systems at Microsoft and AWS, I realized something: I've been too quiet. Why I never shared before: - Too focused on building - Imposter syndrome - "Others know more" - Always next challenge But yesterday something hit me: The kid selling ice cream in Rio would have killed for the knowledge I have today. So I made a decision: Starting today, I'll share: - Real engineering lessons - System design insights - Cloud architecture decisions - Raw truth about tech career No sugar coating. No buzzwords. Just hard-earned lessons from: - Building Azure's notification system - Scaling AWS services - Getting patents - Leading global teams - Starting from zero What you'll get: 1. Deep technical insights - Distributed systems - Cloud architecture - Real scaling problems - Performance optimization 2. Career real talk - From favela to big tech - Breaking barriers - Growth mindset - Actual challenges 3. Startup insights - Early decisions - Technical debt - Team building - Real trade-offs Why now? Because somewhere there's a kid like I was Thinking tech is impossible Thinking dreams are too big Needing to know it's possible Follow along if you want: - Zero fluff - Deep technical knowledge - Real experiences - Practical insights PS: Yes, I'll share the ice cream selling strategies too. Some of them still work in system design 😉 Special thanks to Thiago Caserta and Marcelo Cauduro for pushing me out of my comfort zone. Sometimes you need great co-founders to remind you that your journey matters.

177

25 Comments

Moving My Blazor WebAssembly Blog to Hashnode Headless CMS #dotnet #blazor #hashnode

7

2 Comments

Hi, there! Today I concluded a #react project called "CEP Finder". This project consumes an API from ViaCep Webservice CEP to display the CEP address entered by the user. This API can find any CEP in Brazilian territory. I'm not sure if it's the same thing, but I had done a research and I discovered that in the USA there is a similar system. There, they call it Zip Code instead of CEP.   Anyway, I've known that many Brazlian programming students have done projects using this idea, that is, the idea of consuming this specifc API or a seemed one, but I implemented my own design and features. Please, check out my CEP Finder project and my other authorial projects too by clicking on the links below. Thank you for reading this post so far. I wish you a happy day wherever you are! CEP Finder: https://lnkd.in/duywTMXi My other authorial porjects: https://lnkd.in/d45BsxkN

21

8 Comments

🚀 New Article: Integrating Sentry with CodePush in React Native! 📲✨ If you're a React Native developer aiming to improve your app's stability and user experience, this guide is for you! In my latest article, I walk through the process of combining Sentry with CodePush to enable real-time error tracking and seamless over-the-air updates. This setup helps teams tackle issues faster and deploy fixes without the need for app store approval, keeping the experience smooth for users. Check it out to see how Sentry’s in-depth error insights paired with CodePush updates can make a huge difference in your development workflow! 👇 #reactnative #sentry #android

5

1 Comment

I've often heard the phrase: "Node.js is single-threaded," not only from Java and C# developers but from Node.js developers. However, since version 12, with the introduction of worker_threads, Node.js can now work with multiple threads. Many articles demonstrate this, but I'd like to share a video by master Erick Wendel, who shows us the multithreading capabilities in Node.js. https://lnkd.in/dphheR-v

8

1 Comment

Hi All, In the software engineering field we have tons of ways to solve a problem and usually we apply design principles to get it done. Today, I would like to share two design principles which allows: - Loose coupling between classes and their dependencies - Systems with reusable, testable, maintainable and pluggable components. Please check out my article related to Inversion of Control (IoC) and Dependency Injection (DI)

3

🚀 Node.js 21 is Live! Here’s What’s New 🚀 Node.js version 21 brings fresh improvements to make JavaScript development smoother, faster, and more secure. Check out the key updates: • Enhanced Performance: Improved startup times and lower memory usage, making Node.js applications run faster and more efficiently. • Experimental Permissions Model: Adds fine-grained control over app permissions, allowing developers to manage file system, network, and environment access with precision. • New Built-in Testing Library: Simplifies testing with native support for unit and integration tests, so no more extra setup needed. • Improved V8 Engine: Upgraded to V8 version 11.8, bringing better JavaScript and WebAssembly performance. • Stable Web Streams API: Full support for the Web Streams API, enabling efficient handling of streams within your applications. • Updated URL Parsing: Enhanced handling of URLs, making it easier to work with complex URLs securely and accurately. • Security Patches and Updates: Strengthened security with new patches, protecting your applications from the latest vulnerabilities. Node.js 21 takes efficiency and security to the next level. Ready to upgrade?

10

1 Comment

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