Pedro Marques

1.5K posts

Pedro Marques banner
Pedro Marques

Pedro Marques

@marques_ph

Head of Design @Footprint_HQ. Be curious, not judgmental.

Remote Katılım Haziran 2011
1.4K Takip Edilen790 Takipçiler
Pedro Marques retweetledi
Boris Cherny
Boris Cherny@bcherny·
Opus 4.7 uses more thinking tokens, so we've increased rate limits for all subscribers to make up for it. Enjoy!
English
1.2K
936
22.2K
1.3M
Pedro Marques
Pedro Marques@marques_ph·
Nobody really talks about this, but AI image tools are wildly inconsistent. You craft a prompt, get something gorgeous, and then when you return the next day... boom, totally different look. Colors shift, proportions change, the whole mood feels off. Suddenly, your brand just slips away between sessions. That’s why @rafaelmotta021 and I started Illux as a side project: to fix this mess. Here’s how it works: you upload a handful of reference images to your project. Our system (we’re using Claude’s vision tech) goes over each one, checking line weight, color vibes, rendering style, and all the little compositional quirks. Then, it pulls everything together into a style guide just for your project. And from then on, any illustration you make taps into that guide. No need to re-prompt or copy-paste style details. Whether it’s today or months down the line, you get visuals that actually stay true to your brand. Come check it out! illux.app
English
0
0
1
205
Pedro Marques
Pedro Marques@marques_ph·
@Ryan_Drumwright Yeah, absolutely. In fact, every designer can become a design engineer now. There are literally no more boundaries between design and engineering. Designers who leverage Claude Code (and similar tools) will thrive.
English
1
0
1
29
Ryan Drumwright
Ryan Drumwright@Ryan_Drumwright·
@marques_ph #4 is especially interesting. It makes me think about how Design Engineers are so hot these days. Are you seeing any growth in this new role?
English
1
0
1
12
Pedro Marques
Pedro Marques@marques_ph·
Fascinating.
Lenny Rachitsky@lennysan

My biggest takeaways from @bcherny: 1. Coding is now “solved” for most use cases. Boris hasn’t written a single line of code by hand since November, with 100% of his work now authored by Claude Code. At the same time, he remains one of the most productive engineers at Anthropic, shipping 10 to 30 pull requests daily while leading the team. 2. Anthropic has seen a 200% increase in engineer productivity since adopting Claude Code. As Boris notes, “Back at Meta, with hundreds of engineers working on productivity, we’d see gains of a few percentage points in a year. Now we’re seeing hundreds of percentage points.” 3. AI is moving beyond writing code to generating ideas. “Claude is starting to come up with ideas. It’s looking through feedback, bug reports, and telemetry, then suggesting features to ship.” 4. The next roles to be transformed are those adjacent to engineering. Product managers, designers, and data scientists will see similar transformations as agentic AI expands beyond coding. “Any kind of job where you use computer tools will be next.” 5. Build for the model six months from now, not today. One of Boris’s key principles is to design products for future AI capabilities, not current ones. “It’s going to be uncomfortable because your product-market fit won’t be very good for the first six months. But when that model comes out, you’ll hit the ground running.” 6. Watch for “latent demand.” Claude Code was built by observing what people were already trying to do, and then making it easier. Cowork emerged when they noticed people using Claude Code for non-coding tasks like analyzing MRIs or recovering wedding photos from corrupted drives. 7. Don’t optimize for token cost. Boris advises companies to give engineers unlimited tokens during experimentation phases. “At small scale, the token cost is still relatively low compared to their salary. If an idea works and scales, that’s when you optimize it.” 8. Underfund headcount on purpose. When Boris puts one engineer on a project, they’re forced to let AI do more of the work. Constraint drives creative use of AI tooling, not just faster typing. 9. The most successful people in the future will be generalists. “Try to be a generalist more than you have in the past. Some of the most effective engineers cross over disciplines. The people who will be rewarded most won’t just be AI-native—they’ll be curious generalists who can think about the broader problem they’re solving.” 10. Always use the most capable model, not the cheapest. A less intelligent model often burns more tokens correcting mistakes than a smarter one spends getting it right the first time. Boris runs maximum effort on Opus 4.6 for everything. Here's the full conversation: youtube.com/watch?v=We7BZV…

English
1
0
2
246
Pedro Marques
Pedro Marques@marques_ph·
@claudeai dramatically changed the way I work (for the better). Designers, jump in. It makes you feel like anything is possible. The boundaries are (literally and figuratively) gone. Thank me later ❤️
English
0
0
0
29
Ben South
Ben South@bnj·
Introducing @variantui Enter an idea and get endless (beautiful) designs as you scroll No canvas, no skills or MCP, no constant prompting Reply if you'd like 200 free designs to give it try
English
2.2K
272
4.2K
1.1M
Pedro Marques retweetledi
Flamengo
Flamengo@Flamengo·
Conquistamos o Brasil. Conquistamos a América. Agora, queremos o mundo mais uma vez. Seremos onze em campo e 45 milhões espalhados por cada canto desse planeta. Amanhã é dia de fazer história mais uma vez. Foi assim em dezembro de 81. Assim será em dezembro de 25. VAMOS, FLAMENGO!
Português
294
4.9K
23.8K
378.3K
Pedro Marques retweetledi
David Hill
David Hill@iamdavidhill·
the entire team must care about design not just the designer
English
102
239
2.2K
160.1K
lucas gelfond
lucas gelfond@gucaslelfond·
When I first joined @footprint_hq in May of 2023 I was a wide-eyed Brown junior, eager to jump into startups and get my hands dirty. My biggest motivator was working with great people, and when I got @EliWachs email (through the Neo portfolio / @apartovi) I was intrigued by a pitch about “rebuilding identity on the internet.” We immediately hit it off, and as I got to know more of the team I noticed something rare: insanely talented, low ego, kind people, who loved working together and felt real pride in the thing they built. @AlexGrinman sealed the deal; this was a team that loved engineering and sent around cool cryptography papers out of interest. It’s been a wild ride; we’ve scaled from hundreds of dollars and a few design partners to millions in revenue, supporting not only startups but large enterprises and public companies. I remember my first day, when my manager Rafa told me to “take the time to make it really nice.” Over time it became clear this was an animating principle of Footprint; for @marques_ph to design perfect loading states or @clodoan to perfect motion graphics. Eli would always tell us success and delight came in perfecting details, stuff smart customers noticed, and clearly it worked. With all of this new scale, the team lost none of its dedication to quality. Rafa, @belce_dogru, @elliottvforde, and Ethan always pushed me hard in code review, to build simple, ideal abstractions, to write code we didn’t dread maintaining. I remember so many moments of this quality obsession: Rodrigo's massive OpenAPI migration; @DaveArgoff's painstaking work on undocumented vendor APIs; Amanda at all hours of the day squashing inbound UI bugs. I worked on a lot of things I’m proud of; our new “onboarding engine,” a giant AI SEO push (shoutout to @peter_sweeney0 my partner in crime here), Footprint “Wrapped,” internal access control, tenant onboarding, and so much more. I loved writing Rust, building APIs for our internal agent Percy, refining our onboarding engine, and revamping our audit logs. Footprint has no PMs, and all engineers own product, and some of our work was more subtle, letting customer feedback inform engineering. As the team grew, I loved also meeting a whole new team on sales, seeing @suryawashere's crafty sourcing automations and @Geronimo_Nores and Peter's incredible ability to set our customers up right. I have many others to thank: Keagen for his hard-earned fraud wisdom, Bruno for early mornings combing through Datadog, and Eric, Erik, Julian, and Noah for jumping in so fast. My last day is tomorrow, and I leave as bullish as ever. I’m taking a few weeks off and then have some exciting news to share. In any case: I feel immensely lucky to have begun my career at Footprint, to learn from people I greatly admired, to have people who bet on a new grad and taught me to build software we’re proud to give to other people.
English
9
0
49
3.4K
Pedro Marques retweetledi
Karri Saarinen
Karri Saarinen@karrisaarinen·
Having been an employee at a startup in the past, I found the 90-day option exercise window very unfair. There was rarely guidance on early exercise, or it wasn't allowed, tenders weren't including past employees and there wasn't much transparency on the business overall. With Linear, I wanted to do better. From the early days, we’ve offered a 10-year extended exercise window, early exercise in the US, and as much transparency as possible about the performance of the business, starting from the moment we present a job offer. And now, offering liquidity is another important step in giving our employees more flexibility. More here: linear.app/now/giving-our…
English
10
8
209
18K
Pedro Marques
Pedro Marques@marques_ph·
This is an incredible initiative, and every country should be doing the same tbh. Most government sites worldwide are outdated, clunky, and borderline unusable. Hopefully the US can set the standard and lead the way. I’m sure other countries will follow.
Joe Gebbia@jgebbia

My directive is to update today’s government services to be as satisfying to use as the Apple Store: beautifully designed, great user experience, run on modern software. An experience that projects a level of excellence for our nation, and makes life less complicated for everyday Americans. I’d like to thank President Trump and his administration for creating this vision, and supporting America by Design (@americabydesign). I will do my best to make the U.S. the most beautiful, and useable, country in the digital world.  If you’re interested in joining me at the newly established National Design Studio (@NDStudio) on this ambitious mandate, please reach out with a link to your work. Thank you for your attention to the details.

English
0
0
3
348
Stijn Feijen
Stijn Feijen@spwfeijen·
This AI-powered TikTok page made $1,623,177 in 93 days. No filming. No cooking. No face. Just: - 200+ AI recipe videos/month - Faceless voiceovers + AI food images - $25 cookbooks sold on autopilot - 55M+ views | Dozens of 1M+ videos It looks like a real food creator — but it’s 100% AI. Want the full system comment “Page” & I’ll send it (Must be following)
Stijn Feijen tweet media
English
1.3K
156
1.4K
192.1K
Pedro Marques retweetledi
orkward ☄︎
orkward ☄︎@0xOrkward·
hot take: designers often feel like they have to defend every single choice they make, as if they're constantly on trial. that's because design is so visual—anyone can glance at it and throw out opinions, even if those opinions are vague or come from someone without much expertise. for instance, a non-designer might casually say, "this color feels off," without backing it up or offering a real alternative. the bar for giving feedback is incredibly low; you don't need deep knowledge to chime in. now, compare that to engineering: folks don't usually drop random technical suggestions unless they actually understand the code. instead, they'd point out a specific issue, like "clicking this button triggers an error." it's straightforward and functional, not just a gut reaction like "this code seems weird." but here's where things get imbalanced: when someone hits a designer with that low-effort feedback, the expectation for the designer's reply is surprisingly high. if someone asks, "why this layout here?" answering "after a few iterations this one felt right" rarely satisfies them—they want a full breakdown of ux laws and design thinking with as many jargons as you can blurt out. early in your career, or even later, articulating that intuition can be tough and sometimes there isn't any to articulate in the first place. it's built from experience, patterns you've absorbed, and subtle principles of what works visually. don't doubt it; it's likely spot on, even if the words aren't there yet. this setup can make design feel draining, turning teamwork into a constant justification session rather than pure creation. yet, here's the key: designers don't need a defense for every little element. design isn't something that requires endless justification—it's the bridge that gets a user from point a to point b, all while deeply prioritizing their experience and convenience. trust the process and never let shallow feedback shake your core confidence. ps: using above as a justification for poor design is definitely a skill issue but you get the gist of it.
English
60
181
1.3K
109.1K
Jeddi
Jeddi@antinertia·
i have a Tiktok AI farm making 10M views while i sleep here are the steps - create 200 ai ugc with arcads.ai - distribute on 20 accounts over 5 days - all of them get hundreds views - that’s a guaranteed 100,000 views - 2% will go viral and get 1M+ views it's all on autopilot comment "ai ugc farm" to get the full guide
English
1K
105
1.2K
178.6K