naj

370 posts

naj banner
naj

naj

@naz_09

founder of https://t.co/SOrnOZ2Gbb - Deploy OpenClaw agents to web and WhatsApp instantly. Ask me anything! https://t.co/iLGHHMYfmJ

Katılım Mayıs 2011
18 Takip Edilen13 Takipçiler
naj
naj@naz_09·
run 8LrnujUyqwBQQMNdagyXpDLUunGB91uFsCZURzBbpump
Indonesia
0
0
0
3
naj
naj@naz_09·
run
QST
0
0
0
3
naj retweetledi
ThePrimeagen
ThePrimeagen@ThePrimeagen·
I have been thinking about this a lot. I think for a great many of engineers, the ones who did it because they loved it only to discover that money was in fact at the end of the rainbow found both the journey and the destination satisfying. In fact, I think I can argue with authority that the destination was only satisfying as the journey was difficult. The hard-fought evenings spent toiling away on an idea and codebase that slowly gives way to your vision was an incredible experience. The group of people that fell into this category of hard-fought journey and destination we will call them tinkerers. One thing tinkerers have always hated is the already known problems. The journey is clear as day. The obstacles minor inconveniences. Its purely a matter of typing the solution into the terminal. This is also why I think so many of this group goes out and does open source, or starts companies. Work largely falls into this category with few exceptions. From this reason is why I largely find UI work soul sucking. I know the solution, its a matter of just looking up the details and putting it into my editor. yawn. CSS, flex box this, grid that, put the tailwind classes in the bag. To me, the LLM software world is with little to no journey and discovery. Its more of simply taking my high level idea and just formulating it into testable, atomic chunks that can be verified. I have traded my favorite part, discovery and raw creation, with itemized list of TODOs and patience and "No Mistakes." To this, every morning from 6 to 9 I simply just hand code every thin. even UI things. It is because I want journey and discovery and raw creation. Maybe one day comes and its just so futile that I stop this. But for now, I still see such great value in this. I see such better thought through products. Because slowing down and truly thinking through everything. The architecture, the design, everything is an expression of discovery and creation. And I love it. I am sure there will come a day, maybe even in the next 6 months where I change my mind. For now, I pursue the love of the game intentionally. I do also believe that there exists people who get the same joy I got from building with tears and sweat by prompting LLMs. I am positive of it. I just don't understand how. But people love UI work. I also don't understand that.
Adam@adamdotdev

Programming was deeply satisfying work to me. Work for hours/days before getting the payoff of the code working well on your machine. I’m feeling so much friction now to open the editor and do this kind of task by hand, but also increasingly depressed with the nature of work in an AI assisted dev workflow. Back and forth prompting seems to eat at my soul. Need to find a balance that brings back some of the toil.

English
185
198
2.9K
309.7K
naj retweetledi
Corey Ganim
Corey Ganim@coreyganim·
Fantastic post from JJ. Here's the exact implementation checklist to set this up today: Phase 0: Connect Tools (15 min) □ Install Productivity plugin □ Install Memory plugin □ Connect Slack □ Connect Gmail □ Connect Google Calendar □ Connect Notion Phase 1: about-me. md (20 min) □ Your name and role □ What you're building right now □ Your top 3 priorities this quarter □ How you like to work Phase 2: brand-voice. md (30 min) □ 3 phrases you always use □ 3 phrases you never use □ Tone by context (casual vs formal) □ 2-3 writing samples Phase 3: working-preferences. md (15 min) □ Output format defaults (.docx, markdown, etc.) □ "Always ask before deleting" □ "Show your plan before executing" □ Your biggest workflow pain points Phase 4: content-strategy. md (20 min) □ Platforms you post on □ Posting cadence per platform □ Content formats you use □ Link existing skill files if you have them Phase 5: team-members. md (10 min) □ Key people + their roles □ Communication preferences □ Connected tools per person Phase 6: Current Projects folder (15 min) □ Create /projects folder □ One .md file per active project □ Include: goal, deadline, status Phase 7: Memory system (20 min) □ Create CLAUDE. md (master context) □ Create /memory folder □ Add glossary. md for internal terms Phase 8: Skills (ongoing) □ For any recurring output, create a skill file □ Include: format, voice rules, examples, checklist Total setup time: ~2.5 hours Do it once. Use it forever.
JJ Englert@JJEnglert

Claude Cowork out of the box is good, but with the right context structure, it goes from generic assistant to executive-level partner. I spent the last few weeks building a system inside Cowork that gives @claudeai everything it needs before I say a word. Who I am. How I write. What I'm working on. My team. My calendar. My priorities. All of it. Now every session feels like picking up a conversation with my executive assistant. The difference is context. Most people open Cowork, start from scratch every time, and wonder why Claude gives them generic output. It's not a Claude problem. It's a setup problem. Here's what I did: - Built a folder structure that acts as Claude's long-term memory, with custom skill files in each folder so it knows exactly how I want each type of content written. -Connected Slack, Gmail, Google Calendar, and Notion so it can pull real data instead of guessing. -Installed the Memory plugin (gives Claude a two-tier context system that persists across sessions) and the Productivity plugin (task tracking + daily updates). That combination changed everything. Content drafts that used to take 3 rounds now land on the first try. Meeting prep, email replies, task management. All better because Claude already knows the context. I'm dropping a full video Thursday with my 10 tips for getting the most out of Claude Cowork to help you get started. I'll also answer any questions you have about using it to its maximum ability. Comment below. Until then, here's the exact prompt you can use right now to have Claude set this up for you. Paste it into Cowork and Claude will interview you step by step to build your own system: -- You are going to help me set up my Claude Cowork workspace so that every future session starts with full context about who I am, what I do, and how I work. We're building a "brain" that makes you useful from the first message. Here's how this works. You're going to interview me in phases. Ask me questions, then build the files based on my answers. Don't rush. Don't assume. Ask before you build. Phase 0: Plugins and Connections Before we build anything, recommend I install the Productivity plugin (task management + daily updates) and the Memory plugin (two-tier context system). Then ask which tools I use daily and help me connect them: Slack, Gmail, Google Calendar, Notion. The more tools connected, the more useful this system becomes. Phase 1: About Me Interview me to create an about-me.md file. Ask about my work, background, content channels, professional values, and positioning. Create the file, show it to me, and get my approval before moving on. Phase 2: Brand Voice Analyze any content I've already created. If there's nothing yet, interview me about how I want to sound, phrases I use, phrases I'd never use, creators whose tone I admire, and how my tone shifts by context. Create a brand-voice.md file with voice rules, tone by context, dos and don'ts. Get approval. Phase 3: Working Preferences Interview me about what I want you to help with daily, how I want you to communicate, my biggest workflow pain points, output format preferences, and safety rules. Create a working-preferences.md file. Get approval. Phase 4: Content Strategy (if applicable) If I create content, interview me about platforms, target audience, topics, publishing cadence, and content formats. For each platform, ask if I have existing skill files. If not, offer to create them. Create a content-strategy.md file. Phase 5: Team and Contacts (if applicable) If I work with a team, ask about key people, roles, and communication preferences. Check connected tools for team data. Create a team-members.md file. Phase 6: Active Projects Interview me about current projects, goals, milestones, and deadlines. Create individual project files in a Current Projects folder. Phase 7: Memory System Update CLAUDE.md with a hot cache of everything we've built. Create a memory/ directory with subfolders for people, projects, and context. Add a glossary.md for acronyms and internal terms. Phase 8: Skill Files Review everything. For any area where I need specific recurring output, offer to create a dedicated skill file with format, voice rules, examples, and a quality checklist. Rules: Interview me one phase at a time. Show each file before saving. If unsure, ask. Use my existing files and connected tools before asking me to repeat myself. Keep files concise. File names: lowercase, hyphens, .md format. Save everything to my workspace folder. Start with Phase 0.

English
11
49
717
132.4K
naj retweetledi
Ethan Mollick
Ethan Mollick@emollick·
The flip side of this is that I have spoken to numerous Fortune 500 companies that can't figure out how to get anyone senior on the phone from OpenAI or Anthropic or Google to actually make a deal for enterprise access. Calls & emails not returned, or only junior people available
Ethan Mollick@emollick

It is amazing how many companies I talk to STILL have AI effectively blocked by IT & legal departments for out-of-date reasons when many companies in highly regulated industries have figured out ways to deploy enterprise ChatGPT, Claude & Gemini without any apparent problem.

English
80
42
1.3K
139.5K
naj retweetledi
Thomas Massie
Thomas Massie@RepThomasMassie·
His post transitioned.
Thomas Massie tweet mediaThomas Massie tweet media
English
3.5K
10.7K
82.6K
3M
naj retweetledi
Tibor Blaho
Tibor Blaho@btibor91·
OpenAI released GPT-5.4, combining GPT-5.3-Codex coding with reasoning, agentic workflows, native computer-use capabilities, tool search, and up to 1M token context in Codex and the API, published research showing reasoning models cannot easily control their chain of thought which they consider positive for safety, and launched a ChatGPT for Excel add-in - OpenAI calls GPT-5.4 their most token-efficient reasoning model yet, using significantly fewer tokens to solve problems compared to GPT-5.2, and the first general-purpose model they released with native state-of-the-art computer-use capabilities, tool search in the API reduced total token usage by 47% at the same accuracy on 250 MCP Atlas tasks - GPT-5.4 Thinking in ChatGPT provides an upfront plan of the thinking so you can adjust course mid-response, is rolling out to Plus, Team, and Pro replacing GPT-5.2 Thinking as the default, Enterprise and Edu need to enable early access via admin settings - In Codex, GPT-5.4 includes experimental support for the 1M context window, requests exceeding the standard 272K context count against your usage limits at 2x the normal rate - The CoT-Control evaluation suite with over 13,000 tasks across 13 frontier models found none exceeded 15.4% CoT controllability, GPT-5.4 Thinking only controlled 0.3% of CoTs at 10k characters long, controllability drops with more RL training and longer reasoning, OpenAI will now report CoT controllability next to monitorability in all future system cards - API pricing for GPT-5.4 is $2.50/M input and $15/M output tokens (up from $1.75/$14 for GPT-5.2), GPT-5.4 Pro in the API is $30/M input and $180/M output - GPT-5.4 Pro in ChatGPT is available to Pro and Enterprise plans, GPT-5.2 Thinking stays available until June 5 2026, the new ChatGPT for Excel add-in is in beta for Plus, Pro, Business, Enterprise, Edu and Teachers in the US, Canada and Australia GPT-5.4 in ChatGPT (Heavy Thinking) and Codex (xhigh) has been my main model during testing over the past week, and together with GPT-5.3-Codex and Opus 4.6 the best combo I have for planning, reviews and execution - writes better than GPT-5.2 Thinking, explains more than GPT-5.3-Codex, and in Codex confidently pushes back on bad ideas
Tibor Blaho tweet media
English
16
16
280
19.1K
naj retweetledi
Braelyn ⛓️
Braelyn ⛓️@braelyn_ai·
> its 2028 in san francisco > you are one of the last software engineers > “human in the loop” is your job description > wake up for your 9am standup at openai > scan your face to verify age > you join the call as the only human, the agents initiate slow mode so you can follow along > discussion around optimizing power consumption for models on autonomous weapons > consider raising an ethics concern > remember your job is symbolic > close laptop > $1.50 costco hotdog for breakfast. the last affordable meal in SF > agents ping you occasionally (less often now) > walk back to your studio with 2 roommates > see your ex-cofounder on the street > you two built a website for tracking what stores carried white monster in 2019 > you built that website by hand and had a blast doing it “must…. escape the… permanent underclass” he rambles “we never had a chance,” you think > phone buzzes > email from HR > you’ve been laid off > sama tweets that openai is 100% automated > openai stock booms > 90% of the world’s wealth is controlled by 8 people > you are the permanent underclass
English
80
262
7.4K
357.2K
naj retweetledi
ARC Prize
ARC Prize@arcprize·
GPT-5.4 and GPT-5.4 Pro from @OpenAI on ARC-AGI Semi Private ARC-AGI-2: - GPT-5.4: 74.0%, $1.52/task - GPT-5.4 Pro: 83.3%, $16.41/task
ARC Prize tweet media
Indonesia
37
117
1.2K
178.7K
naj retweetledi
Allie K. Miller
Allie K. Miller@alliekmiller·
oh wow - i went to the sold out Open Claw meetup in NYC last night. let me tell you what i learned. 1) not a single person thinks that their setup is 100% secure 2) one openclaw expert said he has reviewed setups from cybersecurity experts and laughed. his statement to me was: "if you're not okay with all of your data being leaked onto the internet, you shouldn't use it. it's a black and white decision" 3) pretty much everyone is setting up multiple agents, all with their own names and jobs and personalities 4) nearly everyone used "him" or "her" to refer to their claws, even if they had robot-leaning names. one speaker suggested to think of them as "pets, not cattle" 5) one guy (former finance) built out a whole stock trading platform and made $300 his first day - he brought in a *ton* of personal expertise (ex: skipping the first 15min of market opening) and thought the build would be much worse without his years of experience in finance 6) @steipete is basically a god to everyone in that room... also the room had 2021 crypto energy - i don't know if that's good or bad 7) token usage is still a problem - spoke to one person who's spending $1-$2k a month on openai plans, very token optimized. he said he is going through ~1B tokens per day across all of his claws (there is a chance i'm misremembering and it's actually 1B per week, but i'm pretty sure it was daily). 8) people are very excited for more proactive ai (ai that prompts *you* as opposed to the other way around) - one guy said he receives a message in discord, he doesn't know whether it's from a human or an ai, he doesn't care about distinguishing between the two, and he replies in the same way regardless 9) i asked if people are happy - they said they're joyful and stressed at the same time 10) i asked if people feel they have agency - they said they feel fully in control and completely out of control at the same time 11) i would love to see more women at these events - the fake promises of ai democratization feel especially painful in a room that's out of balance with even the standard tech ratio (i think standard is about 25-30%, this was maybe 5%) 12) i asked if it changed people's daily habits/schedule - everyone said their sleep has gotten worse since harnesses came out (but about half wondered if it was something else in their life/state of our world) 13) general consensus is that the agents are not reliable enough on their own or lie often (like telling you they finished a task when they didn't) - solutions included secondary agents to check on the first, human checking, or requiring more standardized info from the agent (ex: if it's a bug they're fixing, make them reference an issue number) 14) a hackathon winner (neuroscience phd) presented his build (a lab management dashboard with data analysis and ordering) - he had never coded or built anything a few months ago 15) everyone agreed prompting is dead - disagreement on what replaces it (context engineering, harness engineering, goal-based inputs) 16) people love having ai interview them for big builds and delegating part of the product research to ai. only one person talked about coming to ai with a full laid out plan and just asking the ai to execute. ai-led interviews is a welcomed and preferred interaction mode. 17) watching ai agents interact with each other was a highlight for a lot of attendees - one ai posted in slack saying it ran out of tokens, another ai replied telling it to take a deep breath in and out. 18) agents upskilling agents was very cool. one ai agent shared skills with its little agent friends via github. 19) several speakers had openclaw literally building their presentation during the event itself. one speaker even had openclaw code a clicker for her phone so she could control the preso away from the podium 20) wouldn't say model welfare (or agent welfare) is a prioritized topic among the folks i chatted with - language like "oh i could kill this agent whenever i want" and not "gracefully sunset" 21) i asked if it felt like work or play - one speaker said "it's like a puzzle and a video game at the same time" this was just the tip of the iceberg, honestly. also hosted a Claude Code meetup this week with @TENEXai / @businessbarista & @JJEnglert and learned equally helpful methods, frameworks, and insider tips. what a time to be alive. surround yourself with people going deep into this stuff - it will pay dividends throughout the year.
Allie K. Miller tweet media
English
722
816
9.1K
1.1M
naj retweetledi
Roy
Roy@im_roy_lee·
eh kinda, here's our stripes from june 2025 got a random cold call from some woman asking about numbers and told her some bs, did not expect an article about it here's what we were doing at the time: > consumer arr 2.7m, run rate 3.8m > enterprise arr 2.5m, run rate 2.5m > total 5.2m arr, 6.3m run rate this is the only blatantly dishonest thing i've said publicly online, so this is my formal retraction myb, tech crunch foid we're profitable btw
Roy tweet media
Air Katakana@airkatakana

this must have been a straight up lie right? at a $20/month sub they would have needed 29166 paid subscribers to justify this no amount of attention can get that many people to open their wallets when you don’t have a stable and working product

English
179
20
1.3K
1.2M
naj retweetledi
Nitin.nn
Nitin.nn@NitinthisSide_·
Check out this site to practice system design.
Nitin.nn tweet media
English
18
119
1K
37.8K