I've been messaging my wife who's out of town all day and wondering why nothing was going through. How does it make sense to ban Telegram. It's one of a million ways you can share things.
India’s IT ministry banned Telegram for one week because some users shared leaked exam questions.
This punishes 150M+ ordinary Telegram users in India — not the insiders who leaked the exam materials.
And the ban hasn't stopped anything. The leaks just moved to other apps.
We're starting to work on using Linear as a shared memory database for our apps. As well as building workflows to automatically track plans and decisions into each project, track triaging learnings and daily work logs. As the volume of work goes up, tracking context is key.
Deadlock is such a great game. Icefrog and Valve really know how to make fun games. Haven't played Dota 2 in forever but it feels like FPS version of that quite literally. People talk about items in the game based on their Dota equivalents.
@linear Please add a search_document MCP tool that does semantic search across documents. I want to use the documents but it's token intensize to search for stuff.
Claude Fable is ripping through my credits on a project I set it on and for some reason ignoring my messages asking what it's done. Going to leave it at it and see what we get at the end.
@Shpigford And for the database we're using Planetscale. Render let's you use AWS PrivateLink so they are connected on a private network which is pretty good to keep down egress costs and improves latency a bit on top of being more secure.
@Shpigford As to agent friendly. They have an MCP and the whole setup builds out from a render.yaml file including multiple services, redis and Postgres. So I've been able to speed up the process a lot using AI.
Step 1 in moving off of @heroku which we've been using for more than a decade. End of an era. I wish more PaaS tools copied some of Herokus UX because it's honestly pretty good.
@marckohlbrugge The tests after in general are not very good because AI can end up trying to fit the test to the code and get a pretty useless result. Telling it to write the failing test and then only make the changes required to pass it works well.
opinion: this is a detrimental change for merchants.
part of what makes building storefront apps easier than before is metafields. it has its issues (like inconsistent caching), but it also allowed us to scale up to serve merchants at insane scale. and merchants + their dev teams love it too. so much so that they explicitly look for apps that expose - and heavily rely on - metafields.
this change effectively forces us to build our own infrastructure, stumble and learn how to do it right along the way.
which is not bad, in isolation, but considering that merchants need apps to be as performant as the work they're putting into their storefront, this means merchants will struggle with building the right experience for their customers.
infra cost to serve this - as a business - is probably something else to think about. i'm going to assume it's not significant for now.
some will see this as a "skill issue". well maybe so, but i'd much rather use our time to expand what our products do.
that's not to say i don't get why they did it. it seems like the decision wasn't easy. the way it's being done though doesn't feel right - more so for merchants (the actual end customer), than anyone else.
@FORSBERGtwo@kirplatonov Given I build an app that heavily uses metafields to provide functionality. This doesn't entirely make sense because either you:
- Split it up but you're still loading the same amount of data
- Load it from your own server through API and that will be even slower