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

Demystifying Active Record: Your Powerful Ally in Rails Development Active Record, a core component of Ruby on Rails, simplifies interacting with relational databases. Let's dive into its capabilities and see it in action!What is Active Record?An Object-Relational Mapper (ORM) that bridges the gap between Ruby objects and database tables.Acts as an abstraction layer, allowing you to work with data using Ruby objects instead of raw SQL queries.Benefits of Using Active Record:Increased Developer Productivity: Write database interactions in Ruby code, focusing on business logic instead of low-level SQL.Reduced Errors: Active Record handles common database operations, minimizing the risk of SQL syntax errors.Improved Code Maintainability: Code becomes more readable and easier to maintain as it reflects your domain model.Example: Building a Blog with Active RecordWe define Post and Comment models representing database tables.The has_many and belongs_to methods establish relationships between models.Validations ensure data integrity before saving records.We create, find, and destroy records using intuitive methods on the model itself.Active Record handles the underlying SQL queries for us.This is just a glimpse! Active Record offers more:Complex queries with methods like where, order, limitData associations like has_one, has_many :throughDatabase migrations and schema management**Active Record empowers you to focus on building your application logic, leaving the database interactions to this powerful tool. **Let's discuss! Share your experiences with Active Record in the comments. What are your favorite features or tips?#RubyOnRails #ActiveRecord #DatabaseManagement #RailsTips #DatabaseLove

7

Finish the Guess-Who Scrap CLI project written in Golang. Now, I can download and extract data on famous Brazilian people from Wikipedia, including specific states and cities. The data is saved in either Postgres or an in-memory SQLite database. In this project, I used Go as the programming language, GORM as the ORM, Cobra for the CLI, and Viper for the properties file. You can see more at https://lnkd.in/dvtTPi8R. Now, the next step is to work on the API project (https://lnkd.in/dUFwuXS8), using Quarkus, Langchain4J, Instruct Labs, etc to get the clues based on the data collected before, by the scrap project.

4

The release of Node.js 22 is available now! ​​Highlights in Node.js 22 include require()ing ESM graphs, WebSocket client, updates of the V8 JavaScript engine, and more!#nodejs #websocket #javascript

14

🎉 Exciting news! I've just released EasyAssets, a Flutter package that takes the headache out of asset management! 🚀Ever found yourself drowning in a sea of asset strings, desperately wishing for a life raft? That was me, until I realized – why not build the raft myself? 🏊‍♂️💡EasyAssets automatically generates a Dart class with type-safe constants for all your assets. No more typos, no more string gymnastics – just smooth sailing! ⛵Why I built it:1️⃣ Couldn't find a library that did exactly what I needed2️⃣ Wanted to simplify asset management for Flutter devs everywhere3️⃣ Thought it'd be fun (spoiler: it was!)But this is just the beginning! On the horizon:🔮 Build runner integration🔮 Customizable output folder🔮 And more!I'm all for open-source collaboration, so if you're itching to contribute or just want to check it out, hop on board! 🏴‍☠️GitHub: https://lnkd.in/gTWb5DGKpub.dev: https://lnkd.in/gHQ5ThuVLet's make Flutter development a breeze, one asset at a time! 💨🌈#Flutter #OpenSource #DartLang #MobileAppDevelopment

3

THE SURPRISING SCALABILITY OF MONOLITHSA lot of folks hate monoliths, but you can’t argue with their success in industry. “DECOMPOSE THE MONOLITH” engineering projects have often failed in reality after huge investment or brought developer velocity to a standstill.Many very successful public tech companies have scaled monoliths to massive traffic and engineering orgs, and I’ve seen the realities from the trenches:- Coinbase, Rails + MongoDB monolith- Nextdoor, Django + Postgres monolith- Facebook, PHP + MySQL monolith- Instagram, Django + Postgres monolithsADVANTAGES OF A MONOLITH:- Developer velocity super fast and shipping new features very efficient - all-in-one, batteries-included frameworks.- Existing patterns & libraries for everything: Async jobs, testing, database migrations, authentication, billing, etc.- Really easy to hire people with experience in frameworks like Rails/Django/PHP/etc- You don’t waste time on premature optimization around RPC, service discovery, etc etc - invest in PMF and features customers want.- Monolithic repos keep business logic adjacent so it’s very easy to coordinate large scale changes/refactors.DISADVANTAGES OF A MONOLITH:- Blast radius of a defect is really high. For example a performance regression in one part of the site can easily take the entire application down. I’ve seen this happen many times in monoliths.- Minimum unit of scaling is an instance of the whole monolith and the database attached to it. Very challenging to e.g. scale up reads from the activity feed separately from writes to the account database. This is why there is ALWAYS pressure inside an organization to “DECOMPOSE THE MONOLITH”.- Tend to be sub-optimal in terms of memory usage and runtime performance. Infrastructure costs typically significantly higher than much more optimized services.There are challenges scaling monoliths and you need expertise to do so. But these are very much solvable problems.

12

How do you manage TODOs left in your code?I personally use a VS Code extension to format those comments differently so they stand out. I use a second extension to create a list of TODOs that mirrors the file structure, which can be useful when debugging or squashing tech debt in a particular area of the codebase. Do you put TODO's straight into Jira or your task management software? Do you always finish them or never come back to them? Have you ever had a major issue from not completing a TODO that you forgot about?

6

2 Comments

A few days ago, I started working on a prefetch implementation based on the recommendations from Unified Streaming’s documentation: https://lnkd.in/dKhQ6phN.Here’s the code: https://lnkd.in/dhwWeWdX(NGINX + Lua and a web server written in go for testing purposes)I haven’t tested it in production yet, but I would appreciate hearing from anyone with experience implementing something similar. If that’s you, could you please share your results?#videostreaming #livestreaming #videoengineering

31

Added to the Github Star Leaderboard changes in standings in the past month:Leaderboard features top 1000 public github repos, based on the number of starshttps://lnkd.in/guYaJaDePackages from this list that I useEach row is:Place, change in standing, package, number of stars- 10, 0, React by Facebook, 226k- 19, 0, Linux, 176k- 21, 0, ohmyzsh, 171k- 22, 0, Bootstrap, 169k- 26, 0, VSCode by Microsoft, 161k- 35, 0, Transformers by Hugging Face, 130k- 38, 0, Next.JS by Vercel, 124k- 41, 0, React Native by Facebook, 117k- 52, 0, create-react-app by Facebook, 102k- 54, 0, TypeScript by Microsoft, 99k- 61, 0, Material-UI, 92k- 81, -1, PyTorch, 81k- 82, -3, TailwindCSS, 81k- 95, -1, OpenCV, 77k- 103, +2, FastAPI by Sebastián Ramírez Montaño, 74k- 182, +1, scikit-learn, 59k- 236, 0, Git, 51k- 248, 0, Traefik by Traefik Labs, 49k- 256, -4, Prettier, 48k- 338, -3, Pandas, 42k- 360, -8, Yarn, 41k- 461, -5, Vim, 35k- 509, -2, Tmux, 34k- 6701, -3, pytorch-image-models by Ross Wightman, 31k- 645, +33, Ruff by Astral, 29k- 760, -5, pytorch-lighning by Lightning AI, 27k- 782, -7, NumPy, 27k- 945, -10, Eslint, 24k- 1000, -19, Ngrok, 24k----GitHub star leaderboard looks very stable. Only Ruff stands out.P.S. Pydantic by Samuel Colvin and Albumentations do not have enough stars to get to the top 1000.

21

16 Comments

Taking a break from the courses that I've been writing (and warming up for writing a Node.js course):https://lnkd.in/eApqU3ee

22

1 Comment

C Is Not a Low-level Language (AKA Your computer is not a fast PDP-11)https://lnkd.in/d7CMUPsA

10

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

5 Key Differences Between Working for a Startup vs. a Corporate Company for Software EngineersWe are often used to learning from big companies.They provide established patterns and tools to solve problems. However, it is crucial to understand the differences if you aim to work in a startup. Many patterns applicable to corporate companies are not valuable in a startup.Before joining a startup, ensure you consider these critical differences from corporate companies:#1. Scope of Responsibilities𝗖𝗼𝗿𝗽𝗼𝗿𝗮𝘁𝗲: Engineers typically have more defined roles with clear boundaries (e.g., front-end, back-end, DevOps).𝗦𝘁𝗮𝗿𝘁𝘂𝗽: Software engineers wear many hats, handling tasks across the stack and sometimes even beyond coding (like product management, customer support, or operations).#2. Pace and Urgency𝗖𝗼𝗿𝗽𝗼𝗿𝗮𝘁𝗲: While deadlines exist, the pace tends to be slower. The process may follow established protocols or regulatory guidelines.𝗦𝘁𝗮𝗿𝘁𝘂𝗽: There is a high sense of urgency. Deadlines are tight, product iterations are fast, and the "move fast and break things" mentality is common. Engineers need to be adaptable and quick to ship features or fixes.#3. Decision-Making and Bureaucracy𝗖𝗼𝗿𝗽𝗼𝗿𝗮𝘁𝗲: Decision-making can be slow, with multiple layers of approval. 𝗦𝘁𝗮𝗿𝘁𝘂𝗽: Decision-making is fast and often informal.#4. Risk and Stability𝗖𝗼𝗿𝗽𝗼𝗿𝗮𝘁𝗲: Job security is typically higher, but engineers might have less freedom to take bold technical risks due to policies, legacy systems, or stakeholder concerns.𝗦𝘁𝗮𝗿𝘁𝘂𝗽: Job stability can be lower, and the company’s future may hinge on product-market fit, funding, or other volatile factors.#5. Learning and Growth Opportunities𝗖𝗼𝗿𝗽𝗼𝗿𝗮𝘁𝗲: Growth can be slower due to more specialized roles, and there may be less exposure to different aspects of the business.𝗦𝘁𝗮𝗿𝘁𝘂𝗽: The fast pace and range of responsibilities in startups often translate to rapid learning.#StartupVsCorporate #SoftwareEngineering #TechCareers #StartupLife #CorporateLife #SoftwareEngineerTips #CareerGrowth #TechJobs #ProductivityHacks #LeadershipInTech #CareerDevelopment #TechIndustryInsights #StartupCulture_____________Do you want to learn more about being a software engineer in the startup world?Subscribe to https://lnkd.in/d_4XyCiN

8

Enhancing The New York Times' Web Performance with React 18 — Late last year, the team at The New York Times aimed to leverage React 18 on their flagship news site. This case study explores the challenges they faced during the upgrade and highlights the significant benefits they achieved. It's an insightful read for anyone interested in web performance and modern web technologies.https://lnkd.in/g8eyi8qR#react #web #performance #caseStudy

12

I was trying out Vitest, and thought to record a video on how to mock NPM packages (watch it if you use Jest as well - it's the same). It's a common practice, especially when you're using packages like "uuid" or "nanoid" - packages that generate stuff, but you want the output to be either constant or at least predictable. That's when you mock them! Check out the video, and make sure to watch until the end because there are two solutions 😁https://lnkd.in/g92PC2Nv#vitest #testing #unittest #npm #mocking #packages

9

1 Comment

🚀 Mastering Fork Maintenance in Open Source Projects 🚀Maintaining forks of open-source projects can be challenging, but Joaquim Rocha shares some invaluable tips to make it easier. From using atomic commits to contributing changes back upstream, his guide covers essential practices for smooth fork maintenance.🔹 Atomic Commits: Keep your git history clean and conflicts minimal by making each commit focused on a single update.🔹 Identify Fixes: Use conventions to tag your commits, making it easier to manage and squash fixes.🔹 Avoid Evil Merges: Ensure merge commits don't introduce changes to maintain a clean history.🔹 Rebase Often: Regular rebasing reduces conflicts and keeps your fork up-to-date with upstream changes.🔹 Contribute Back: Simplify maintenance by contributing your changes back to the original project.Check out Joaquim's full guide for more insights! 🌟#OpenSource #Git #ForkMaintenance #DeveloperTips

4

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 downI 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 workSince 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

Code simplicity equals easier to change & easier to understand. Explained so well in a short concise 10min talk - https://lnkd.in/dDYzuVh7Note: Although the title says React but the concepts can apply to any code you write.

1

𝐖𝐡𝐲 𝐘𝐨𝐮 𝐒𝐡𝐨𝐮𝐥𝐝 𝐂𝐡𝐨𝐨𝐬𝐞 𝐂𝐥𝐨𝐣𝐮𝐫𝐞 for Your Next ProjectAs developers, we’re always looking for tools that simplify complexity and boost efficiency. Clojure does exactly that—here’s why it might be the game-changer for your next project:1️⃣ Simplicity is Key• Clojure emphasizes minimalism, reducing complexity in code.• Immutability makes your code easier to reason about and maintain.2️⃣ Built for Modern Challenges• Designed to handle concurrent programming with ease.• Offers powerful concurrency primitives like atoms, refs, and agents to manage state seamlessly.3️⃣ Leverages the Power of the JVM• Runs on the Java Virtual Machine (JVM), giving access to a rich, stable ecosystem.• Combines JVM robustness with functional programming expressiveness.4️⃣ Lisp for the Pragmatist• Code is data: Enables powerful metaprogramming and DSL creation.• Retains Lisp’s flexibility while being practical for real-world applications.5️⃣ Thriving Ecosystem• Vibrant community and libraries like Ring, Compojure, and Luminus for web development.• REPL-driven development enhances productivity and debugging efficiency.𝐓𝐡𝐞 𝐓𝐚𝐤𝐞𝐚𝐰𝐚𝐲Clojure brings simplicity, immutability, and concurrency together, making it a top choice for modern software challenges.Whether it’s scalable microservices, data-heavy workflows, or experimental projects, 𝐂𝐥𝐨𝐣𝐮𝐫𝐞 𝐜𝐨𝐮𝐥𝐝 𝐛𝐞 𝐭𝐡𝐞 𝐤𝐞𝐲 𝐭𝐨 𝐲𝐨𝐮𝐫 𝐧𝐞𝐱𝐭 𝐛𝐫𝐞𝐚𝐤𝐭𝐡𝐫𝐨𝐮𝐠𝐡.What’s your take on functional programming or Clojure’s ecosystem? Let’s discuss in the comments! 👇#Clojure #FunctionalProgramming #ProgrammingTools #SoftwareDevelopment

9

C# keeps getting better every day, increasing software developer productivity, and we've managed to help save around 70% of the cost of Devprime plant accelerators 🔥#dotnet #chsarp #devprime #dotnet #dotips #code #visualstudio #microservices