Lauren 近期貼文

ask your bot to email tibo@mail.grokbot.com if you want to send in a bug report!

it won't be long before "have your bot talk to my bot" becomes common! some fun use cases of multiplayer grok bot over email could be: • debugging (you can send my bot bug reports!) • customer support • booking meetings and events • group buys • buying and selling stuff off craigslist what have you used bot mail for?

ban and delete most if not all code comments! agents love copying what already exists. a seemingly harmless comment explaining some temporary workaround is one of the worst viruses you can have in your codebase. like a weed it'll spread quickly as a tool for agents to quickly get their job done. before you know it, your codebase is overrun with hacks and stale comments. just one more workaround bro you can use pstack's /no-comments skill as a weedkiller. it'll seek out useless comments while keeping the ones that actually should exist (like explaining a browser quirk), and figure out how to solve them on a first principles basis here's a prompt you can try asking @bot: create a project agent that uses /poteto-mode to spawn a /swarm to use /no-comments and identify useless code comments we can prune in my repo. come back with a high level plan of which of these workarounds would be best solved by refactoring and which we can straight up delete https://t.co/nqeRdY62ee

if you installed pstack through grok bot or cursor, it updates automatically! x.ai/bot/plugin/9717366

this is now a new skill /in-your-own-words in pstack 0.15.23! extremely useful to ensure that you and your agent are aligned on the goal and that it understands your intent clearly

Don't build alone, apply to join our Grok Bot X Communities https://t.co/1dEvXMU7Su! We have curated group chats for: • GTM • Product • Marketing • Engineering • Recruiting • Design where you can share what you're working on and learn from others using Grok Bot https://t.co/kqbXdx50N7

me vs the reset guy https://t.co/Slpi68fsZA

i love writing. i never let agents write for me. whether it's docs, or tweets, or shitposts, or even prompts (okay maybe that one's harder as agents manage other agents) there's a simple reason for that: i still strongly believe that writing is thinking. it's a skill i hope to never give up. it's also important to me that whatever i say is always authentic, mistakes and all. my favorite posts are the ones that i just full send without any editing i suspect it also helps with prompting. being able to clearly express what i want, and knowing the vocabulary i need to be able to direct my agents does seem to make for more effective usage of agents. in the same way that engineers have an advantage when we prompt agents to write code, because we are intimately familiar with the words that make up the discipline knowing the right word incantations to get an agent to produce a desired goal almost feels like spellcasting. as models get more capable, and that input box looks more and more like a magic box that can output anything, words become the interface between you and the genie there may come a time when we give up the keyboard in exchange for brain-computer interfaces. but until then, i'm writing every word.

it's finally here! one unified sub with incredible value across Grok, Grok Bot, Cursor, and X Premium

also please watch my talk nitter.cf/poteto/status/21020504…

something that keeps bothering me is how some people see slop as something that is happening to them, like they're some kind of helpless bystander powerless to do anything about it excuse me but you are a software engineer, you literally learned how to make sand think and make computers do your bidding?! and now you can't do anything about it? please the 2 things you should know to cut through all the noise: 1. you need to give your agent a way to verify its own work (i just posted about this so won't rehash) 2. your codebase is memory the 2nd is not new either, we have always had lint rules, compilers with good diagnostics and strong type systems, LSPs, etc to help us write better code. there is no difference when agents write the code instead, you just need more of them, and stronger ones. forget rules and skills. you can add those later. yes, your codebase is a form of memory to agents! agents love extending what already exists. so every nit and every annoyance you've ever seen, every mistake and bad pattern you observe from agents, needs to turn into a constraint, or the agents will just keep repeating those same mistakes like a virus in your code. then you keep observing and repeating this process until your codebase is locked down enough that even agents with little context can one shot a high quality PR. an even better direction is to refactor/rewrite your code such that agent anti-patterns become categorically impossible. use type systems to your advantage, use libraries/frameworks that reduce the architectural search space, or heck, create your own framework like we did for grok bot and design high quality primitives and well thought out APIs

found a few smaller bugs also which i am fixing, but the fix in 0.70.2 was the biggest contributor to your desktop client going to sleep

this is fixed and released in 0.70.2! rolling out now

okay now that we're past that tired discussion, let's talk about how we get agents to write more correct code (note: this won't mean the code will be Good, but it should at least work) this is the entrypoint into your most basic agentic loop: verification. it means giving your agent the ability to verify its own work, most commonly by actually running and interacting with it like a real user would. whether your interface is a cli/api/ui/whatever, you want to start here so that your agents can close the loop. if you want you can even have your agents model the problem in TLA+ and attempt to verify if you have things like state machine bugs. the point is to give yourself confidence in the agents' work by them producing some kind of artifact that proves that 1) that the work is correct, 2) that it matches what you intended, and 3) is easier to review than reading the whole PR. most commonly this would be a video and/or screenshots for UI work. everything else like skill packs are really bonus and optional, all you need is a way for your agents to verify their own work to start using them more autonomously. some caveats are that not all domains can be verified easily yet, and that verification is just approximation and can still be wrong. it's no different than trusting that a human actually ran the code they wrote and trusting it so start here!

it's very interesting how many replies i've gotten about maintainability and clean code being still important. i would argue that that is no longer true and we all need to update our priors on what Good Code really means in 2026. clean code has always come at a cost - performance. indirection and making code readable/understandable for a human is not free, it often comes at the cost of worse performance. we have historically been okay with this because of Moore's Law and the fact that most code is not on the hot path. these principles also came from a time where humans maintained code. it made sense to optimize for humans then, but it makes less sense now when agents are already writing all the code. we will in fact probably discover and come up with new principles: principles of agent friendly architecture (i plan to write more thoughts about this soon)

not sure what to use grok bot for? send it a link to this post below (almost a thousand ideas in here!), or tag: @bot read this full thread and suggest ideas for my work and personal life you can help me with

also another interesting post i always come back to ever since @tomocchino shared it with me https://t.co/jFTiJ11byY

except mine of course

tldr all code is slop

pstack is now 10% smaller with no loss in behavior! updates are automatic in grok bot and cursor x.ai/bot/plugin/9717366

codebases have always contained slop. we have always been okay with this because code rarely needs to be perfect, outside of mission critical "hard" (eg embedded) software. swe is a unique form of engineering because you're often building something that constantly evolves and is almost organic - user tastes change, your mental models evolve, and features come and go. admittedly, i and many others who've been coding for a long time were initially (like back in 2024) skeptical that agents would write production code. "but what about all the slop that would enter our beautiful codebase?". well, even before, we had human slop, and there was a lot of it! if we're being truthful, most people call "code i didn't write" slop. the reality is that 99% of people (i include myself in that number) don't even know what Good Code looks like, let alone be capable of writing it. i would propose that Good Code is: • correct • bug free • fast and cost efficient to run it has always been exceedingly difficult and expensive to write truly Good Code, because for the longest time (maybe @bendlang will change that), code was not something you could cheaply and formally guarantee to have all 3 of these properties. this is why writing hard software is much more difficult and expensive, because depending on the use case, you may only get one chance and so you have to be right from the start. but the vast majority of software we use does not need to be Good Code to provide value to users. in fact, it is very likely that most software we use is not formally verifiable! we accepted some bugs in exchange for velocity and progress, so we rely on tests and o11y instead and have adopted a more incremental approach. this is a good thing! agents help us move faster, and if you're open to the idea, are capable of helping us write better code. it won't be Good Code (that is still expensive), but it is likely to be much better on average at scale. the new craft of swe is to figure out how to do this. it's your job now! if your productivity with and without agents is not significantly different, you're doing something wrong. but it's not too late to embrace it and use it as an opportunity to learn a whole new skill tree

@bot tell poteto to send this to my pstack project and add a new skill called /ketchup

i have so many cursor Projects running in parallel (16 right now) that my most used prompt has become "/bro catch me up on everything since my last message, and if there are any action items for me give me enough context (exec summary) to make a call"

wow @NICKIMINAJ uses grok bot!

san francisco ikigai

try mentioning @bot and ask it to do the same!

yeah i'll take 5.5 opus

he's a 10 but he says opus like gpus

fish dead gill issue

@bot remind me about this post in 2047

help im turning into @threepointone

on a related note, there's been some chatter recently about software engineering skills (eg the ruby/rust/elixir drama). i'm a bit torn because while i do feel like they're software engineering principles and patterns are still important, at the same time i wonder if there will come a point in time when they just won't matter anymore. not that they're no longer useful, but that your own intuition can fill in the gaps as you use agents in an intuitive sense rather than knowing explicitly what they're doing if that doesn't make sense, the analogy i have is the first iphone. 20 years ago you had to be a professional with expensive equipment, now just with a phone and some creativity you can film content that's compelling to a new audience. i don't know if there's a term for this but i want to call it "skill compression". where what used to be gatekept and prohibitive to experts becomes accessible to a new audience of creators with a whole new meta. the details have sort of faded away and now the craft is not in knowing the equipment and how to use it, but how you use it creatively we're going to see a whole new generation of builders who've never seen or written a line of code build incredible things

bonus: show me your factorio/satisfactory save file

i feel like swe interviews could probably collapse into just 2 technical rounds: • system design (how well can you articulate your ideas, do you actually know how to engineer something) • onsite project to build a real thing with agents (can you translate your intent into high quality outcomes) everything else we used to ask is no longer necessary

if you can't tag @bot, sign into grok.com with your Grok Bot email, then link your X account

ask your bot, or tag @bot on X to set this up for you!

if you’re new to coding, download my bot and ask it: “make me an engineer bot that uses cloud agents and pstack for coding work. it should make a project to group together related tasks” https://t.co/AZIdKxbgFS

try coding with Grok Bot!