The amount of software that will need to be written for AI in high performance and specialized languages far exceeds your imagination and it WILL NOT be vibecoded
@KyleHessling1@NousResearch Incredible! I've been using this model with @_HermesAgent for two hours now, on my 3090 with no problems, and completing tasks regarding skills, a couple "crons" and is going amazing.
GITHUB JUST CREATED AN OFFICIAL CERTIFICATION FOR THE MOST IN-DEMAND DEVELOPER ROLE OF 2026.
It is called Agentic AI Developer.
GH-600.
And it is the first formal signal that running AI agent teams is now a recognized engineering discipline with a credential behind it.
Not a prompt engineer.
Not a vibe coder.
An Agentic AI Developer.
The person who operates, supervises, and integrates AI agents across the entire software development lifecycle.
The person who knows where agents fail in production.
The person who understands how to build autonomous workflows that do not introduce catastrophic failure modes into CI/CD pipelines.
The person every engineering team is going to need and almost none of them have right now.
GitHub certifying this role changes the hiring conversation permanently.
Before GH-600: "Do you work with AI agents?" is an interview question with no standard answer.
After GH-600: the credential tells the hiring manager exactly what you know and what you can do before the interview starts.
The engineers who get certified in the first wave of GH-600 will have a credential for a role that has more demand than supply for the next 3 to 5 years.
The engineers who wait until it is mainstream will be competing with everyone who moved first.
If you are already working with GitHub Copilot or building agent-driven workflows you are already doing this job.
GH-600 is how you prove it.
Bookmark this.
Follow @cyrilXBT for every AI certification worth your time the moment it drops.
@jsmithkempston@itZmeanuragh@ollama This is like that and it always be, generous quotas limits to generate the user base, and then silently tighten limits without any further notice. @ollama is now a joke of provider. And btw, they nevel will reply 'cause they DGAF for their customers.
@MichaelGannotti@tonysimons_@ollama Yes, there are unknowns—when you don't have details on what you've spent, the dates, the items, and the amounts, those are unknowns. Or that progress bar on your bank's website—would that be enough for you to know your credit balance?
@tonysimons_@MichaelGannotti@ollama@ollama is not a reliable service any more. Not only with the not announced and dark limit reductions this week, the inconsistent and poor service is noticeable more than ever. They should make a decision, be clear with limits and usage or let the space to others.
API call failed (attempt 1/3): ReadError
🔌 Provider: ollama-cloud Model: deepseek-v4-pro
🌐 Endpoint: https://t.co/X83YxVkDr1
Just another @ollama wonderful service
@ollama Just another day trying to get something done: Connection to provider dropped (ReadTimeout). Reconnecting… (attempt 2/3)
🔄 Reconnected — resuming…
٩(๑❛ᴗ❛๑)۶ contemplating...
It's almost impossible to work withe the @ollama services.
@GattacaHeavens@ollama Absolutely—they’re introducing more models without even ensuring stability for the ones already on the list. They’re following a master plan to ruin a business.
@ollama Instead of adding more models, you should focus on providing a reliable and efficient service; their availability issues have become all too common.