Lucas Sahdo retweeted
Need help from the builders and PHP community! ๐
elephc is the first real PHP-to-native compiler (no VM, no runtime).
Weโre currently at ~250 stars and Iโd love to reach 500 as a milestone.
If you find the project interesting, a star would mean a lot and help more people discover it.
โ github.com/illegalstudio/eleโฆ
What do you think, is native PHP compilation exciting?
Hรก algumas semanas publiquei um vรญdeo sobre DDD estratรฉgico e tudo o que vocรช nรฃo ouvio falar sobre Domain Driven Design by the book. Para meus seguidores dessa rede segue youtu.be/FKNrpyPqK48?si=NYkCโฆ
Sรกbado dia 16/05 eu tive a oportunidade de palestrar presencialmente sobre um tema que gosto muito e uso todos os dias nos projetos que atuo no mercado. Domain Driven Design. Minha mensagem tem sido constante e previsรญvel: Pecisamos modelar domรญnio de forma mais estratรฉgica!
Changing an old #Laravel project here. Iโm renaming the persistence layer from #Repository to #DAO, since repos should be aggregate centric, right? And this one clearly follows more of a Laravel way style. For now: โActionโ pattern, anemic domain, and DAO baby, cheers! ๐บ
If your #Repository is just a hashtag#proxy to the #ORM, you're missing the point.
Repository is a bridge between your hashtag#domain and your #infrastructure.
The whole idea is that your business logic doesn't know how data is stored.
New video is out.
Lucas Sahdo retweeted
the lessons I've learned scaling my startups:
> 90%+ of users pick google sign in. just make it the default.
> strip all formatting from your emails. send from a real name, not "company team." watch your open rates jump.
> add "how did you hear about us?" to onboarding. makes marketing 10x easier.
> 99% of people sliding into your dms with "opportunities" are wasting your time. protect your calendar.
> creator sponsorships cost less than ads but eat more time. pick based on what you have more of.
> building a good product is just relentlessly asking "what does my user actually want" and doing that.
> copycats show up the moment you get traction. they'll clone everything. they still won't catch you.
> i couldn't build something good if i wasn't using it daily.
> always check logs right after pushing updates.
> bugs are fine. slow fixes aren't.
> people notice good ui/ux design even if they can't explain why.
> first 10 paying customers are harder than the next 100.
> always refund people who ask. not worth the energy or the bad review. give them 2 months free too.
> marketing is just running experiments fast. steal from what works for similar products.
> cheap accountants cost more in the long run.
> users will hop on calls way more than you'd expect. these conversations are cheat codes.
> strong testimonials let customers sell for you.
> you won't have a "pmf moment." only way to know is when people tell their friends about your product (word of mouth)
> even when things are going well you'll have days where you think it's all falling apart. it's not. keep building.
And then:
๐ฎ๐ฌ๐ญ๐ฐ: ๐๐ฎ๐ฐ๐ฒ๐ฏ๐ผ๐ผ๐ธ ๐ฟ๐ฒ๐น๐ฒ๐ฎ๐๐ฒ๐ ๐๐ฎ๐ฐ๐ธ
๐ฎ๐ฌ๐ญ๐ฒ: ๐ฆ๐น๐ฎ๐ฐ๐ธ ๐บ๐ถ๐ด๐ฟ๐ฎ๐๐ฒ๐ ๐๐ผ ๐๐๐ฉ๐ ๐ฎ๐ฌ๐ญ๐ด: ๐ฅ๐ผ๐ฎ๐ฑ๐ฅ๐๐ป๐ป๐ฒ๐ฟ ๐ฟ๐ฒ๐น๐ฒ๐ฎ๐๐ฒ๐ฑ ๐ฎ๐ฌ๐ฎ๐ฎ: ๐๐ฟ๐ฎ๐ป๐ธ๐ฒ๐ป๐ฃ๐๐ฃ ๐ฟ๐ฒ๐น๐ฒ๐ฎ๐๐ฒ๐ฑ
Today, if you're starting fresh and need high-performance #PHP, you have great options: Swoole, FrankenPHP, RoadRunner. But back then? These companies had to build their own paths...
Why Facebook, Slack, and ManyChat didn't choose Swoole, FrankenPHP, or RoadRunner to solve their performance problems with #PHP back there?
The way I see it, the simple answer: ๐ง๐ถ๐บ๐ถ๐ป๐ด.+
Why I think that? Here's when each solution became mature:
๐ฎ๐ฌ๐ญ๐ฌ: ๐๐ฎ๐ฐ๐ฒ๐ฏ๐ผ๐ผ๐ธ ๐ผ๐ฝ๐ฒ๐ป-๐๐ผ๐๐ฟ๐ฐ๐ฒ๐ ๐๐ถ๐ฝ๐๐ผ๐ฝ
๐ฎ๐ฌ๐ญ๐ญ: ๐๐ฎ๐ฐ๐ฒ๐ฏ๐ผ๐ผ๐ธ ๐ฎ๐ป๐ป๐ผ๐๐ป๐ฐ๐ฒ๐ ๐๐๐ฉ๐
๐ฎ๐ฌ๐ญ๐ฎ: ๐ฆ๐๐ผ๐ผ๐น๐ฒ ๐ฑ๐ฒ๐๐ฒ๐น๐ผ๐ฝ๐บ๐ฒ๐ป๐ ๐ฏ๐ฒ๐ด๐ถ๐ป๐ (๐ถ๐ป ๐๐ต๐ถ๐ป๐ฎ)










