Colin Devroe

Gracefully Handled the time/Date mismatch in Revlead without any package or plugin. Since the app was depending a lot on the DateTime.now() (Device Time). Thats where the features are disturbed and data is disrupted. How i did it. 1. Deployed supabase edge function returning server time,. 2. Converted Server Time and Device Time to UTC. 3. Find the time difference and set the error margin (in minutes). 4. If difference is greater than margin then time is Incorrect. #flutter #dart

13

So which models produce HTML that has the least accessibility errors, and at what cost? Mapped it out here (bottom left is the best). This is helpful for understanding which models are most compliant for those with disabilities and do it efficiently. Qwen and Gemini 2.5 Flash lead the pack. Hat tip to Ben Ogilvie for pointing me to this: aimac.ai

55

2 Comments

WordPress sites are faster when they have images with smaller file sizes. That's not the only metric of course, but it can be a significant one. Large image sizes can also fill up your drive space on your host. There are several ways to mitigate this, ranging from hand crafted image to paid services to magically do it for you. I found a great new plugin that solves many many of the problems we currently have with getting this process right. It's called Cimo, and I did a blog post about it. Check it out. https://lnkd.in/gMgWsDnj #WordPress #Performance #ImageFormats #WebP

20

1 Comment

ICYMI: In our JavaScript for AI session with Sitebulb we covered what to audit for LLM accessibility. Similar to a tech SEO audit that reviews accessibility issues on your site for Google & other search engines, an "LLM Accessibility Audit" should include: 1) a review of what content, on what pages, is only available in rendered JS (and, therefore, NOT accessible to most LLMs) 2) a review of what information is available - that you might not realize - in response HTML (e.g. embarrassing, jokey, confidential, or private info) (It's not too late! Catch the recording here >> https://lnkd.in/dBUQ8GkK)

61

2 Comments

Interoperability isn’t just a technical problem, it’s a human one. When we talk about interoperability in verifiable digital credential systems, too many conversations stop at technical standards, APIs, and data formats. Yes, these matter, but they’re only one layer of the stack. Real interoperability lives in the social and cultural systems that surround the technology: ✨The data models that determine what gets recognized and what gets left out. ✨The governance frameworks that shape who gets a seat at the table and who doesn’t. ✨The trust we build not just in the tools, but in the communities maintaining them. ✨The transparency to say when something isn’t interoperable, and the humility to fix it. Too often, vendors talk about interoperability as if it’s something you can solve with a spec sheet. Yet, if we’re serious about credentials that can move across systems, sectors, and societies we have to care as much about people, process, and power as we do about protocols. Interoperability isn’t just about systems talking to each other. It’s about humans agreeing on what’s worth saying. #DigitalCredentials #Interoperability #Trust #OpenStandards #Governance #DigitalIdentity #EthicalTech #PeopleFirst

31

2 Comments

Don't believe the BS that you can use Claude Code for free. Ollama recently made their API compatible with Claude Code. Many creators quickly jumped on the opportunity to farm engagement with the hook: "You can now use Claude Code for free!" My thought? Claude Code without Opus 4.5 is not Claude Code. Period. But this is exciting news. Not because I can use Claude Code for free, but because I see an opportunity to optimize costs by delegating easier tasks to local LLMs. The key question is: what tasks can local LLMs handle? I tested out 7 local LLMs. In this post, I will explain the BS and share my 1st experiment. -- Why the BS? Claude Code has been praised as one of the best AI tools by its users, not only for coding but for many other tasks. But the price feels steep to many. The $20/month plan is not enough for any serious work. You need to at least subscribe to Max 5x ($100/month). Many heavy users, including me, subscribe to Max 20x ($200/month). It’s a steal. But still, many were eager to try it but aren't ready to pay. Ollama's recent announcement means you can buy a Mac, a Strix Halo, or a GPU and use Claude Code for "free" with local LLMs. It’s appealing, as it is a one-time investment, and you can use the machine for other purposes. Creators are leveraging this opportunity to farm engagement. But the reality? Claude Code without Opus 4.5 is not the same Claude Code we praised. Local LLMs are far less intelligent. -- But for those who understand the difference, we see an opportunity to optimize costs by delegating some easier tasks to local LLMs. I'm interested in finding out what tasks local LLMs can handle. This is my typical flow when using Claude Code. This is for coding, but I have similar flows for marketing and content creation. 1. Research and planning 2. Create PRD and implementation plan 3. Break plan into bite-sized tasks 4. Implement + review with reflection pattern 5. Final review with agents 6. Final review and QA by me Based on my quick tests, we can forget about asking local LLMs to do research and planning. All of them failed at a simple instruction: "Visit https://learnparrot.ai/ and tell me about the website." So, I think the most viable use cases would only be (4) — implementation + review loops. While it looks like a very narrow use case, it is where we burn a lot of tokens. So I think it is worth a try. The main selection criteria for this will be instruction-following capability. One very common task is to refer to code samples or templates to code a new feature or page. This is a good test of instruction-following. So, I crafted my first test: - Used Opus to create HTML that I can screenshot as a LinkedIn carousel to display info for each model. - Turned one of the pages into a template and deleted the rest. - Asked each LLM to refer to the template to code its own page, given its specs. Swipe the carousel to see the results. Who would you hire? #LocalLLM #ClaudeCode #VibeCoding

20

10 Comments

Web editors shouldn't waste time wrestling with HTML — they should be busy bringing great stories to life. At Smith College, we completely flipped the Drupal experience: 🌟 Editors create visually, joyfully, and in real-time — without developers, HTML, or CSS. 🌟 Content workflows now rival the best consumer-friendly platforms (think Wix and Squarespace), giving editors total creative freedom and control. 🌟 The real innovation wasn't technical — it was strategic. We replaced gatekeepers with trust. Editors went from frustrated to fearless. When you trust your content creators, your website transforms. 👇 Learn how Smith College editors became passionate advocates of their website — and #Drupal: https://4ktch.in/smith #DrupalRevolution #ContentStrategy #EditorExperience #DigitalTransformation #HigherEdWeb

48

4 Comments

When Claude Opus 4.5 generates an Artifact, it doesn't just render a React app. It incorporates the business, files the LLC paperwork in Delaware, and closes a Series A funding round before the UI finishes rendering.

182

19 Comments

Vibe Coding is picking up steam. What does this mean for development costs? I'm curious about the real-world implications. For entrepreneurs and small businesses, website development has always been a significant investment. Even basic implementations require serious budget consideration. Vibe Coding promises faster development cycles and reduced complexity. That sounds compelling. But I want to understand the practical impact. Questions: • Will this democratize web development for smaller budgets? • How does code quality compare to traditional development? • What happens to the development timeline - weeks instead of months? • Does this shift the cost structure from build to maintenance? The marathon runner in me knows that shortcuts in training usually show up on race day. But genuine efficiency improvements? Those can be transformational. For the developers and agency owners, what are you seeing? Have you experimented with Vibe Coding approaches? What's the real performance versus the promise?

11

7 Comments

Brightcove has released its 2026 product roadmap in a detailed, extensive blog post [https://lnkd.in/gYPZ7mhH]. I've had the chance to see some of the new features and provide feedback, but more importantly, Brightcove has spoken with many customers about how they want to see the platform evolve. The roadmap includes several new features and improvements across Brightcove's two core tracks: AI Innovation and Quality of Experience. They include: - Native real-time captioning, improved accuracy and expanded language support - Accessibility and compliance to meet WCAG, ADA, and European Accessibility Act requirements  - Auto-generated video chapters and AI-assisted live clipping - Full Video Cloud redesign - Web/mobile player and SDK upgrades for iOS and tvOS - Expanded publishing flexibility with native support for TikTok, Instagram, and Facebook Reels - Improved visibility and tracking for user activity logs and advertising metrics - New search functionality within Live Channels In addition, they are enabling new AI workflows to enhance the viewer experience, new user activity logs, advertising-improved Google-Tag-Manager metrics, and initiatives to improve Brightcove Player and SDKs. You can read the blog post here: https://lnkd.in/gYPZ7mhH - #SVOD #AVOD #cloudvideo #streamingmedia #videoworkflow Bending Spoons

82