
swe | reading, tinkering, and building things | Alum @RecurseCenter @uOregon
NYC đź—˝
Joined January 2009
- Tweets1.7K
- Following899
- Followers405
- Likes9.1K
Marc retweeted
The eyebrow equivalent of uptalking. This is the face people use when they don't want to take responsibility for what they're saying.
Marc retweeted
Another one. Already a powerful painting, but moving around it yourself gives a totally different feeling.
Jacques Louis David's "The Death of Socrates" => #Genie3
Marc retweeted
a ton of ppl are overengineering ai products right now & worse many are showcasing tech instead of solving anything real.
you gotta start simple. stupidly simple. then layer in narrative & features like you’re sending love letters. each iteration should feel handcrafted, like a letter pressed card with your name on it. less “look what ai can do.” more “this was made just for you.”
the best ai experiences aren’t maximal, they’re specific. this is what we are doing.
Marc retweeted
opencode rewrite is done and ready for general use
- works with claude pro/max
- beautiful themeable tui
- shareable links for any session
- zero config LSP support
- works with 75+ LLM providers (including local)
link in reply
Marc retweeted
There's a new kind of coding I call "hype coding" where you fully give into the hype, and what's coming right around the corner, that you lose sight of whats' possible today. Everything is changing so fast that nobody has time to learn any tool, but we should aim to use as many as possible. Any limitation in the technology can be chalked up to a 'skill issue' or that it'll be solved in the next AI release next week. Thinking is dead. Turn off your brain and let the computer think for you. Scroll on tiktok while the armies of agents code for you. If it isn't right, tell it to try again. Don't read. Feed outputs back in until it works. If you can't get it to work, wait for the next model or tool release. Maybe you didn't use enough MCP servers? Don't forget to add to the hype cycle by aggrandizing all your successes. Don't read this whole tweet, because it's too long. Get an AI to summarize it for you. Then call it "cope". Most importantly, immediately mischaracterize "hype coding" to mean something different than this definition. Oh the irony! The people who don't care about details don't read the details about not reading the details
Marc retweeted
there is no market for way shittier versions of apps/games/software no matter how fast you and an LLM can "make" it
Marc retweeted
Launching GPT4All 3.0: The Open-Source Local LLM Desktop App
- Completely Private Experience
- Supports 1000’s of models and all major operating systems
- Major UI/UX Improvements
- Local File Chat
- MIT Licensed
Get started below:
Marc retweeted
Replying to @dumbstoicc @linear
We're currently on LaunchDarkly, but not married to it.
Marc retweeted
This is by far my favorite post on the AI executive order. Andrew says it best:
The right place to regulate AI is at the APPLICATION layer. Requiring AI apps like healthcare, self-driving, etc. to meet stringent requirements, even pass audits, can ensure safety. But adding burdens to foundation model development unnecessarily slows down AI’s progress.
Laws to ensure AI applications are safe, fair, and transparent are needed. But the White House's use of the Defense Production Act—typically reserved for war or national emergencies—distorts AI through the lens of security, for example with phrases like "companies developing any foundation model that poses a serious risk to national security."
Yes, AI -- like many technologies such as electricity and encryption -- is dual use in the sense it can be used for civilian or military purposes. But conflating AI safety for civilian use cases and military applications is a mistake.
It’s also a mistake to set reporting requirements based on a computation threshold for model training. This will stifle open source and innovation: (i) Today’s supercomputer is tomorrow’s pocket watch. So as AI progresses, more players -- including small companies without the compliance capabilities of big tech -- will run into this threshold. (ii) Over time, governments’ reporting requirements tend to become more burdensome. (Ask yourself: Has the tax code become more, or less, complicated over time?)
The right place to regulate AI is at the application layer. Requiring AI applications such as underwriting software, healthcare applications, self-driving, chat applications, etc. to meet stringent requirements, even pass audits, can ensure safety. But adding burdens to foundation model development unnecessarily slows down AI’s progress.
While the White House order isn’t currently stifling startups and open source, it seems to be a step in that direction. The devil will be in the details as its implementation gets fleshed out -- no doubt with assistance from lobbyists -- and I see a lot of risk of missteps. I welcome good regulation to promote responsible AI, and hope the White House can get there.
Marc retweeted
MSFT had a press event today w/ OpenAI. All summed up here.
IMO, it isn't a question of OpenAI vs Google, but a question of OpenAI + Microsoft vs Google.
theverge.com/2023/2/7/235874…
Marc retweeted
Chat AI is the Current Thing, but
IMO dont sleep on the text2img community, they are alive and well and hacking away every day
Analog @StableDiffusion was recently released and is marking a new frontier in AI-generated, not-crazy-oversaturated photorealism.
These Do Not Exist:






























