What would be the output ? This is a Google interview question on #Javascript

If you want to get hired, open the screen recorder on your computer and create a short, tailored intro / pitch video to the company you want to get an interview with. DM this video along with a short introduction and link to your 1 page resume to someone in the company responsible for the role you are hiring for. Most importantly, only do this for roles you actually think you’re capable of. It will work 1,000x better than this slop.

Introducing the Stitch SDK Yes. You can program design now. I've been dreaming of shipping this for so long because it's just so much fun to use. I welcome all the stars ⭐️ github.com/google-labs-code/…

Unpopular Opinion: Most vibe coders have spent more money on AI credits than they will ever make from vibe coded apps or projects.

If you've wondered what your LLM is actually sending, Sherlock is a nice tool. It sits in the middle, shows you every request live, and saves it all as markdown. Also, watching your tokens tick up in real-time is oddly satisfying. github.com/jmuncor/sherlock

I’m honored to be speaking at this power-packed event! My session will be very hands-on; be sure to bring your jotter and pen! Thank you @theglobalmarvie for the opportunity. 🥰

"WE are developer zero" @cassidoo on Developer Relations teams! 🤯

Open source isn't dying because of AI. It's dying because we all fucking suck. Users. Maintainers. The whole ecosystem. All of us. We fucking suck as users. We use OSS to do our jobs. To build products. To make money. Our employers depend on it. Our startups run on it. But the second a maintainer mentions compensation? We lose our fucking minds. "It should be free." "That's not the open source way." Meanwhile we're extracting value from someone's unpaid labor every single day. We file issues like we paid for a support contract. We demand timelines. We get snippy when our bug isn't the priority. We're not customers. We're guests. Start acting like it. We fucking suck as maintainers. We wanted the GitHub stars. The conference talks. The Twitter followers. We wanted to be the person who "owns" that thing everyone depends on. But now people actually depend on it and we're annoyed. "Talk is cheap, show me the code." So someone does. They spend hours on a PR. We ignore it for months. Close it with no explanation. Or we screenshot their issue and mock them publicly for not reading our minds about what we actually wanted. We invited contributions then punished people for contributing. We don't want to maintain projects. We want to be admired for maintaining them. Not the same thing. We suck at this together. Both sides want the benefits without the responsibilities. As users we want free, maintained, high quality software but won't contribute a damn thing. Not money. Not code. Not even basic respect. As maintainers we want the status of running critical infrastructure but won't communicate, won't collaborate, won't treat people like humans. We all know this shit doesn't work. And yet here we are. Okay Josh, what do you suggest then? If we use OSS and profit from it, we contribute something. Anything. Money, docs, triage, kindness. We stop expecting infinite free labor. If we maintain OSS and we're burnt out, we say so. Archive it. Hand it off. Ghosting is worse than walking away. And if we can't treat each other with basic respect? We don't get to participate. Full stop. Open source runs on people. On us. None of us owe each other a god damn thing. But we could choose to stop being assholes and do better anyway.

In today’s AI world, why would you hire a junior developer instead of making your team use more Claude or any other LLM?

He preparado un checklist práctico para detectar qué partes de tu trabajo como developer ya deberías estar automatizando con IA. Sin teoría. Trabajo real. 👉 Descárgalo aquí: labs-resources.dominicode.co…

We've officially launched @imagine_dev_ . I'd love to know any feedback from yall. If you have a few minutes to test it out, would also love to see what you build and get your feedback. :D DMs are open.

Joining a new team? Your #1 job is to ramp up fast. If you’re joining as a leader, that responsibility is 10x. The team cannot afford to "dumb things down" or pause execution to spoon-feed you context just so you can play along. Do the homework. Earn your seat. The most critical KPI for a new leader is "Time to Context."

Hi fam! Just created a BlueSky account. Follow me there: bsky.app/profile/devpato.bsk…

Check out our curriculum github.com/microsoft/mcp-for… especially chapter 3 that has many sub chapters