Pull the latest changes from main into your coding prototype branch after a PR is merged
Manish recommends pulling the latest changes from main into your coding prototype branch after a PR is merged, so your prototype stays current.
42,607 results · Most relevant
Manish recommends pulling the latest changes from main into your coding prototype branch after a PR is merged, so your prototype stays current.
Manish recommends testing code prototypes on a mobile phone in a responsive way: mirror the code layer running on your canvas to your phone, where it runs responsively and lets you interact like a real app — zooming, panning, going into details and map view — to really feel the prototype before making a decision.
Sam recommends that when a design system has complex interactions — like when a search should fire off during typing — you document all the different states of the input field as separate frames before creating a code layer.
Manish recommends going back to GitHub to check that the PR was created, then using squash and merge after confirming you're happy with the changes.
Manish recommends asking the agent to clone a repository — from GitHub or by providing any Git URL — to bring existing code into code layers.
Will Brown recommends collecting traces, reviewing proposed experiments every night, looking at flagged issues, and kicking off a training run for the night.
Brown recommends collecting traces, then every night reviewing the proposed experiment, looking at flagged issues, and kicking off a training run for the night. He also endorses using idle inference capacity at night — when employees are not using agents as much — for training instead of serving.
Brown recommends having a big model and a small model do the same task, then judging whether the small model was as good as the big model; if so, that becomes data for routing that kind of task to the small model more. For tasks with clear labels and a right answer, there is an opportunity for a human or another agent to give feedback.
Will Brown recommends that when a big model and a small model do the same task, you judge whether the small model was as good as the big model, and if so, start routing to the small model more.
Go look at the graph of how fast your company is growing — that same curve is the graph of how fast your job is growing, how fast everything around you is changing, and how fast you need to grow.
Robert Greene recommends doing the exercises at the end of each chapter of The Law of the Sublime to bring the ideas into your daily experience, and incorporating the book's ideas into daily life rather than treating it as an academic book about the sublime and the brain. He frames the book as trying to open you up to the strangeness of the world we inhabit and to alter your experience of life itself at the roots of your consciousness by expanding your circle of perception. He adds that both daily micro practices and large transformative experiences have real value for accessing the sublime.
hedged
Robert Greene recommends putting the phone in a drawer to resist its temptation, acknowledging the addiction is real.
Robert Greene recommends going to the desert and walking through it, feeling the emptiness, silence, and lack of vegetation, letting the environment inhabit you so your senses awaken; going to a mountain or swimming in the ocean; or simply sitting in your own backyard and encountering it as he did for his Sublime book. He says your senses are waiting to be awakened — it is not dead, it wants to be awakened, and it can happen at any moment.
Commercial context: The creator describes this as their own product.
Andrew Huberman endorses slowing down your temporal frame rate — for example, stopping to watch your espresso pour with immense temporal detail, collecting more information — while noting you cannot maintain high temporal detail all day because you won't get anything else done.
Robert Greene recommends keeping your phone out of the room when you work and when you relate to other people, and putting the phone in the drawer when it tempts you, noting you get better and better at it over time. He also observes that even people who keep the phone away feel temptation and understand the addiction, so expect a slightly hypocritical side to yourself.
Robert Greene recommends looking at ordinary objects like a cup as they are — their weird shape, funny color, handle, material — instead of only their use value, and noticing the quasi-miracles in your day-to-day life, like your body healing, rather than only seeking extraordinary things.
Robby Stein advises designing the AI search box experience so it feels like the brand (Google) but signals that AI is inside helping the user, describing it as an upgrade that felt like AI is here.
Robby Stein recommends building an AI agent tool that uses your product as a user would — type a question, ask a follow-up, record the experience, screenshot it, and evaluate against a comprehensive rubric — sharing that he actually built such a tool to look at all of the potential questions they might ask.
hedged
Make the product interface have zero resistance: no credit cards, very fast signup, super quick value, and super clear limits and upgrade paths.
When comparing themselves to competitors in listicles, Ajelix says something like: ChatGPT and Claude are very good for general use, but we are specifically good for business users, for those who need to create reports or administrative tasks.
Choose sources → to get a library of your own and a daily brief.