CharlieDigital

6 ms·

1.
by CharlieDigital 3d ago
I think this is a very classic "waterfall" world view. In many cases, the problem can only be understood through many failed solution attempts. It could be because the actual problem is novel. It could be because there is a diff
2.
by CharlieDigital 3d ago
> Then you look at the code. Code that has passed review, generally. You realize that the database schema has been broken silently, and that the agent has rewritten the tests or the golden fixtures to match. I find that the co
3.
by CharlieDigital 5d ago
I'm not sure about the specifics of what Cal.com is trying to do, but interval trees [0] are a good fit and generally simplify a lot of the otherwise iterative or recursive logic for scheduling. There are some other related algorithms
4.
by CharlieDigital 6d ago
It is perhaps more accurate to say that they can meter by the second, but the billing calculation is a trailing activity.
5.
by CharlieDigital 6d ago
Politics and profits. Deepseek delivers 1 product; Microsoft delivers dozens (or hundreds depending on how you want to count it) across various domains.
6.
by CharlieDigital 7d ago
Downside would seem to be that CI tends to increase the cycle time and feedback loop and add their own cost into the equation.
7.
by CharlieDigital 8d ago
I worked for a long stint building SaaS for life sciences/pharma. A big, big part of this space is "traceability" through the SDLC. If something goes wrong, there is a long chain of liability from the final effect (a subject
8.
by CharlieDigital 23d ago
I don't think I implied there was a shortage? Rather I'm pointing out that the mid-career devs are going to struggle advancing their foundational knowledge that is gained through hard won battles and reps; they're going to go
9.
by CharlieDigital 23d ago
In my 30's I really hit my stride as a developer and system architect. Enough experience, seniority, and autonomy to own and build out large complex systems. Many, many mid career devs, I fear, will miss this window. They will become
10.
The Unexpected AI Stack: C# + .NET (Part 1)(chrlschn.dev)
2 points by CharlieDigital 1mo ago|1 comments
11.
by CharlieDigital 1mo ago
This is a 5 part series that is intentionally (hand) written to help dev teams understand how to scaffold a codebase for agentic engineering by focusing on key, underlying technical decisions and manual wiring before building with AI. Ge
12.
by CharlieDigital 1mo ago
Everyone thinks their workflow is a special snowflake. Truth is that useful dev workflows and tooling probably coalesces in a tight band. There's really no point in re-inventing the wheel over and over again at this level (the raw too
13.
by CharlieDigital 1mo ago
I'm (solo) spinning off the internal agent knowledge and observability layer used at Motion (YC W20, series C, ~40 devs). It was born out of a need to lift all devs using heterogeneous models, harnesses, and prompting styles to a high
14.
MCP Is Dead; Long Live MCP – Revisited(chrlschn.dev)
3 points by CharlieDigital 1mo ago|0 comments
15.
by CharlieDigital 1mo ago
MCP is even more important now in enterprise and thus the shift towards the streamable, stateless HTTP server implementation.
16.
by CharlieDigital 1mo ago
It isn't. MCP over streamable HTTP is just JSON RPC payload over HTTP. The internal interface for the ChatGPT app and Coded are all MCP based (stdio on local). All enterprise AI rollout is eventually going to converge on MCP as a key p
17.
by CharlieDigital 1mo ago
how many extensions do you need for browsing the web? Adblocker. Not much else because the browser already does the important work. Same with any of the off the shelf harnesses. Go build something useful instead of tweaking the minutiae o
18.
by CharlieDigital 1mo ago
Stateless MCP was already possible before this and made sense for whole classes of use cases where it helps to have a remote fleet of servers. Wrote about this back in March: https://chrlschn.dev/blog/2026/03/
19.
by CharlieDigital 1mo ago
End up building Pi extensions instead of actual product. Doesn't make sense to me, but to each their own.
20.
by CharlieDigital 3mo ago
> ...Do they just want to force you to keep busy Given functionally unlimited access to tokens with frontier models, there is really no "force you to keep busy"; it should just bake overnight. We're talking about a rather
21.
by CharlieDigital 3mo ago
Anthropic were the progenitors of the Model Context Protocol. Claude Code does not fully implement the client end of the protocol. A protocol; a literal pre-defined spec that an agent should be able to one-shot. Neither does Codex. Code
22.
by CharlieDigital 3mo ago
Pink Lady, Snapdragon, Sweetango are all probably closer to alanced compared to Cosmic Crisp. Cosmic Crisp being more tart than Sugarbee, but still definitely more sweet than tart in flavor profile IMO. Sweetango and Pink Lady are probably
23.
by CharlieDigital 3mo ago
> And you cannot keep doing high concurrent DROP TABLEs to run your large scale CRUD app In this kind of use case/design, I would assume it would make use of partitions to make this more palatable in which case it would se
24.
by CharlieDigital 3mo ago
A few things are not clear to me from reading through docs and examples: df.wait_for_schedule() How does this call work? Is it idempotent if I call it from an application? If I run it 2x with the same parameters, does it double t
25.
by CharlieDigital 3mo ago
Really good talk that goes over this: https://corecursive.com/vue-with-evan-you/ Totally worth the listen.
26.
by CharlieDigital 4mo ago
> We are shipping more features That's not really the important question; the important question: is it generating revenue . If you increase your spend -> ship more features -> no correlated increase in revenue, tha
27.
by CharlieDigital 4mo ago
Even if the laptop costs $5k and you upgrade it every year with the latest hardware and run local models (assuming your workload can tolerate smaller models at slower tok/s), you win.
28.
by CharlieDigital 4mo ago
That's because for some of these folks, the cost of the tokens doesn't have to match the value of the output; the hype from the story is all they need. Normal people have to produce something of value from that spend. So starting
29.
by CharlieDigital 4mo ago
You're a content creator; you define your revenue stream. Uber engineers do not define their revenue stream; the product leadership team does. $1500/mo of AI spend by engineers does not equate to revenue. They need to figure out
30.
by CharlieDigital 4mo ago
Consider rewiring your perspective: getting an edge doesn't really matter; the only thing that matters is will customers pay for this ? Is this a useful, valuable problem to solve? Coding faster doesn't really solve that. Uber

More ›