Binh

Poland is also home to so many brilliant Erlang and Elixir developers. I've worked with a few of them via @ErlangSolutions. I think the stud @Prince_Canuma operates out of there too.

The upper right corner of @opencode is my favorite bit of software real estate.

I've been using @OpenAI Codex to compare Python scripts generated by Qwen 3.6 and Open 4.6. Codex consistenty ranks the Qwen scripts higher.

@itsolelehmann Cowork

i'm running a live claude cowork workshop for non-technical people on april 22 by the end of the 2 hours, you'll have a fully set up marketing system on your computer that: > produces a full week of content in one sitting, dialed into your voice so it sounds like you on your sharpest day > turns any marketing framework or post into a repeatable skill that claude runs on command for you > builds sales pages in minutes so you stop paying designers and copywriters thousands > schedules tasks to run while you sleep so you wake up to finished drafts, fresh ideas, and updated reports every morning > writes launch emails, newsletters, and sequences using the same frameworks behind my 6-figure product launches all click by click, on your machine, while i do it on mine here's everything that you get: • the full 2-hour live workshop where you build everything in real time • 16 personal skills that i built over 100s of hours for my own business • the complete recording so you can rewatch anytime • a self-paced course version of all the material • access to Claude Marketing OS telegram group this system runs 90% of the marketing behind my 7-figure brand doing 15M+ impressions/month and it's all yours come april 22nd comment "Cowork" and i'll DM you the link

My sophmore year I worked at UW cancer research lab placing tumors in hairless mice, just under the skin. The tumor would grow wherever it placed. I started working at RealNetworks after research become too difficult to observe.

I'm always surprised at people's enthusiasm over ditching one frontier model for another. I get the best results when using @claudeai in tandem with @OpenAI.

The frontier models are decent at designing web interfaces but pretty bad at designing for iOS and MacOS. My approach now is to go from design document to web implementation with Gemini, and then from Gemini to UIKit/AppKit with Claude. Porting from one language/framework to another seems to make a lot of sense to these models.

Maxell is bringing back a classic, w/ their brand new Cassette Player 🥳🎉 -Wireless AND Wired 🙌 -Rechargeable ⚡️ -11 Hours of Battery 🤯 * Step back into the 80’s with Maxell *

I've been converging on a realization: software engineers are still very much needed for the foreseeable future. Let me explain why, and why I think the current AI hype cycle is no different from every previous one. First, of course, there will be a specialized, narrow set of skills that lets people build AI-assisted software without touching the code much — guidelines and best practices that make it possible to maintain a project by AI alone for more than a couple of weeks, with proper storylines, tests, and compatibility layers between components. The code would get messier. It would accumulate repetition. As of today's models, it probably wouldn't be secure enough — though this is changing quickly. But for a small-ish project, it would be maintainable. Being a fan of the Unix philosophy — small, targeted tools that do one thing well — I think this approach may actually fly. Quick detour: if the OS kernel is stripped down to its core and you have a compiler, tools like `binutils` could in principle be AI-built on top of well-documented syscalls. Lightweight, correct, pleasant to use — and never touched by human hands. However, whether you like it or not, money is concentrated in large-scale, enterprise-grade products. And those require exactly what AI still struggles with: long-term context maintenance. Acquiring quality context that is well internalized in operational memory is everything. Perhaps better code annotation tools and new reasoning techniques will produce a leap forward here — but so far, I wouldn't bet on it. For prototyping, AI wins. For refactoring: unclear. I've tried a couple of times to hack something up with AI first — get a working prototype, extract the story, then refactor cleanly. Does it help the overall development process? Inconclusive. Once you have the prototype, it's not clear it's of much use beyond helping you visualize what it should look like and surface imperfections in the original approach. That's about it. Tests help, sure — though even that is less clear-cut than it sounds. A well-defined set of acceptance criteria in plain English may already be competitive with a suite of unit tests. We might port tests conceptually rather than literally: summarize the intent, then ask an LLM to reconstruct the test in spirit, not character-for-character. So we're back to the same conclusion. AI helps build prototypes and set direction. There will be a narrow niche of engineers who can scale what's buildable without touching code — from trivial to somewhat less trivial. That I believe. And yet: most code today lives inside large companies, with complex business logic and long sales cycles. I'd prefer these companies to transform or die out — I like lightweight, fast, simple experiences. But this machine will take a decade to turn, at minimum. If it turns at all. Much like large companies have crowded out open source by offering better end-user products, we may see the same happen with indie projects. People will keep doing business with the big players, tolerating the clumsiness, because for what they pay they get predictable quality. Think of OpenOffice — it never competed with the giants, while those giants replicated its functionality many times over. The same dynamic may play out for AI-built SaaS. So if you're a good software engineer, your job is safe. We will need more people who can apply sustained intelligence over extended periods to legacy-heavy codebases — people who can articulate which changes can be made quickly, which require careful planning, and which are too dangerous to attempt without a full redesign. "Programmer" once meant someone who flipped switches or punched holes in cards. That changed long ago, and the industry didn't suffer. We're going through the same transformation now — faster, but not dramatically so. We've seen a long series of tools each promising 10x productivity gains. Ruby on Rails is a fine example. At the end of the day, every other approach proved at least as effective, and the industry didn't move much faster in the long run.

@zilasino Rails console

What Rails feature still feels like magic even after years of use?

@signulll Where does the group chat fit in?

let's simulate what sama & mark chen are going through for the next few weeks on what to prioritize & what to chop shall we? this will be the walmart version of it lmao. openai has 29 "products" in the portfolio. - chatgpt - chatgpt search - deep research - chatgpt agent - chatgpt atlas - chatgpt pulse - sora - codex - image generation / images - voice in chatgpt - projects - canvas - tasks - shopping research / commerce in chatgpt - gpt store / gpts / apps - chatgpt business - chatgpt enterprise / team / edu packaging - atlas for enterprise - oit's vepenai api platform - responses api - realtime api - agents / agentkit - agents sdk - web search api/tooling - image generation api - codex cloud / developer codex surfaces - computer-using agent (platform/model layer) - operator (legacy/transitioning standalone identity) - let's say 4 hardware devices jony ive's team is working on (this probably does not get killed) now obviously most of these fit into the enterprise & coding territory. so what do you keep vs kill? most likely to be killed / deprioritized: atlas pulse gpt store (at least put in sunset) shopping & commerce sora (as a “hero product”) merge & consolidate everything else into chatgpt app. intense focus: codex agents enterprise workflows

@itsalexvacca SKILLS

We built 12 Claude Skill files that run our entire GTM operation inside Clay (and I'm giving it all away) Prompts give you generic output. These skill files on the other hand are built from hundreds of Clay tables across 80+ B2B clients at $7M ARR. Each one does a specific job: → Company Research Agent → Personalization Writer → ICP Scorer → LinkedIn Profile Analyzer → Data Cleaner & Normalizer → Objection Handler → Email Sequence Writer → Competitor Analyzer → Job Posting Analyzer → Technographic Qualifier → News & Signal Synthesizer → Account Brief Generator How it works: drop it into Clay → map your columns → run. No prompt engineering. No switching tools. Just output. Giving the full pack away free. Reply "SKILLS" and I'll send it.

Thanks to help from @claudeai my Framework 13 automatically detects my Benq display when it's in clamshell mode. It even helped me create a TUI to cycle through different resolutions.

So it is true. @GeminiApp can lose your chats in an irrecoverable way and man does that suck.

For Johnny. For the brotherhood. For America. 🇺🇸

icon

I've always been told real programmers don't use print() or puts, but I've found that coding agents are exceedingly more effective when they're encouraged to use print or puts liberally to help them interpret their own code.

I think people are sleeping a bit on how much Ruby on Rails + Claude Code is a *crazy unlock* - I mean Rails was designed for people who love syntactic sugar, and LLMs are sugar fiends.

@zoltanhosszu @jorgemanru That's awesome. Looking forward to trying it. I'm currently working on porting the lexical-ios project to have native support on MacOS. Table support is the last item on my list.

@binh @jorgemanru Yes! Plus, Enter and Backspace also work as expected

Although Mr. Lexxy (@jorgemanru) is spending his well deserved sabbatical, work on our open source text editor doesn’t stop! We’re bringing some awesome Table UX improvements in the next version of Lexxy: github.com/basecamp/lexxy…

Many 49ers fans would love to see the Niners move back to San Francisco, throwing it back to the Candlestick Park days, when the 49ers won their five Super Bowls. How would you feel about a stadium design like this? Golden Gate Bridge as the backdrop, still an outdoor stadium with a natural grass surface. #49ers