Chris Frantz
@frantzfries
@loops
This is all we do: 1. Talk to existing users and potential new users 2. Build new feature for new users 3. Fix bugs in new feature to retain new users 4. Polish existing features for existing users 5. Share updates on social and via email Then repeat. Every week. For a decade.
wild how we just rolled up everything into AWS after a couple of years
first engineering post is out, flowchart is a banger
Migrating in production is always nerve-wracking Here's the full breakdown of how we did it while maintaining zero downtime in production
The team @loops has been working hard to migrate our infra to @awscloud. We consolidated from 9 vendors down to 3 while preserving uptime. Hope this deep dive is useful👇 loops.so/engineering-bl…
the ai generated content baseline across code, video, images is awful or pretty good but baseline competency to create is now zero without competency you don’t develop taste, so most posted ai gen is slop jobs start to really disappear once the baseline shifts to fine
post a job on LinkedIn and you too can receive job applications from North Korean state actors and crypto scams!
LinkedIn is now processing 11,000 job application submissions per minute—a 45% surge from last year, per NYT
Always felt like the logo strips on landing pages were low trust Does Google _actually_ use your product? All of logos are active paying users, so we added the paid conversion date and will be linking to customer stories for each one as we knock them out
lol guess that's what happens when you own the distribution channel
reading through the latest draft on the engineering blog and we're like the grim reaper of queue management services
