Your path to senior developer and beyond! 🚀 In-depth frontend & fullstack courses. Try our 200+ courses for 7 days for free with the link:

Industry

Technology, Information and Internet

Company size

11-50 employees

Headquarters

Minneapolis, MN

Type

Privately Held

Founded

2008

Specialties

JavaScript, HTML5, Training, React, Web Development, Node.js, Vue, Front-End, Full Stack, Python, CSS, Go, Rust, TypeScript, and Next.js

• 147,452 followers

  3h

  Hover Proximity Using Modern CSS You can always easily style :hover, but what if you want the NEXT item to have styling too? Or, just a smidge harder, the PREVIOUS item. How about multiple in any direction?

  Hover Proximity Using Modern CSS https://blog.master.dev

• Master.dev (Formerly Frontend Masters) reposted this

  1d

  This is the clearest breakdown of frontend architecture I've worked through in a while, from modular monoliths up to full micro-frontends. I've been part of a team maintaining and building features on a 14-package monorepo in production. I've also seen teams reach for micro-frontends because it sounds right, not because they had the problem it solves. I've been going deep on this lately, and the main insight I've taken away: You adopt micro-frontends when coordinating a single codebase costs more than running a distributed one, when release trains start queuing and teams step on each other. Not before. Also a useful reminder that "monorepo," "multi-zone," and "micro-frontend" are three different things people constantly mix up. The right move is usually the boring one: the simplest architecture that removes your actual bottleneck. Thanks for the shared knowledge, Maxi Ferreira.

  Architect Scalable Frontend Applications master.dev

• 147,452 followers

  5d

  Laravel Fundamentals is next week! 🚀 Join Leah Thompson from the Laravel Team on Aug 25, 9:30am-4:30pm CDT, building a fullstack app with React & Inertia.js. Learn routing, auth, background jobs & more. Ship a real app by end of day. RSVP: https://lnkd.in/eZaATZnV

• 147,452 followers

  6d

  Devs push constantly. If every push triggers a pipeline, you're burning cash. In our Cloud CI/CD with GitHub Actions course, Erik Reinert walks through a change that seems small but saves real money: gating pipeline runs behind pull requests instead of pushes. Push code with no PR open, and the pipeline simply doesn't run. Nothing happens until a pull request exists. Why does this matter? Because developers push constantly, and every push used to spin up a full pipeline. Imagine watching five pipelines overlap each other because someone was pushing fix after fix after fix, each one provisioning dozens of VMs in the background. Switching the trigger from push to pull request means you only pay for CI runs when the code is actually ready for review, not every time someone nudges a commit. It's a simple config change with an outsized impact on cloud spend and pipeline chaos. Full walkthrough in our Cloud CI/CD with GitHub Actions course: https://lnkd.in/dKd7k3GH

• 147,452 followers

  6d

  ⏰ Starting in 1 hour! Codex for Backend Engineers with Spencer Schneidenbach (CTO, Aviron Software / Microsoft MVP) kicks off at 9:30am CDT today. If you’re a backend engineer, tech lead, or full-stack dev looking to bring AI-native workflows into real production systems (APIs, data models, migrations, debugging, and safe refactors), don’t miss it. 📺 Watch Now → https://lnkd.in/eJuxZ4z8

  Codex for Backend Engineers — Exclusive Workshop master.dev

• Master.dev (Formerly Frontend Masters) reposted this

  Senior Software Engineer at Adobe | Creator of Gravity Box (400k+ Players) | Shipping AI features end-to-end | Speaker | lutr.dev

  2w

  I just spent 8 hours on my first backend course, and it was well worth it! It's the "Full Stack Fundamentals, v3" course by Jem Young on Master.dev (Formerly Frontend Masters). Most of my work sits on the frontend, so the server and systems side has always been the part I could use but not really explain. So that's the gap I wanted to close. And this course was full of foundational stuff that finally made things click! Here are a few of the areas it covered: - How HTTP works under the hood. Headers, status codes, HTTPS and certificates, and the jump from HTTP/1.1 to HTTP/2. - What databases give you over just saving to a file. Relational vs non-relational, primary and foreign keys, SQL basics, and why prepared statements matter. - Containers and how they run. Docker, Dockerfiles, images, and why a container is lighter than a full virtual machine. - How real-time communication actually works. WebSockets, Server-Sent Events, long polling, and WebRTC, and when you'd reach for each one. Really well done by Jem Young!

• 147,452 followers

  1w