Victor Mota

10K posts

Victor Mota banner
Victor Mota

Victor Mota

@vimota

co-founder, @coplane - the intelligence layer for the enterprise back office. previously: @Stripe, Google (BigQuery and Kaggle)

Austin and New York Katılım Mart 2008
1.8K Takip Edilen3.3K Takipçiler
Sabitlenmiş Tweet
Victor Mota
Victor Mota@vimota·
tech folks *want* people to know they're using AI, it's a flex 😅
English
0
0
0
54
Victor Mota
Victor Mota@vimota·
tbh I wish software engineers had a similar aversion to AI code. it's great to use AI, but I shouldn't be able to tell you used it. my fiancee saying she thinks non-tech people are better users of AI because they don't want people to know they're using it
rahul@0interestrates

why do people (including me) have an aversion to AI writing but not as much to AI code? if a piece of text smells AI i stop reading it but i use things coded entirely with AI every day

English
1
1
4
452
Victor Mota
Victor Mota@vimota·
Assuming the problem is trivially verifiable - wouldn't a better metric be compute-normalized solve rate. Given test-time-compute is a log axis, total compute used to get on average 1 solution for the 0.1 pass@1 (ie. 10x) may be much less than the total for 0.5 (ie. 2x an exponentially larger amount).
Victor Mota tweet media
English
0
0
2
159
Kenneth Auchenberg 🛠
In the depressing sea of Tesla’s, I found an oasis of good taste in SF at Motoring Coffee 👌✨
Kenneth Auchenberg 🛠 tweet media
English
39
1
248
24.9K
Victor Mota
Victor Mota@vimota·
@Brendan_McCord Thank you!! For a second I thought it was Dear Chairman that I just read recently. This looks great
English
0
0
0
26
Victor Mota
Victor Mota@vimota·
Corporate memos are an art form. Are there any good collections (books, archives) of the greatest memos that have been made public? Not talking about letters made for public consumption or VC investment memos , strictly internal memorandums.
English
2
0
1
437
Victor Mota
Victor Mota@vimota·
One of my favourite things at google and Stripe was reading memos from @patrickc and @collision , engineering leaders and early employees
English
0
0
0
106
Victor Mota
Victor Mota@vimota·
@JoshConstine Of all the very valid claims in the video I feel like this screenshot comparison is the weakest though
English
0
0
0
111
Kenneth Auchenberg 🛠
Kenneth Auchenberg 🛠@auchenberg·
Personal news! I’ve joined @iendeavors as our partner in NYC to back technical builders and focus on software infra! We need to rethink all of our infrastructure and abstractions for an agent-first world. Now is the time to double down on infra. Blog: kenneth.io/post/joining-i…
English
34
5
87
11K
Victor Mota retweetledi
Chris Sperandio
Chris Sperandio@sperand_io·
phenomenal take. hard to overstate the importance of ASC 350-40 here. when it comes to *clerical* (G&A) work, frontier models are for codifying, not for performing. in enterprise, creation of bespoke internal "Corporate" software (and continuous self-assembly thereof) is the killer app
christian@curious_vii

"...frontier models are useful for producing capital assets. Open weights models are useful for operating them..." Here's how I'm thinking about frontier vs. open weights models atm: As long as the Labs can maintain a meaningful, if relatively small in terms of the time it takes to catch up, lead versus the open weights models on the margin, it'll often be the economically rational decision to pipe your problem in context through OpenAI or Anthropic's latest offering and not the open weights models. That being said, I do suspect there's room in the real economy for both. One way of thinking about this is that frontier model tokens and the complementary labor that uses them should probably be capitalized as you take good judgment and scarce context and turn it into a capital asset, e.g. an intangible full-stack software application that unlocks capacity across the business, making a subject matter expert's logic and data accessible to team members asynchronously and in an AI-native way via MCP. On the other hand, open weights models would seem to make more sense as OPEX spend once something is known and scaled. If there is some probabilistic inference that needs to happen at runtime to make that capital asset available to a larger audience, then using those open weights in production might be the move. So, frontier models are useful for producing capital assets. Open weights models are useful for operating them.

English
0
1
7
1.5K
roon
roon@tszzl·
no bro you need to turn on “/extrausage”. dawg are you sure you have “/fast” mode on? Did you check the “no mistakes” toggle? are you sure you picked “correct mode”? did you turn up the “autonomy slider”, that’s how the pros use it,
English
190
93
3.4K
199.9K
Victor Mota
Victor Mota@vimota·
@TheStalwart @tszzl Through the RL process being mediated by people whose views overlap with that centroid!
English
0
0
1
24
Joe Weisenthal
Joe Weisenthal@TheStalwart·
@tszzl Probably. But how do you get the centroid of the knowledge worker specifically or the respectful programmer out of such a massive crawl? What technique ends up elevating their views above the ideology of the comments section?
English
3
0
22
3.9K
roon
roon@tszzl·
@TheStalwart I believe the statistical footprint of LLM text on the internet-mostly gpt and claude- exerts a gravity on the training of all new models. also these views are probably the most coherent extrapolation of the educated internet that programs (the Bay Area cultural vortex)
English
8
3
140
20K
Victor Mota
Victor Mota@vimota·
the most insightful bit from the Chesky interview for me was the idea of managing people *through* the work. The idea that managers shouldn't be people's therapists is obvious, but that the coaching/mentorship/performance evaluation happens through focusing on the work was a good framing for how managers can still be production-oriented and managers at the same time.
English
0
0
2
253
Fahd Ananta
Fahd Ananta@fahdananta·
Correct, it’s one of the lowest leverage ways to work with each other Typically you only see rookie leaders jam up their calendar with tons of 1:1s. They don’t know what else to do and pick the least impactful, low conviction way to establish their leadership.
David Cramer@zeeg

If you’re a manager and you have weekly 1:1s with your reports you are wasting your time and their time You’re either misunderstanding the purpose of the 1:1, or you’re using it to discuss tactics that should be group sessions

English
2
1
56
16.1K
Victor Mota retweetledi
Chris Sperandio
Chris Sperandio@sperand_io·
Here's why Cloudflare is the exception to the pattern of companies using spurious AI transformation claims to justify "we got fat and lazy" layoffs. Brief preamble: AI running amok doesn't work at scale for repetitive, high stakes, low-creativity-points, compliance-heavy back office business processes with tons of stakeholders. Too many companies think the answer is to throw managed agents at them. Or just to arm humans with AI augmentation. Both have their place but not for core operational transformation. The naive approach drives opex up and quality of outcomes down. Cloudflare is unsurprisingly ahead on real internal transformation and cost excision (while innovating and growing apace) because their developer platform is the reference architecture for real AI driven corporate transformation. The enabler is not always more AI. It's more, bespoke, deterministic logic under AI-speed iteration cycles. No 18 month implementation of S/4 so you can get Joule on the other end. Just... build and ship the internal "information processing" software yourself. You need AI on the meta loop, self-organizing and progressively compiling the happy path and exception cases into CPU instructions- self-authoring harnesses that evolve for each specialized workflow. It takes more if/else clauses then was ever profitable to fully codify human judgment in the back office (the beauty of ABAP notwithstanding), but that's changed with the cost of if/else authorship plummeting and the emergence of infrastructure that can hot reload cpu instructions (eg with cf dynamic workers). It doesn't always take a trillion parameters to post an invoice or reclass a transaction or run a recon, but it does in the exception case. And in the back office, the exception is the rule. So solving with humans was the correct decision historically. Models are smarter than the marginal shared service center staffer now. But they're also more expensive. (Really!) But once an agent has done it enough, AI can distill the deterministic rules over historical decisions and exceptions, and call specialized model invocations or agentic subroutines where still needed. This paradigm shifts token cost from opex to capex and achieves real outcomes vs shiny demos. Kudos to @eastdakota on the decisive moves. I'm sure it was a difficult decision to enact. But this is the company to emulate and learn from if you are seeking to see real G&A cost curve inflection. If your company does 2bn+ in revenue and employs >10 FTEs per B in revenue in the controllers org, reach out to discuss how to be more like Cloudflare.
Matthew Prince 🌥@eastdakota

@MicheleRivaCode Some truth to that. There’s a whole bunch of back office you needed to be public which AI has made a lot more streamlined. Very few engineers or customer-facing sales people impacted by our layoff. And we’ll continue to hire like crazy in those roles — like we did as a startup.

English
0
2
5
1.8K
Victor Mota
Victor Mota@vimota·
Skill used to be a natural speed limit to what you could do in software engineering - but that's no longer true. A junior engineer could only write so many lines of code that compiled and worked, and their skill was the rate limiter. As they got better the scope of what they could do increased along with the speed which they could do it. With AI, that's no longer true. The raw output a junior vs senior engineer can produce is roughly the same, yet the quality and risk blast radius is vastly different between the two. On the one hand, that's great - you're no longer bottle necked by technicalities that may or may not be relevant to what you're trying to achieve (ie. the particular syntax of a language). But on the other, you now don't have any backpressure. Someone with lesser skill can produce as much in volume as an expert (which Chamath seems to think makes the latter no longer relevant !!) obsfucating the risk and tech debt that used to be naturally limited. The biggest problem of all is that on the surface the two look the same - which explains a lot of the exec AI psychosis we're seeing right now.
English
1
0
3
192
Victor Mota retweetledi
Chris Sperandio
Chris Sperandio@sperand_io·
Choice of user-agent is incidental to blast radius. A midlevel's openclaw's action surface is limited to the credentials they've been issued, which are provisioned as a liability / controls risk by IT. Usually exceptionally conservatively. SAP’s GTC says the customer owns the data and bears responsibility for who they grant access to. Their job is to provide the controls customers configure to enforce their own policies, and to ship software that behaves as documented. they do that exceptionally well. programmatic access stipulations are their prerogative but are ultimately self defeating. this isn’t new either — see the Celonis litigation. It's in keeping with their anti-competitive, anti-customer, eurocoded modus operandi. The founders would shudder, which ultimately is why you can trust SFDC over SAP, Workday, ServiceNow in the next-decade horizon. While CRM's signals are mixed (headless on one hand, slack restrictions on the other), running SAP and Workday unambiguously means being subject to their whims over how you access and use data you own. This is a strategic / adaptive liability for the F500 and a massive opportunity for next gen enterprise players
English
0
1
4
286
Victor Mota
Victor Mota@vimota·
@patrickc @daytonaio Nice - that's what I remember it being called when I joined in 2020, glad it's come back full circle!
English
0
0
0
102