mgdev

6 ms·

1.
by mgdev 2mo ago
Never bet against Clay.
2.
by mgdev 3mo ago
> Whatever they did to market the product Not-JIRA + dark mode + usable APIs will take you far.
3.
by mgdev 5mo ago
Mitchell is a bellwether. This is a 'tipping point' situation. Exodus will be a little at a time, then all at once.
4.
by mgdev 5mo ago
It's a mistake to confuse what you're seeing out of today's models with what you'll see out of future ones. We're barely out of the gate on this stuff. We'll borrow what works, and use it to bootstrap something
5.
by mgdev 5mo ago
I can't tell if you're trolling. Nothing precludes you from doing that with AI-gen code vs human-gen code. What you just described is downstream. If you have a human authoring code, you re-roll every time they release a new versio
6.
by mgdev 5mo ago
You already do this with human-authored code, just slowly. Project model capabilities out a few years. Even if you only assume linear improvement at some point your risk-adjusted outcome lines cross each other and this becomes the preferred
7.
by mgdev 5mo ago
This is an economically sound conclusion. It also means that you need to extract enough value to cover the cost of said tokens, or reduce the economic benefit of finding exploits. Reducing economic benefit largely comes down to reducing dis
8.
by mgdev 5mo ago
Once upon a time S3 used to cache small objects in their keymap layer, which IIRC had a similar threshold. I assume whatever new caching layer they added is piggybacking that. This keeps the new caching layer simple and take advantage of th
9.
by mgdev 8mo ago
One thing you can try is powering Clawdbot with a local model. My company recently wrote[0] about it. Unclear what kind of quality you'll get out of it, but since the tokens are all local, kinda doesn't matter if it burns through
10.
by mgdev 8mo ago
I offhandedly set it up to do a weather alert every 4 hours during the big winter storm. Absent a well-specified API, I can only assume it was repeatedly doing a bunch of work to access some open API it discovered. Very much the LLM equival
11.
by mgdev 8mo ago
This thing is cool except: 1) It chews through tokens. If you're on a metered API plan I would avoid it. I've spent $300+ on this just in the last 2 days, doing what I perceived to be fairly basic tasks. 2) It's terrifying. N
12.
by mgdev 9mo ago
It's the perfect honeypot.
13.
by mgdev 11mo ago
After 20+ years with Apple, I'm 90% on Linux at this point. Two desktops, two AI workstations, two laptops, and a handheld. Even my wife is running Linux. My personal phone and work laptop are the last holdouts.
14.
by mgdev 11mo ago
Very simple. Undermines their ad business - which is their fastest-growing profitable business.
15.
by mgdev 11mo ago
Hear hear. Elixir is a dream for this kind of stuff. But it requires very different decisions "all the way down" to make it work outside of BEAM. And BEAM itself feels heavy to most systems devs. (IMO it's not for many use ca
16.
by mgdev 11mo ago
Yes. Obvious to anyone who writes AI garbage all day.
17.
by mgdev 11mo ago
That makes zero sense.
18.
by mgdev 11mo ago
This is, as they say, "The beginning of the end."
19.
by mgdev 1y ago
Alyssa Henry is former AWS, and an absolute monster of a leader.
20.
by mgdev 1y ago
I was trying to be ironical.
21.
by mgdev 1y ago
it's pretentiousness thinly disguised as modesty. trust me.
22.
by mgdev 1y ago
You are right, it is a good litmus test. I suppose it depends on which battle you’re choosing to fight. When I enter such orgs, I join to fix the org. And I want every tool at my disposal to do it. I love turnarounds. But they require caref
23.
by mgdev 1y ago
Profitable operations, doubling previous adjusted EBITDA. [0] While not a yet an ROI-positive takeover, on an incredible valuation growth trajectory from the post-acquisition low. Likely to be positive the minute xAI meaningfully monetizes
24.
by mgdev 1y ago
My company had what was at the time one of the largest Slack enterprise contracts. You have no idea what internal corporate battles we had to face to get our higher-ups to take us seriously at every stage of adoption, and ultimately roll it
25.
by mgdev 1y ago
Yes, when you have the notoriety, distribution, and reputation-for-insults that Linus does, you can get away with things like that, because you're selling into a culture that already understands the "joke".
26.
by mgdev 1y ago
I know a little about getting large companies to use unknown and "risky" tech. I've done it a number of times (including one I'm especially proud[0] of, and that is relevant given the Clojure connection), and built more
27.
by mgdev 1y ago
I love this project. I've been a sponsor on GitHub since late last year. But for the love of... please pick a different name. Whatever reasons companies/teams will have for not letting someone use Jank at work, don't let the
28.
by mgdev 1y ago
I wrote an app to help mitigate this exact problem. It sits between all my MCP hosts (clients) and all my MCP servers, adding transparency, monitoring, and alerting for all manner of potential exploits.
29.
by mgdev 1y ago
This is awesome. I've been in software for 20+ years now as well. One thing I've noticed is many (most?) people in our cohort are very skeptical of AI coding (or simply aren't paying attention). I recently developed a large-i
30.
by mgdev 1y ago
Local LLMs will solve this.

More ›