@boardyai building AI that turns messy real-world inputs into workflows, like handwritten grading across 13 languages with real teachers waiting. Boardy Pro would be huge for this
My take.
There are a lot of parallels between frontier model companies and drug dealers.
They get you started for free, then they charge for it. Those who are training models, I feel they are optimizing for token output instead of results.
Either Sam Altman reads The Pragmatic Engineer (I wrote about this in detail exactly one week ago for paid subscribers) or I'm just a week ahead to what he also sees!
Google is raising $80 billion for AI infrastructure.
Meanwhile, in Pakistan, massive electricity costs—higher than anywhere else in the region—prevent us from being remotely eligible to even be bottom feeders
Google used to show your search results down to the millisecond. It was their way of proving how quickly they could process the web.
With Gemini 3.5, Google is going back to those roots. Speed was the MOAT then, speed is the MOAT now.
@mitchellh I have this in my prompt.
"An good engineer understands that it all a tradeoff. Please use verbiage that is less cock-sure. My PTSD gets triggered."
It works most of the time.
Google Jeff Dean says bigger context windows alone are not enough
What matters is staged retrieval: lightweight mechanisms that narrow a trillion tokens down to 10 million, then to the million you actually need
"you don't need a trillion at once, you need the right million"
I know there is some overlap between open source and anti-AI activists, but I have a hard time reconciling it. My million+ open source LOC were always intended as a gift to the world. Yes, I would make arguments about how it would strengthen our communities, and the GPL would prevent outright exploitation by our competitors, but those were to allay fears of my partners to allow me to make the gift.
AI training on the code magnifies the value of the gift. I am enthusiastic about it!
Some people do look at open source as a tool for social change, career advancement, or reputation building, but those are all downstream of the gift.
New startup. You're the first infrastructure hire.
CTO wants the platform ready in 3 months.
Option A: Kubernetes from day one
- Future-proof
- Steep learning curve
- Longer initial setup
- Easier to scale later
Option B: Simple ECS + Fargate
- Faster to production
- Less operational overhead
- Might need migration later
- AWS lock-in
Option C: Just EC2 + Docker Compose
- Fastest MVP
- Manual scaling
- Technical debt guaranteed
- Cheapest short-term
Team size: 4 developers (none with K8s experience)
Expected growth: 10x users in 12 months
Funding: Series A secured
What's your recommendation?