Mark (@MarkSuperDev) header
Mark (@MarkSuperDev) profile picture

Entrepreneur, Developer, CTO & Advisor. Repeat Founder, One exit. Building game studio!

San Francisco
Joined February 2010
Photo by Mark (@MarkSuperDev)Photo by Mark (@MarkSuperDev)Photo by Mark (@MarkSuperDev)Photo by Mark (@MarkSuperDev)Photo by Mark (@MarkSuperDev)Photo by Mark (@MarkSuperDev)Photo by Mark (@MarkSuperDev)Photo by Mark (@MarkSuperDev)Photo by Mark (@MarkSuperDev)Photo by Mark (@MarkSuperDev)
Replying to @emmanuel_2m
@emmanuel_2m posted a great example of MCP versus IMG to 3D, took a lot of heat for the topology. Here is the asset integrated in to Unreal Engine, including shots of the topology. In the end the lighthouse was around 700 polygons. 👇
2
3
44
4,125
Truth!!
Don't lose your grip on the dreams of the past. You must fight just to keep them alive!
2
76
Back at the Cafe in SF where I built my previous company from nothing through to acquisition. Filled with nostalgia and energy for the future!! We once filled this place when our team from China, UK and of course here in the Bay Area all got together. It’s still the same owner, a little older, when he saw me he gave a very warm welcome, unaware the impact his little cafe had on the tech scene, so many founders came through here over the years (I recall doing code reviews for YC founders here long ago lol). Good times!!
1
73
This is why we have avoided the need for a board thus far. Being founder led allows us the flexibility to do what we deem crucial to building the long term foundation to succeed! Having some folks clearly not in the arena forcing some corporate lackey in to take over what you’ve sacrificed years to build from nothing? No!
Founder led company versus functionary led company -
70
This wins the internet today!
Folks, I have spent literally the entire day trying to get someone at AOL to unlock my email. For the last eight hours, I have been told that the issue has been escalated to supervisors who would contact me. I haven't heard a thing. You would think that, since I'm one of the last human beings on the face of the Earth still using AOL, they would take care of this. You'd be wrong. So, once this gets resolved, hopefully before the next presidential election, I'm dropping them. (I kept them this long out of convenience, but now I have no reason to keep them.) I'll see you on the radio at 6 p.m., at which time I will address this further.
41
Been using YuE2 for audio locally on the Mac (MLX), its kind of incredible how far it has come. While this song is good for coding / dev work, the real power is iterating and editing along with the speed of rendering the final music.
1
100
Replying to @Kotaku
This appears to be a translation from English to Japanese and back which has picked up some characteristic nuances along the way. So to say it more Americanly: AI is happening, AI won’t un-happen, and Epic is going all-in to bring the gains to all game developers.
86
59
20
1,530
89,530
The Unity pivot to AI was the canary in the coal mine for other engine developers. The speed at which Epic are pivoting their entire stack will go down in the history books! If you aren’t building agentic repeatable workflows that help you create amazing experiences you’ll have a very challenging time ahead! This doesn’t mean giving up your creative agency, ignore one-shot thirst traps and look at what real developers are doing!
Our Q3 performance was our strongest ever, with strategic revenue growing 59% year-over-year and Unity delivering our first-ever GAAP profitable quarter since our IPO. We are seeing the compounding impact of our flywheel strategy: more creators make more games on our platform, and more games fuel the need for more discovery through advertising.
42
Epic Games are hard pivoting to AI-first development and the resulting drama is crazy. I'm not sure why this move is shocking to anyone, the existing paradigm and legacy architecture represented a very real existential threat to their existence long-term. @ Super we are a dual engine studio (one of which is UE 5.x, we even built our own MCP that we think is actually FAR better than Epics in some regards) and frankly, while some of the foundational changes that are rolling out are frustrating, in an agentic development team they are 100% necessary. The existing engine is like guiding an elephant when using AI when you really want the speed and agility of a leopard, it'll be painful but we'll take the leopard!! The new paradigm whether folks like it or not: [AI Abstract]->[gen-code]->[runtime binary] We've been working toward this internally for the last 2+ years now, it wasn't always smooth, we feel confident that the future of building is bright and more approachable than ever for new entrants as well as veteran teams. Epic are on the right side of this, you should never just settle for something because you are comfortable, be curious!
“Epic isn't trying to sell you a model.” Interesting statement from @UnrealEngine at #UEFESTTOKYO26. But I think we're ignoring a massive elephant in the room. WHO IS GOING TO PAY FOR ALL THIS AI? Epic is going all-in on AI-assisted development, while UE6 is moving toward Verse and Scene Graph, eventually removing traditional Actors, Blueprints, and the C++ Gameplay Framework. We're talking about replacing development systems that people have spent decades learning, extending, and building production pipelines around. And apparently AI-assisted migration is part of the answer. But who exactly is this designed for? AAA studios with enormous budgets can afford expensive AI subscriptions, frontier models, API usage, and dedicated AI infrastructure. Now imagine you're a small indie studio. You have 2–5 developers and limited resources. Your $20 AI subscription hits its usage limits during a serious development session. Suddenly you're looking at $200–$500 plans, multiple subscriptions, or expensive pay-as-you-go API usage. And please don't mention “just use cheaper models” argument. Anyone who has seriously worked with AI on complex Unreal Engine C++ codebases knows that the difference between budget models and frontier models is substantial. MCP supporting every model sounds fantastic on a presentation slide. But model freedom means very little when the models you actually need are financially out of reach. @TimSweeneyEpic, I think Epic needs to answer some questions: 1. Can indie developers realistically use UE6 without expensive AI subscriptions? 2. Who pays for AI-assisted migration of large existing projects? 3. Will conversion tools work without continuous third-party API spending? 4. What happens when AI quotas are exhausted halfway through development? 5. How does Epic intend to keep its ecosystem accessible to developers who cannot afford frontier models or high-end local AI hardware? @sama recently argued that it's “quite terrible” to have scarce DRAM sitting in personal computers, supposedly being used only 5% of the time, when that memory could be utilized more efficiently in cloud data centers. So the CEO of one of the world's largest AI companies is effectively arguing that scarce computing resources would be better centralized in the cloud. @nvidia : Rumors spread that largest consumer GPU dies may increasingly be prioritized for far more profitable professional hardware. RTX 5090 availability has become non existant. And RTX 5080 is going same line. And let's not forget @AnthropicAI. Dario Amodei keeps warning about the dangers of powerful open-weight models while advocating tighter controls over their release. Meanwhile, Anthropic's increasingly restrictive Claude usage policies and account enforcement show exactly how much power centralized AI providers have over their users. Developers are being pushed toward cloud AI services where the provider controls the pricing, usage limits, acceptable use, and ultimately whether you retain access at all. And local AI requires substantial RAM, VRAM, and compute (that is not affordable or doesn't exist) to deliver comparable results on serious coding tasks. So independent developers get squeezed from BOTH directions. @UnrealEngine may remain free to license, but Epic risks turning affordable game development into an increasingly expensive ecosystem of AI subscriptions, API tokens, and hardware requirements. Basically replacing one barrier with another, potentially much more expensive one. Until then, I'll be keeping my UE5.8 fork alive. #UnrealEngine #UE6 #IndieDev #GameDev #LocalAI
1
289
Another top post from my good friend @judegomila. I got to see early versions of this as they built it all up. I can tell you the Rankings alone are 100% worth browsing on a regular basis just to give you a look at things you may not have come across. ultrametric.ai/arena/game-en… I argued with Jude on the game-engines ranking in particular but you'll appreciate the detail across all categories. ultrametric.ai/arenas
I'd like to share a little about what I've been working on at my new company @ultrametricai with my cofounder @tylerlastovich. We have been exploring how we could automate the startup itself, leaving founders with more time to focus on their exact mission. Enter our first release of the Open Startup Repo: github.com/ultrametricai/ult… A common foundation for transparent automation of the startup. After close to 20 years in silicon valley, backing hundreds of amazing founders & startups, being in the trenches of founding Heyzap (YC08), then solo founding @golden, going through 2 acquisitions and working behind the scenes with some of the iconic companies today, I'm witnessing the largest change to how we work I could have imagined - a truly monumental era of creative abundance. I believe the next generation of companies will largely run themselves: from operations, code, product upgrades, growth, vendor control & selection, process execution, special situations, strategy etc etc. That leaves founder time for 'the art' at the very niche core: the (currently) unautomatable, the special leaps humans tend to make, and north star setting. We want founders to go super deep into the main problem they are trying to solve and not get held up doing anything else, from searching for domain availability with trademark checks to setting their company up, to running their processes on autopilot. So to help that broad foundational layer for starting and running a company, we have spent around a year exploring how to help founders focus on their mission across different verticals, geos, stages and initial starting conditions. Our first few attempts at making something useful actually failed as the market and AI was moving so fast; it just got absorbed into the models or other product releases. We saw polsia happen, openclaw, then grokbot, muse, dots, etc era as the astras, fables, opuses, kimis and jevs rolled out. What seemed to have been missing along the way was a common repo to identify, unify, open and normalize all the lego bricks that startups have to interact with (vendors, processes, business logic, law, best practices, surface areas, art of the possible). As the number of software vendors blew up, the interfaces to drive them multiplied, the international startup founder blew up as silicon valley moved from a specific location to a state of mind and global movement. Unlimited pre seed funding in unlimited vertical sub markets and permutations has brought us to the age of infinity but we have yet to achieve being able to type into an agent a very simple sentence with very complex implications 'just setup my company and make $1m/m'. We have ended up with a hybrid mismash of computer use, API calls, plugins, shifting surface areas (API/MCP/CLI/plugins/chats/musish futures), and changing model absorption to vendor balance making it an exciting and unstable time. As our first step we started to rank all the vendors that startups interface to when going about their journey in terms of how agentically controllable they are via their APIs, MCPs, CLIs etc and computer use compatibility as we are largely switching from a UI driven world to the agentic control surfaces and onto full automation. We have 100 ranking areas you can check out with an overall open ranking here: ultrametric.ai/overall Then we looked at the processes that startups do and how the vendors rank for the sub steps or process as a whole and how this changes across geos. Open processes: ultrametric.ai/processes Then we started to hack on an open repo for startups that would contain all the components we are going to need for a common foundation for founders across the globe even if our gov processes vary so much from Bengaluru to SF or Lisbon to Shenzhen. The founder spirit is geo-invariant. We have looked at special founder/startup situations, the business logic that will make open modules for the startup that we can hack on together, ranked law firms, government services and interfaces, stacks that go well together. We have mapped the law and lore that maps to startups and the schemas that make up the data objects and documents. But also the open documents and the missing gaps. MUCH TO DO. All the BS processes and fluff work that founders waste their time on needs to goto zero. I want to see more supersonic planes, cancer drugs, seemingly impossible missions done and increase the bang for buck founders have with their funding. This is a work in progress and we are keen for the community to come hack on the repo with us here: github.com/ultrametricai/ult… Lets get into the structure of the general repo and the visualizations we made on ultrametric.ai site with example links: - Open rankings: ultrametric.ai/overall - Open rankings example (online payments): ultrametric.ai/arena/payment… - Open ranking example 2 (cap table): ultrametric.ai/arena/equity-… - Open processes: ultrametric.ai/processes - Open process example (Incorporate C-Corp) ultrametric.ai/processes/inc… - Open situations that founders face: ultrametric.ai/situations - Open startup simulator (you can test our different initial starting conditions): ultrametric.ai/startup-sim - Open modules (e.g. cap table, payroll logic etc - we'd love help improving these) ultrametric.ai/open-modules - Open law (we are interested in how law changes the processes, situations and normalizing this over time) ultrametric.ai/open-law - Open lore (we are interested in the historical lore of startups, the rules of thumb and heuristics that might guide your agent): ultrametric.ai/open-lore - Open fields (we are interested in how the schema for the data connects to the open modules, business logic, open documents and artifacts of each process eg how is a EIN defined?) ultrametric.ai/fields - Open documentation (eg SAFE notes and missing! docs) ultrametric.ai/open-document… We have looked at YC companies as well in terms of which ones do well agentically: ultrametric.ai/yc We are interested in stacks and how people are changing their work: ultrametric.ai/stacks We are interested in what is automatable and where the agentic ceiling is currently and how to push that up in all areas: ultrametric.ai/rankings/proc… There is more for you to explore and a lot more coming in terms of how you will be able to navigate business in an optimal way in your chosen surface area; whether you are hanging in grokbot, dots, muse, claude, terminal, chat, or whatever is coming up in this exciting time. We have a lot of data to collect, clean up and help agents navigate the vast landscape emerging functionality the entire startup ecosystem has to offer. Come join us getting your vendor in, ranked or that access pattern you have wanted or getting the data more accurate in terms of which vendor is best for a process or steps. Or open a module of something that currently cost money that could be free. Also come play in our discord for founders and join the chaos (we can solve each others issues including fund raising tips from me personally): discord.com/invite/3aHky836q… It's time to lift all the boats in the harbor and I'm extremely excited as to what the community of hackers and painters will hack into the repo, what asks they will have and whether we can shift normalization of processes globally, gov agentic interfaces and have common repo for founders that grows over time. I expect a lot of experimentation along the way, bugs and upside... I appreciate our backers having faith in us as well from @ycombinator with @garrytan to @immad doing a sizable check (congrats on $1bn rev homie) to @darbyw (congrats on Stripe buying @clerkyinc), @drewhouston form @Dropbox and also @pioneer_fund @tomerlondon cto @GustoHQ and hopefully this is 'boring' and complex enough for Charlie Songhurst :> @delingpole @Liquid2V @ivolo from @segment @ryanpowe @sonicaghi of @kong @DellyTamer+ other supporters (@michaelwfrank, Fundamental ventures and if I missed you sorry moving fast!). [And don't worry, all vendor rankings are open scoring methods so no favors are being done if someone backed us and is a vendor they have to compete with how agentic and automatable they are just like anyone else.] PS: we have bugs and many quality upgrades to make but thought better to go out early and fix as a community. PPS: we have other stuff to launch we just thought this was a great place to start and have 200 PRs coming out pretty soon but I still want to know what is broken or doesnt make sense or inaccurate. Special thanks to current and past team members for getting us here and all the experiments we did you know who you are.
1
1
2
252
TTC, Time to Clone will be THE metric to track for investors and founders in ‘27. Can you be cloned in a few hours? Then you need to re-evaluate how you build and transact in an AI first world!
1
58
Evolve or Die, there are still folks that believe this doesn’t apply to them, only others. We’ve been building toward this future the last couple of years and believe we’ve found the balance we need in our new AI assisted future! Stay tuned!
Technical moats are mostly over at this point. If you’re building something that is meant to be durable, the only moats now are: • Proprietary data • Network effects • A physical component
46
This kid is smart, I actually tried to invest in him a year or two ago. Reminder: Don't invest in products, invest in founders that have that *spark* of genius. A lot of investors get stuck up their own arses trying to predict what initial product will work, for early stage, you just need an instinct for how smart and driven someone is, they'll figure it out, be there.
1
1
72
I should say this isn't the only smart thing @jaivin has done. It is very very unsurprising that he has blown through 10M views on this and counting. I hope @elonmusk & the X team lean into games on the timeline, its actually the perfect fit and would be as disruptive as canvas games back in the Zynga days @markpinc
1
1
27
100% spot on for the future of creativity, Capcom made one of my favorite arcade games back in the early days (Commando) amongst others.
#RE2026CAPCOM まとめ(ΦωΦ) 他は話が早くて写真で精一杯(ΦωΦ)
1
73
This reminds me of San Francisco Rush, every week there is a new innovation in AI that requires tooling adjustments, what an amazing time to build!!
a Waymo run down San Francisco's iconic Lombard Street. built with fable 5.5 + threejs play here: teleoperator.mindblown.ai
1
3
150
My friend Jude built this and showed me an early version, it’s worth supporting!!
I've attempted to map everything in oncology in a public website and open source repo for all. The site is trying to get all cancers, products, technologies, bottlenecks, people, startup opportunities with 1000+ ideas for upgrading the field. If you have a loved one with cancer and you are technical or can engineer, go take a look, file improvement requests or bugs or help with the open repo and make this the best open and free info resource for individuals, researchers and educational use. This should save people time, aid AI oncology projects and generate positive action. If you are not technical just complain in this thread about broken or annoying or things you want and I'll fix them live. Some of the interesting pages: Treatments: onco.cc/drugs A gallery of the molecules being used onco.cc/molecules/ And targets: onco.cc/targets/ The technologies in oncology: onco.cc/technologies/ 1100 ideas for helping oncology: onco.cc/ideas/ Bottlenecks on oncology: onco.cc/bottlenecks/ Open questions (LETS GO RESEARCH PEOPLE) onco.cc/open-questions/ Startup requests (LETS GO STARTUP PEOPLE) onco.cc/startup-requests/ Mechanics of cancer: onco.cc/mechanics Battlefronts: onco.cc/fronts/ Isotope supply: onco.cc/isotopes Key papers: onco.cc/key-papers Pipeline funnels: onco.cc/pipeline Cancer by type: onco.cc/cancers/ Institutional rankings: onco.cc/institutions/ The startups: onco.cc/startups/ Heros and heroines : onco.cc/heroes/ Key medical people: onco.cc/people/ Here is the project roadmap: onco.cc/roadmap/ Models and data sets: onco.cc/models/ There are other views as well, take a browse. Try making a PR if you have an upgrade to this on the repo here: github.com/judegomila/OnCo If you are biologically/medically minded and something is wrong, file a bug as well or say on the thread and we will get it fixed live. If this is a useful project star the repo and help get it calibrated. I've tried to add some other languages but I cannot speak them so tell me if that doesnt work well. I believe we will crack oncology and having total information dominance is key to the problem. Let the feedback flow!
1
1
6
268
I've attempted to map everything in oncology in a public website and open source repo for all. The site is trying to get all cancers, products, technologies, bottlenecks, people, startup opportunities with 1000+ ideas for upgrading the field. If you have a loved one with cancer and you are technical or can engineer, go take a look, file improvement requests or bugs or help with the open repo and make this the best open and free info resource for individuals, researchers and educational use. This should save people time, aid AI oncology projects and generate positive action. If you are not technical just complain in this thread about broken or annoying or things you want and I'll fix them live. Some of the interesting pages: Treatments: onco.cc/drugs A gallery of the molecules being used onco.cc/molecules/ And targets: onco.cc/targets/ The technologies in oncology: onco.cc/technologies/ 1100 ideas for helping oncology: onco.cc/ideas/ Bottlenecks on oncology: onco.cc/bottlenecks/ Open questions (LETS GO RESEARCH PEOPLE) onco.cc/open-questions/ Startup requests (LETS GO STARTUP PEOPLE) onco.cc/startup-requests/ Mechanics of cancer: onco.cc/mechanics Battlefronts: onco.cc/fronts/ Isotope supply: onco.cc/isotopes Key papers: onco.cc/key-papers Pipeline funnels: onco.cc/pipeline Cancer by type: onco.cc/cancers/ Institutional rankings: onco.cc/institutions/ The startups: onco.cc/startups/ Heros and heroines : onco.cc/heroes/ Key medical people: onco.cc/people/ Here is the project roadmap: onco.cc/roadmap/ Models and data sets: onco.cc/models/ There are other views as well, take a browse. Try making a PR if you have an upgrade to this on the repo here: github.com/judegomila/OnCo If you are biologically/medically minded and something is wrong, file a bug as well or say on the thread and we will get it fixed live. If this is a useful project star the repo and help get it calibrated. I've tried to add some other languages but I cannot speak them so tell me if that doesnt work well. I believe we will crack oncology and having total information dominance is key to the problem. Let the feedback flow!
200
939
109
4,544
334,672
This: "But don’t be the out of touch Kung Fu master, heir to lifetimes of tradition, that gets mauled by an amateur MMA fighter."
I recently went through a translation of Musashi’s Book of Five Rings. The introduction chronicled the evolution of swordsmanship and martial arts in general from pragmatic battlefield necessities to sports, historical curiosities, and hobbies. It was interesting to hear how in the post-WW2 occupation when martial arts were banned, Judo was represented as equivalent to western wrestling, and Kendo later to western fencing. The poignant undercurrent for me is that I can see many programming skills following that path. There are probably dozens of people reading this that remember hand assembling opcodes to hex and still have some magic numbers burned into their memory, but even the small group of people still programming in assembly today (hey, @FFmpeg !) don’t work at that primitive level now. AI is making many other programming skills much less critical. We aren’t there yet, but carefully writing code completely by hand is moving from a -jitsu to a -do. Code-do? Codo? That’s ok! The retro computing scene is delightful, full of people building and exercising old skills for the love of it. But don’t be the out of touch Kung Fu master, heir to lifetimes of tradition, that gets mauled by an amateur MMA fighter. Musashi would probably have been pretty enthusiastic about assault rifles.
1
169
It may seem retro but: bring back pull to refresh The number of times I’ve been on a post and wanted to come back to it…. No I don’t want you to auto refresh any feed!
1
83