![]() This week, we’ve got baby (JavaScript) driver, the festival of the century, and a new CSS selector that pays tribute to a classic R&B group. Welcome to #114.
It’s not the car, it’s the driver Volume up, pedal downWe, like most people, appreciate a good driver. Minnie, Adam, Baby… all fantastic. So PlanetScale definitely caught our attention last week when they announced the “PlanetScale serverless driver for JavaScript” (name clearly inspired by “Dwight Schrute’s gym for muscles”). If you haven’t heard of PlanetScale, it was started when a bunch of homies from GitHub decided to dip their toes into the warm waters of hosted MySQL and make a database that operates a lot like Git (you can branch and merge, making migrations and updates as easy as a pull request). Previously, you needed to make a “raw TCP connection” (sounds dirty) to whisper sweet Here are a few noteworthy details:
Bottom Line: Another huge W for the edge, serverless, and fetch (also wouldn’t mind if the 🌎Scale team wanted to send us one of them bomber jackets).
“I still think it needs more pop” [sponsored] Bugherd will break you out of the infinite feedback loopDante’s 8th level of Dev Hell: trying to get feedback on a website from a big team. You create the new landing page and send it to your manager, who gives you feedback and sends it to the VP, who also gives you feedback and “CC’s a few more stakeholders” who also give you feedback… for eternity. Thankfully, there’s BugHerd:
It saves a lot of time and is our favorite way to work with QA teams, outside clients, or contractors. Check it out – and see why over 10,000 companies use it.
The celebs are out at BootFest Bootie’s 11th birthday bashTo celebrate Bootstrap turning 11 years old last week, we wanted to throw a huge, 2011-themed party with an all-dubstep dance floor, a jQuery tattoo station, and Justin Bieber’s Never Say Never documentary playing on repeat. But since none of you responded to our e-vite for BootFest 2022, we’ll just have to celebrate in email form. How we got here: Bootstrap was never supposed to be the next big thing. Mark Otto and Jacob Thornton were just trying to help their team at Twitter build internal tools that looked a little less janky (Retool wasn’t around yet 😢). But after debuting their first version of “Twitter Bootstrap” at the company’s Hackweek, it immediately took off within other teams at Twitter. So Mark and Jacob started working with an equal mix of designers and engineers to create a more extensive library of components that looked great and were easy to implement by adding a few classes to your HTML. When they open sourced Bootstrap in August 2011, developers ate it up. Web apps were still just starting to become a thing, and Bootstrap provided a helpful starting point for devs who weren’t used to building (or styling) richer, more interactive experiences for the web. Even though we all eventually got tired of seeing the same Bootstrap sites everywhere, its 11-year run (that’s 77 in web years) continues to be super impressive. They’ve gone through major rewrites — incorporating responsive design, switching from Less to Sass, adding Flexbox support, removing jQery dependencies — while adding dozens of new components along the way. Today, Bootstrap is still the #7 most-starred project on GitHub and gets more npm installs than Tailwind CSS. Turns out that being well-designed and easy to use is still an undefeated combo in OSS. Bottom Line: BootFest might’ve been brief, but it was definitely more fun than half of this summer’s tech conferences (it smelled better too). JobsSenior or Staff Front-end Engineer — React (100% Remote)Close.com is looking for 3 experienced individuals that have a solid understanding of React and want to help design, implement and launch major user-facing features. Close is a 100% globally distributed team of ~55 high-performing, happy people that are dedicated to building a product our customers love. JS Quiz — Sponsored by Sleuth.ioSleuth was created by the founding engineer of Jira, and is the best way to track & improve your team’s engineering efficiency (without spying on them). Why does this code work?
Specifically, why does Cool Bits
Spot the Bug Solution — Sleuth.io
As mentioned earlier, if you look at The reason is because the
|