Mark

1K posts

Mark

Mark

@MarkYourMaker

Founder @ MNIFST | AI Engineer

Stamford/Hertfordshire เข้าร่วม Mart 2011
1.2K กำลังติดตาม205 ผู้ติดตาม
Mark
Mark@MarkYourMaker·
@nico_jeannen @Logitech Having the exact same issue - got in touch with Logitech but have just missed the warranty window and will have to buy a new one - what a pain!!
English
0
0
0
459
Nico
Nico@nico_jeannen·
Been using @Logitech MX Masters for the past few years and the quality is absolute trash I've had 5 so far. EVERY SINGLE ONE breaks after ~6 months of use with the EXACT SAME ISSUE (the left click stops working). Any good alternative to this junkware? The #1 things I need are the ability to horizontal scroll, all the buttons (eg, to easily move between desktops, as well as being able to swap between devices easily.
Nico tweet media
English
90
1
40
112.2K
Mark
Mark@MarkYourMaker·
Amazing comms as always from OpenAI team 👏
Tibo@thsottiaux

Hello beautiful people! We have reset usage limits across Codex and ChatGPT Work. And another one will come later in the day. Rejoice. Now that I have your attention, a quick update on ChatGPT Work, Codex and all the updates we shared yesterday. We’ve spent the last 24 hours reading feedback, looking at usage patterns, and talking with many of you. The short version is that there is a *lot* of excitement for GPT 5.6 Sol, ChatGPT Work on mobile & web, but also that we didn't get everything quite right. - We made it too easy to use the highest-compute settings without making the impact on usage limits sufficiently clear. - We reorganized the desktop app in one bold move, making familiar things like chats and projects harder to find. - Our launch framing was focused on ChatGPT Work and to some of our Codex fans it made it feel like Codex was going away over time. Absolutely not our intention, we love Codex and it is here to stay. - And we introduced regressions for some existing multi-agent workflows, alongside a collection of rough edges in plugins and other parts of the experience. We’re landing a first set of improvements today. We’re resetting usage twice so people can keep experimenting, changing defaults and the model picker so they don’t push people toward unnecessarily expensive settings, fixing several plugin submission issues, improving how we represent Codex in the product, and cleaning up some of the most immediate desktop problems. A larger set of improvements will land next week. We’re bringing chats and projects back into the sidebar in a more familiar and customizable way, making usage and reset timing much more visible, clarifying when to use ChatGPT Work and when to use Codex, and addressing the many other smaller pieces of great feedback we've had. The ambition behind this launch hasn’t changed. We think bringing ChatGPT and Codex together into a workspace where people and agents can collaborate is a very important step forward. But an ambitious direction doesn’t excuse avoidable confusion or regressions in the first version. Please keep the feedback coming. We’re moving quickly, and you should see the experience already get better with a few updates today; and substantially better again next week.

English
0
0
0
24
The Bugged Dev
The Bugged Dev@thebuggeddev·
Eh, i'm really not impressed by GPT 5.6 sol lol. Asked it to recreate a 3 screen app design with image generation skill. Given how well it performs on benchmarks, I expected a lot more but the results were pretty ehhh. Not even close. Maybe I need to try harder but then... wasn't it supposed to do better?
English
99
24
614
138.3K
Mark
Mark@MarkYourMaker·
@thsottiaux @Lentils80 also ChatGPT projects are now gone - this feels like a huge downgrade in that regard
English
0
0
1
23
Mark
Mark@MarkYourMaker·
@thsottiaux @Lentils80 Is switching between Work and Codex supposed to do something? The entire app is the same no matter which one I select
English
1
0
0
83
Tibo
Tibo@thsottiaux·
@Lentils80 Most technical staff I know still refers to it as Codex. It's all the same, actually significantly improved. And no way back after you try it with GPT-5.6 Sol.
Tibo tweet media
English
99
5
605
33.9K
Mark
Mark@MarkYourMaker·
@DavidOndrej1 No sweat - VPN to the rescue. Looking like a Solny day ☀️
English
0
0
0
281
David Ondrej
David Ondrej@DavidOndrej1·
if GPT 5.6 Sol is not available in the EU im gonna actually crash out
English
121
13
1.1K
91.9K
Mark
Mark@MarkYourMaker·
The Sol is rising ☀️
English
0
0
0
9
Mark
Mark@MarkYourMaker·
@UltraLinx A luxury that’s out of reach to most unless that want to hire it for a weekend play but realistically only few will every have it or use it.
English
0
0
0
141
Oliur
Oliur@UltraLinx·
So Fable is a Ferrari.
Dan Shipper 📧@danshipper

GPT-5.6 is like a Porsche, Fable is like a warp drive. We've been testing internally @every for about a month. And GPT-5.6 is the best combination of power, speed, and performance for your day to day knowledge work and coding. Fable is a different beast. If you need to get across the galaxy use Fable. If you need to get around town using the best available tool for the job, use 5.6 Full vibe check dropping tomorrow!

English
9
0
134
29.6K
Mark รีทวีตแล้ว
Dan Shipper 📧
Dan Shipper 📧@danshipper·
.@NataliaZarina rode so hard for Claude Code we devoted an episode to how she was using it to automate her job running @every’s consulting practice. Fast forward to five months later, and she rides just as hard for Codex. I had her back on AI & I to talk about what caused her to make the switch, including how she ran a prompt in Codex before bed and woke up to a finished, custom CRM tool. We get into: - Why she finds Codex easier to use than Claude Code - How she’s using loops in Codex to create customized tools that work exactly how she needs them to - Why the consulting team still pays for SaaS products like Attio and Asana even though they could vibe code their own versions - How she built an app to manage her father’s medical care in Codex - How knowledge work is evolving from sculpting to gardening, in which you develop the context and logic you need for an agent to execute for you This is a must-watch for anyone trying to figure out whether to build their own tools or buy real software—and what it takes to get an AI agent to run unsupervised for hours and nail the output. Watch below! Timestamps 1. Introduction: 00:01:05 2. How Natalia manages Claudie, the consulting team’s AI project manager: 00:02:35 3. Why the consulting team still pays for SaaS products: 00:04:55 4. Codex as a game changer : 00:11:47 5. Building personalized learning guides and illustrated explainers with AI: 00:14:55 6. Inside Natalia's AI-powered email triage system: 00:21:40 7. The shift from knowledge work as sculpting to knowledge work as gardening: 00:26:44 8. Using Codex to on-shot a custom CRM: 00:28:57 9. Using Codex to build an app that coordinates her father’s medical care: 00:33:16
English
12
10
152
25.4K
Mark
Mark@MarkYourMaker·
@theo Insane
Türkçe
0
0
0
37
Mark รีทวีตแล้ว
Justin Poehnelt
Justin Poehnelt@JPoehnelt·
Two months ago I was fired by Google for creating the Google Workspace CLI. It went viral, hit #1 on Hacker News, gained thousands of GitHub stars and many thousands of actual users in just a couple days. It was an incredible, confusing journey, from directors and leaders asking what they could learn from the tool to getting grilled by legal about why the Google logo and brand colors are on the Google Workspace GitHub code repositories. I think the cause was that Workspace and certain leaders (and projects) were afraid of being disrupted. But the fear wasn't specific to my CLI, it was a broader fear in what agents meant for Workspace. Either way, the irony of my termination was the announcement at Google Cloud Next two days before I was fired that an official Workspace CLI was coming. I want this out there because it is easier for me to explain my story and it is an experience I want to fully own. It's also part of my healing. Nearly 7 years at Google was an incredible opportunity for me and I was fortunate to have wonderful teammates and a manager that fully supported me through these last few months. Thank you.
Justin Poehnelt tweet media
English
617
1.1K
14.8K
4.8M
Mark รีทวีตแล้ว
Mark รีทวีตแล้ว
Shruti
Shruti@heyshrutimishra·
This is why smart people rarely build businesses Jensen Huang stood in front of a room of Stanford graduates and told them he hopes they suffer. He wasn't being cruel. He was being precise. His argument: people with very high expectations have very low resilience. And resilience, not intelligence, is what decides who actually makes it. A Stanford grad has spent their whole life as the smartest person in the room. They've rarely been tested by real failure. So when something finally breaks, they break with it. Then he said the line every founder should sit with: "Greatness is not intelligence. Greatness comes from character. And character isn't formed out of smart people, it's formed out of people who suffered." He would know. At nine, Huang was scrubbing toilets at a Kentucky boarding school his family hadn't realized was a reform school. As a teenager he bussed tables at Denny's. In 1993 he started NVIDIA in a Denny's booth, and nearly lost it more than once in the years that followed. The character was built decades before the valuation showed up. This is why he uses the words "pain and suffering" inside NVIDIA with what he calls great glee. He isn't trying to shield his best people from the hard part. He's trying to give it to them on purpose. Talent gets you into the room. The people who stay are the ones who were broken once and learned they could rebuild.
English
106
874
4K
271.9K
GREG ISENBERG
GREG ISENBERG@gregisenberg·
The takeaway from Fable 5 being BANNED by the government: GET GOOD AT LOCAL MODELS SO YOU HAVE 100% CONTROL. My entire weekend was going to be building my craziest ideas with Fable 5. That's now cancelled. So instead of building with Fable this weekend, I've decided I'll go deep on local models: 1. Start with the runtime. Download Ollama or LM Studio first. This is the thing that actually runs models on your machine. 2. Match the model to your hardware. A model's size is measured in billions of parameters (7B, 32B, 70B). Bigger is smarter but needs more memory. Rule of thumb: a 7B model runs on almost any laptop, a 32B needs a good Mac with 32GB+ RAM, a 70B needs serious hardware like a DGX Spark or a maxed-out Mac Studio. 3. Know which model for which job. Qwen 3 is the best all-around choice for most tasks. DeepSeek for reasoning and coding. Gemma 4 when you need something tiny that runs on a phone. Llama when you want the biggest community and the most fine-tunes. 4. Quantization. You can shrink a model to run on weaker hardware with barely any quality loss. Look for versions labeled Q4 or Q5. This is how a model that "needs" a server runs on your laptop. Learning this one concept changes everything. 5. Connect it to your agent. Point Hermes or your agent stack at a local model. 6. Context window is your real constraint locally. Cloud models give you huge context for free. Local models make you pay for it in memory. A bigger context window eats RAM fast. Keep your sessions tight and your prompts lean or your machine chokes. 7. Learn to give local models tools. A smaller local model with web search, file access, and code execution beats a giant model with none. The capability gap closes fast when you wire up the right tools. The model is the engine but the tools are the wheels. 8. Fine-tuning is more accessible than you think. You don't need this on day one, but know it exists. You can take an open model and train it on your own data so it gets good at your specific domain. I'll probably do a breakdown at some point on this @startupideaspod if people are into it. The lesson from this ban is basically don't build your entire workflow on something that can disappear with a single letter. Own part of your stack. Local models are insurance. It reminds me when people realized they don't own social media accounts. And then you saw people build email lists etc. I remember running a startup and my biggest traffic source was organic FB. All of a sudden, algo changed, and I lost 99% of my traffic. Same sorta moment (but bigger) for AI. This is a wake up call.
English
341
438
4.3K
486.8K
Mark
Mark@MarkYourMaker·
@jasondoesstuff I have an M3 Max with 64gb ram and it wouldn’t even break a sweat with what you’ve me mentioned
English
0
0
1
18
Jason Zook
Jason Zook@jasondoesstuff·
Hey Macbook Pro M4/M5 Max owners, Does running Conductor, Codex, Terminal, an email app, Slack, Chrome, Telegram, Messages, Spotify, and like 19 other random background apps hold up fine? Asking for a friend with a M1 Max laptop. 🙊👀
English
177
1
324
103K