Good luck with the launch
06.09.2025 10:10
👍 4
🔁 0
💬 1
📌 0
Good luck with the launch
Super cool 😲
Boom! Many congrats 🙌
Also “is it compliment or complement?” 8 times 🤦♂️
When exploring my Google Takeout data I discovered that I’ve searched “how to reheat rice in the microwave” 11 times in 11 years… my brain refuses to commit the answer to memory
An excellent point - definitely overlooked.
Underrated aspect of having kids. When they use your YouTube profile to watch some vids, your subsequent recommendations for the next week are epic… worlds biggest container ships ✅, triceratops vs 3 tyrannosaurus ✅, paper aeroplane tutorials ✅. Yes please!!
Super cool! Many congrats
Spot on
Bet its memory usage is even worse
That’s a very fair point, the customer selection piece in particular resonates when operating within a niche, you definitely live with a concern around reputational risk and the idea that you need to get it right first time or you’ve blown your chance.
Always wondered how to introduce and sign off the letter though “To whom it may concern…”
Always struggled with the “so ship today” one… maybe just war torn from the QA process and regression testing cycles
The 80’s, 90’s, 00’s, ‘10’s called… they want their potential solution to the housing crisis back
Massive shout out to the Lego product team on this one - what a line up!
Excellent. After his comedic performance in Extras, nobody is more deserving of the Frank Drebin role than Liam Neeson!
If [design] = [art] + [constraint], then
[strategy] = [business design] = [inspiration] + [constraint].
The decisions you make, both the + and - consequences of that, are the constraints.
These are often called enabling constraints.
Articulate, and embrace them. Here is how:
Feel like the modern day version of this needs to account for the bots that make up 75% of the pile on
If you are planning to release in Europe a big #AI model any time soon, today is an important day…
Zero ill feeling from the anyone at the club (I’d assume!) for him taking the decision. Forever a Spurs legend, and leaving on a high.
Obscure celebrity reference, I’m here for it!
It’s 100% true
Love this!
Just published a new article! 👇🏾
Your company will stop growing sooner than you think. The "Max MRR" metric predicts revenue plateaus based on churn and new revenue.
Many thanks for spreading the love with ❤️ and 🔁!
Cool to see Mimoto featured in the Observer this week.
Just a few scrolls down from the guy using ChatGPT for, er… size advice.
Not quite the context I imagined, but hey - all publicity, right? 😅
observer.co.uk/style/featur...
2018: “Our token will revolutionize food distribution in post-conflict regions. Here’s our white paper.”
2025: “It’s a dog. On fire. With sunglasses.”
Send ETH.
Haha nice work, enjoyed it!! Feel there’s probably a Christmas cracker sequel option for this.
r/vibecoding u/davidlover • 2d Why does Al complicate things so much? Join I am currently using Claude Code to help me develop a mobile app (I have no swift experience) while I handle the backend. Every time I ask it to build me a new feature with plan mode, it comes up with an elaborate scheme that involves re-writing things, building new views, models, etc. Even without knowing swift / Apple development, I can see that half the stuff it is proposing is unnecessarily complex. For example, I am currently implementing pagination for data in the analytics page of my app. I say: "The skeleton animation works good on the page when awaiting the initial data fetch, but for pagination it just deletes the info cards and then replaces them with the new data (looks bad). I just want to have the existing skeletons show up for that async fetch period" To this Claude tried to get a pagination manager with an integrated date period and search function that also manages the loading state and animations. All it needed to do was reuse the existing code it wrote that manages the skeletons animations and have them display during the fetch. This happens so much it is frustrating (even after adding multiple lines in claude.md about overcomplication).
You're so close dude. You are nearly there
I think "context engineering" is going to stick - unlike "prompt engineering" it has an inferred definition that's much closer to the intended meaning, which is to carefully and skillfully construct the right context to get great results from LLMs simonwillison.net/2025/Jun/27/...