Jacob Herper

@wesbos Congrats! Somehow had to read that twice - thought the name was "World August Bos" 🤦‍♂️

Hello World August Bos We welcomed Bos baby #4 yesterday. Had a home birth on a beautiful, sunny holiday Monday. Mom and baby are doing great! (I am a little sleepy, thanks for asking)

@helloitsolly @thadkrugman @b333n I assumed it was for an engineer and likely senior (as most freelancers / contractors need a certain level of experience to be effective at what they're doing). But fair enough.

@JakeHerp @thadkrugman @b333n 1. It's not an engineer 2. It's not senior

A freelancer just asked us for a $5,000 sign on bonus

@helloitsolly @thadkrugman @b333n $60 is less than 50 quid. Not exactly a high hourly rate, considering a senior engineer in the UK will earn that in a full-time job with paid annual leave and other benefits.

@thadkrugman @b333n The U.S. is not the whole world

@Worldle_Game Austria isn't bordering Switzerland? 🤔

@wolfr_2 @Jonnotie Kind of like saying you don't need to use hooks in React, but nobody seriously writes class components anymore. I'm not sure how I feel about the direction Svelte is moving into.

@Jonnotie As far as simplicity goes it is a step backwards but you don’t have to write your code that way and if you need it, it’s a handy tool to have I think (instead of finding yourself writing weird code to work around the library)

I’m looking to learn a new framework other than React/NextJS. I’m not a full stack developer. I’m more of a “design engineer”. I’ve been doing html/css for 20 years, and React (up to a point) for 5 years. It’s getting too complex and it stops me from building fast. Any recs?

@nxcoventry Thanks for this information. I tried calling that number all day, but unfortunately nobody ever answers. Is there an alternative contact method?

@JakeHerp Hi Jacob, I am very sorry to hear if this please Contact the garage below if you have lost property on this service. National Express Coventry garage 2 Ford Street Coventry CV1 5WT Telephone: 024 7526 8970 Monday to Friday, 10am to 2pm

@nxcoventry my daughter lost her favourite toy on bus 6 today around 2:20pm (she left the bus near Sainsburys coming from Tanyard Farm towards Coventry). We'd be very grateful to get it back, as she is heartbroken 😢

@jaredpalmer @vercel @v0 It was great to meet you in London the other day. Really interesting stuff. Can't wait to play with the new API

We have been working on a new API for the @Vercel AI SDK based on React Server Components and Function Calling that will let you mix both premade and generative React components (like @v0) into AI-native streaming chat UIs. With this update, you’ll be able to move beyond plain text and markdown and finally allow your users to interact with AI using rich component-based interfaces. I’ll be giving a keynote about this and more in SF next week at our AI Night. Register here: vercel.fyi/QBKffED

@jacksoncheek @rauchg Hey @jacksoncheek, just wondering how reliable the data is? I checked the API responses for a few of my recent flights and the aircraft_icao is always `null`.

@rauchg That’s me! Vercel is great, thanks for the tool!

Fascinating to see the reaction to the MAX incident. Including folks shipping apps in 2 days 😲 ismyplanea737max.com

@wesbos I think this skews the results, as iTunes isn't really a thing. Apple Podcast might be the better term.

How do you listen to podcasts?

@elizlaraki The one thing that really bothers me from a design perspective are the light shadows in dark mode.

15 years ago, I helped design Google Maps. I still use it everyday. Last week, the team dramatically changed the map’s visual design. I don’t love it. It feels colder, less accurate and less human. But more importantly, they missed a key opportunity to simplify and scale. ––– Google Maps has started to widely roll out updated map colors: - All roads are now gray - Water changed from blue to teal - Parks and open spaces are now mint green It seems the goal was to improve usability and make the maps more readable. Admittedly, I do think major roads, traffic, and trails stand out more now. But the colors of water and parks/open spaces blend together. And to me, the palette feels colder and more computer generated. But color choices aside… If the goal was better usability, the team missed a big opportunity: Google Maps should have cleaned up the crud overlaying the map. ––– So much stuff has accumulated on top of the map. Currently there are ~11 different elements obscuring it: - Search box - 8 pills overlayed in 4 rows - A peeking card for “latest in the area” - A bottom nav bar (Personally, I would LOVE to see usage metrics for all these overlays.) The map should be sacred real estate. Only things that are highly useful to many people should obscure it. There should be a very limited number of features that can cover the map view. And there are multiple ways to add new features without overlaying them directly on the map. ––– Here’s how it could look: - Keep the search box - Keep the bottom bar - Remove everything else from the map - Roll the most used features into the bottom bar - Bury the less used features elsewhere in the app I assume the search box and directions are top priority and should remain prominent. My Location and map layers (satellite, traffic, etc.) could move to the bottom bar. The explore overlays (restaurants, gas, etc.) could live in the bottom bar in “Explore” and open as cards. The additional space in the bottom bar could be used for Saved, as a “More” option, or could be removed entirely. There are many variations of how features could be arranged. But the key points are: - Dramatically simplify - Strongly prioritize map visibility - Bury legacy and low use features ––– It’s normal for products to accumulate features over time. But it’s also super important to stay vigilant and continually clean them up. In many ways, it’s interesting to see history repeating itself. In 2007, I was 1 of 2 designers on Google Maps. At that time, Maps had already become a cluttered mess. We were wedging new features into any space we could find in the UI. The user experience was suffering and the product was growing increasingly complicated. We had to rethink the app to be simple and scale for the future. It seems like it’s time for Google Maps to do this again… ––– For more on design + tips for early stage founders, follow me on X: @elizlaraki

I strongly believe that if you're using LLMs to generate code, it's super super super important that you (human) can still: → understand the logic → analyze/verify the logic → modify the logic Otherwise you're automating the creation of LLM-flavored black boxes that become impossible to maintain.

@TheJackForge I'd say it really depends. As a senior dev with lots of experience salaries are getting close to 6 figures, some will pay more, many pay less. I'd say the ceiling overall is at around £120k without going into leadership positions.

@thekitze And my wife is complaining that I keep all the iphone and macbook boxes 😂

me until 2015: fk apple it's an evil overpriced company and only iSheep would fall for their scams and schemes, my android is runinng a custom ROM and my linux distro has everyt- me now:

🔥 JavaScript Sets are about to become a lot more useful with these 7 new methods: .difference() .intersection() .symmetricDifference() .union() .isSubsetOf() .isSupersetOf() .isDisjointFrom()

@ReceptionRK @TemplarsPrimary Thank you again for all you did this year! Enjoy your well-deserved summer break!

What a fantastic year we have had in RK, we have made new friends, learnt new things, had lots of laughs and a few tears. I’m looking forward to seeing you all in Year One. Have a great Summer! @TemplarsPrimary

@trunarla @joeydotdev Yes, in Europe the ceiling is probably around $150-160k, unless you go into senior management / C-suite roles. But life in general is mostly cheaper than in the US, so I'd say the quality of life is comparable.

@joeydotdev Yeah a lot of them are Europeans or not in the US at least so it’s valid haha

The amount of people in tech I know making over 300k and admitting to me they work <20 hours a week is insane 😅

@wesbos @syntaxfm Been consolidating all my domains with namecheap over the last few years.

We're doing a Domain name registrar roundup for @syntaxfm Where should you / do you register yours? Are there any features you look for, like 2FA, phone support, client access, etc?

@dan_spratling My understanding is that in your use case your probably better off fetching everything in the page.tsx (possibly using react query to avoid prop drilling), but I'd also be interested in different approaches without having to run the api calls synchronously.

Someone teach me how to Next13 properly with lots of data fetching Here's an example I'm currently struggling with 1. Fetch blog root page data 2. Fetch all blog posts 3. Fetch all authors for associated blog posts I thought I was able to fetch data much lower down to avoid prop drilling so blog /page.tsx <- Fetch root data here /BlogList <- Fetch all blog posts here /Author <- Fetch author here All deduped nicely so I only fetch data once and in a logical place But it seems that the most effective way to fetch data is (still) to load it all on blog/page.tsx and prop-drill it down to the components, exactly like pages Loading data lower down, as far as I can tell, slows down requests by preventing you from using Promise.all, and doesn't deduplicate the same requests as I expected (so only something to do on components you want to render after initial render) What am I missing? Any examples solving this would be excellent

Should add that our monthly usage is only around £120