ravimohan.bsky.social
Generalist Software developer based in Sydney, working with c# | angular | aws at work and c# | nextjs | fly.io for the side. Technology Agnostic and love to play with all languages and tools. https://github.com/sravimohan
273 posts
378 followers
491 following
Prolific Poster
Conversation Starter
comment in response to
post
MS did this with IE in the early days of the browser and rightly got slammed for it. But it is not the same in this context, is it?
comment in response to
post
And what if they were to only make available, certain LLM features only to their own solution.
comment in response to
post
GitHub copilot is doing this. But it is going to be very interesting to see the competing solutions directly from OpenAI.
comment in response to
post
You can mitigate the risk somewhat by not totally relying on one provider and have the ability to switch to another provider.
comment in response to
post
It IS true that Builder .ai hired ~700 engineers in India. These engineers acted more like forward deployed engineers as I understand.
The company had an AI team building Natasha spread across the US and EU and they built a real and functioning agent.
comment in response to
post
For small to medium-sized companies, enabling teams to build their infrastructure by establishing best practices, a defined tool stack, and common patterns is often more effective than attempting full-scale abstractions.
comment in response to
post
Finding the right abstractions in organisation level tooling, takes skill, effort, and ongoing commitment. This is not necessarily specific to platform engineering. The same applies to developing shared libraries and packages.
comment in response to
post
Does this mean ongoing feature parity with core react or will diverge?
comment in response to
post
Does that mean, there are enough people building dotnet with vs code making commercial plug-in’s viable?
comment in response to
post
Is the build step still happening or is just becoming transparent?