New York, USA
Joined April 2018
- Tweets20.2K
- Following941
- Followers6K
- Likes27.3K
Pato retweeted
I worked on Firebase for 12 years. I built the tool I think it desperately needs.
pyric.dev - A disposable Firebase environment with all the tools to generate complex Security Rules and data structures.
No project, no config, or even a account. Point it at your agent and let it cook.
ALT pyric.dev - Firebase tooling for the agent era. Give agents the freedom to build without production consequences.
Pato retweeted
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.
Pato retweeted
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/…
ALT import { stitch } from "@google/stitch-sdk" const design = await stitch.project("id").generate(` A GitHub repo landing page for an SDK that can generate designs from natural language. `) const html = await design.getHtml() const imageUrl = await design.getImage()
Pato retweeted
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
Pato retweeted
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. 🥰
The Freelancer's Success Webinar 2.0 is here already 💃💃
In December, I held the first edition of this webinar for free and invited 4 experts to share so much valuable knowledge with us.
The sessions spanned across Upwork usage, Fiver Mastery, Remote work navigation, how to land freelance opportunities by optimizing your LinkedIn and CV'S as well. You can check quotes for the excerpts and start practicing already. I have testimonials from attendees 💪
This February, I will be hosting the second edition of this webinar with my Queen and Mentor @TheQueenArit on the 15th.
If you know Mama, you will know #5000 isn't worth the value you will get for two days but she loves us a lot. If you don't know Mama, Check the 2nd slide for more Info.
So go ahead, register, spread the word and let's start winning in 2026 already.
Kindly check out the flyer for what you will be learning 🙌
Here's the link to register: [nestuge.com/tncy9rgni]
#TheGlobalCommunity
Pato retweeted
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.
Pato retweeted
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…
Pato retweeted
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.
We're extremely excited to introduce @Imagine_dev_
The AI builder with @Appwrite Cloud *built-in*.
Build something real.
Pato retweeted
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."
Pato retweeted
Check out our curriculum github.com/microsoft/mcp-for… especially chapter 3 that has many sub chapters
Pato retweeted
A casi 3 días de la #miduConf 2024 🎉
Este año tengo la suerte de ser speaker junto a gente muy 🔝 de la comunidad, como mi peligrosa fav @carmenansio, @teffcode, @DotCSV, @S4vitar, @devpato, entre otros.
Os daré un poco la turra sobre Web Extensions 🧩
miduconf.com/
Pato retweeted
I have now crossed over 22 thousand learners on LinkedIn. 22,000 individuals have had their lives directly impacted by my work globally.
GOALS
Pato retweeted
Not enough people are following the creator of @ApiMocking (MSW). He's got great things to share (and even more coming in 2024). You don't want to miss it! Follow @kettanaito 👈
Pato retweeted
I gave a presentation about this at work about how we waste time in countless meetings.
Things we have done to reduce the # of meetings we have and shrink the time for ones we keep:
1. Require an agenda for every meeting scheduled. No agenda, no attend-a.
2. Circulate the agenda before the meeting is scheduled (attach it to a calendar invite) - you might find your items can be answered async.
3. For the meetings you do keep, spend the first 5 minutes reading over the agenda and allow people to add answers or comments.
4. Anytime someone asks you to “hop on a quick call” ask them to write out their question (preferably in a document) so you can answer them properly. In doing so, you also created a piece of documentation that can be referenced to later.
Over time you will find your team move towards async communication (if it goes well!)
It’s worked for us
3 reasons why meetings are especially bad for software engineers:
1. Writing code requires deep focus - It takes hours of continued focus to make any meaningful progress
2. Context switching is expensive - It takes some fixed amount of time to start writing code. Each time you switch you pay that cost
3. Fragments your time - Meetings chunk up your calendar into smaller, useless fragments of time that aren't as useful for making progress
Not to mention that many meetings aren't even necessary. Have you ever attended a meeting only to realize it wasn't worth the time?
