Russ Miller

Drupal can be a wild beast. But with the right partnership, it becomes a trusted steed. Let me tell you about our journey with SABEeX. Here's how we supported them in building, managing, and maintaining their websites over the years. 𝗕𝘂𝗶𝗹𝗱𝗶𝗻𝗴 𝘁𝗵𝗲 𝗙𝗼𝘂𝗻𝗱𝗮𝘁𝗶𝗼𝗻 SABEeX came to us with a vision. They needed a robust, scalable platform. We crafted their websites on Drupal, focusing on stability and performance. 𝗠𝗮𝗻𝗮𝗴𝗲𝗺𝗲𝗻𝘁 𝗠𝗮𝗱𝗲 𝗘𝗮𝘀𝘆 Once the sites were live, the real work began. We provided ongoing management. Ensuring smooth operations and rapid updates. 𝗦𝘂𝗽𝗽𝗼𝗿𝘁 𝗧𝗵𝗮𝘁 𝗡𝗲𝘃𝗲𝗿 𝗦𝗹𝗲𝗲𝗽𝘀 Our partnership didn't stop at management. We offered 24/7 support, ready to tackle any issue. We built a relationship based on trust and continuous improvement. ----------- So, what can you learn from this? The key to a successful Drupal project isn't just the build. It's about having a partner who can support you longterm. Are you ready to take your Drupal site to the next level? Feel free to reach out and let's discuss how we can help!

1

If you've been using git for a while, it's likely you've experienced the frustration of losing commits due to various reasons – perhaps a git reset --hard mishap or making changes in a detached HEAD state without saving your work in a branch. In this week's blog, we delve into "git reflog", a lesser-known git command that can save you from the headache of redoing lost work by helping you recover those vanished commits. Link in comments.

34

1 Comment

One of the most over-engineered and misunderstood parts of the web dev industry is rendering strategies like ISR, SSR, etc This is a good read that will help you understand with pretty graphics https://lnkd.in/gmxj9-fq

8

Most of the Small and Medium scale Business owners face prolonged project timelines due to undocumented code, and on reaching out to the original authors, they find them unavailable!! Businesses get stuck with undocumented code when the code becomes a tangled web of legacy languages and archaic practices. During this time, when businesses think of resolving this issue, the original authors are long gone and are unavailable. The years of domain and technology experiences could be used to automate workflows! In this case, Reverse Engineering needs to be performed on the software to figure out the software’s logic and understand how it works. Also rebuilding critical components using modern technologies helps the software become better. While exploring the code, carefully recording and documenting it (Code Documentation) helps everyone on the team to know what's going on, facilitating knowledge transfer and enabling efficient collaboration. #business #code #software

5

In the Agile Manifesto, the second principle is "Working software over comprehensive documentation." While we at Ascendco Health value thorough documentation, we've discovered that smaller, contextual pieces of documentation, such as focused tutorials, can be more effective. That's why I'm so excited we are enhancing Sonar by embedding short educational videos at key workflow points as part of a comprehensive onboarding system. This initiative aims to greatly benefit our clients, especially those running 24/7 operations with frequent turnover. Our goal is to seamlessly integrate educational content within the application's workflow, reducing the need for users to dive into extensive documentation. By making learning intuitive and accessible, we can help our clients stay efficient and informed. Additionally, we're having a blast using AI tools to create these videos. This not only makes maintenance easier as we enhance our software but also allows us to roll out content in multiple languages. At Ascendco, we're committed to making software that works for you, not the other way around. Our focus on working software means delivering immediate, accessible, and effective support right where our users need it. This agile approach ensures our clients can maximize their efficiency and stay ahead in the fast-paced world of healthcare.

21

2 Comments

Agents are getting really really good at programming, try this agent out: https://buff.ly/4cY7vRk I use this agent every single day multiple times a day to build functions with documentation, error handling, and type validation. It's overpowered.

1

Why agents lack practical chops? They are missing - tool awareness - tools are not yet designed for agentic use (most are designed for human-in-the-loop) - hence RPA is such a big use-case for agents (programmatic tools / API based tools) - tool discovery - no universal registry - a lot of tools are human gated (think sales teams and demos) - tool provisoning - need access to buy and self-provision tools most agentic use-cases hence showcase demos like - flight booking - calendar booking / scheduling - social media posting - content research - tools that are ungated and high degree of programmatic or standardized interfaces. Looking at building universal agents - gotta solve the realtime vision + action challenge - there needs to be a model that can see pixels and manipulate browser / computer in realtime. I see this as the waymo or tesla moment for the digital world. You need the digital equivalent of lidar for computers. This will be the base model on top of which specialized agents can emerge - fine-tune the base model with training for tool use + reasoning systems will emerge. The agent stack for November is as below - building something in agents - HMU #agents #ai

32

1 Comment

I've seen clients waste millions on overcomplicated software before partnering with MEV. It can be hard to recognize wasted spending when you're in the middle of a process, too. We had a client who was facing this scenario: • A $2 million system, bloated with features • Complex workflows no one needed • Unfriendly user interface What did they really need? Much simpler requirements. The truth hit hard when we stepped in. We stripped it down. Focused on the essentials. Delivered a solution at a fraction of the cost – just $100,000. The result? A system that did exactly what was needed. Quick, efficient, and without the unnecessary frills. The lesson was clear: Saying "no" to good ideas can be tough. But understanding and focusing on what truly matters saves money, effort, and time.

9

1 Comment

Making an API document is a pain. Making a beautiful API document is a strong pain. Mintlify solved my pain. 🎯 From the beginning of Podonos, we have built documents on our SDK (https://podonos.com/docs) for connecting AIs to human intelligence. We know how to write documents from experiences, but don't know how to build beautiful document pages. So we used Mintlify as we wrote the first line of SDK code. If you work on #B2B #SaaS #API #SDK, use Mintlify, save time, and make your docs beautiful. No, I am not affiliated with them. No reward from them. Want to show my love on the product ❤️ #Mintlify #Podonos

44

3 Comments

Few agencies without a technical lead are able to get by (and none thrive). Relying on contractors can be a double-edged sword: they bring specialized skills but often lack a cohesive vision that aligns technology with your customer’s long-term goals. This disconnect results in software bloat, where unnecessary features and technical debt pile up. The pain is real: without a consistent, forward-thinking approach, your business is at risk of compounding technical debt that will stifle innovation. Don’t let short-term fixes lead to long-term problems. It’s time to rethink how you approach technology, ensuring it supports—not stifles—your growth.

15

2 Comments

Understanding CSR and SSR - Tech 101 for PMs! 🌐 When we visit a website, there are two main ways it can show us information: Client Side Rendering (CSR) and Server Side Rendering (SSR). :: Client Side Rendering (CSR) :: Client Side Rendering (CSR) means that most of the work happens in your web browser. The browser gets a small piece of information from the server and then builds the whole page right there. Think of CSR like making a sandwich at home. You get all the ingredients from the store, and then you put them together yourself. ➡️ CSR in action: If you visit Instagram on your phone, you might see the layout before photos fully appear—this is CSR in action! Advantages of CSR [1] Feels fast and smooth once everything is loaded [2] Great for websites that look like apps and need user interaction Disadvantages of CSR [1] Takes longer to load at first and can be slow on weaker connections [2] Crawling bots may find it difficult to crawl the website :: Server Side Rendering (SSR) :: Server Side Rendering (SSR) is when the server does most of the work. The server prepares the entire webpage and sends it to your browser all at once. Think of SSR like ordering a sandwich from a restaurant. You place your order, and they make it for you before serving it at your table. ➡️ SSR in action: When you search on Google, the results load quickly and show up all at once. Advantages of SSR [1] Faster initial load time [2] Good for SEO - crawlers can easily read the information Disadvantages of SSR [1] Pages might feel slower when you start clicking around [2] Needs more server power to handle each request In simple terms, CSR is like building the page on your device, while SSR sends you the completed page right away. Liked this? Repost and share with your network. #Technology #ProductManagers

68

7 Comments

🚨 New product for developers: Supabase Cron This is one of several "modules" we're releasing to the platform. We'll drop another module tomorrow. Special shout-out to the Citus Data team + contributors. Their pg_cron extension is the core of this release. We've added integrations for webhooks, Supabase Edge Functions, and observability tooling. Check out the full blog post ↓ https://lnkd.in/d-ZWuZkH

104

10 Comments

When there is great uncertainty, there can't be predictability to any useful level. We have to reduce uncertainty to where it can be managed effectively, and we do this by running experiments... trying things. Does the stakeholder like what we've done? Does the customer like what we've done? Are we solving the problem that customers have? This puts us in the 'complex' quadrant of the Cynefin Model, where we have to try and (perhaps) fail, perhaps repeatedly, until we know enough. Yet, we still have a goal in mind and we at least know the first few things that need to get done... or the first thing we need to test to determine feasibility. Apple knew that unless it could source a ruggedized hard drive that would withstand being carried and occasionally dropped, the iPod would not be successful... so getting a commitment from Western Digital (who had been working on such a drive and was almost ready to ship) was the key decision point. The Wright Brothers knew that unless they could figure out a way to turn their airplane without 'skidding' and stalling a wing (a problem that had killed many of their inventive contemporaries) they couldn't build a safe airplane... oh, and find a lightweight, powerful-enough motor while you're at it. It all comes down to reaching decision points: do we know enough to know whether to continue, or whether to cancel our effort? In the example below (waterproofing a below-ground basement), we are going to have to continue. Therefore, we want to continue only at the pace at which we are certain of the decisions we're making. Is what we're doing working? If so, do more! If not, do something else. That is exactly what the contractor did in the post below, making 'MVP' experiments until the path to success was clear, until they had the 'Aha!' moment. So, when do we get predictability with useful accuracy? At the 'Aha!' moment. Figure out what 'Aha!' moments are needed, devise experiments to reach those moments and drive enough uncertainty out (you'll never get to zero) to where the range of uncertainty is acceptable. #predictability #forecasting #estimation #commitment #agile #planning #riskmanagement #projectmanagement

3

3 Comments

Every hour spent on manual testing is an hour your team isn’t innovating. Many developers think slow, methodical manual testing is necessary for quality. But here’s the truth: AI-powered testing speeds things up without compromising on reliability. With Sentra, your team can: • Automate routine tests. • Run continuous checks in CI/CD. • Eliminate testing bottlenecks. The result? Faster releases, fewer bugs, and more time for what really matters: building amazing software. How is your team accelerating testing? Let’s chat in the comments. #ai #softwareengineering #coding #programming #softwaretesting

2

FHIR extensions are a controversial topic. There’s a school of thought that says no individual organization should create new extensions — that only officially sanctioned or “community driven” extensions should exist. I see this as a “perfect world” Vs “real world” situation. In the perfect world, all extensions that need to exist do exist. And if for some reason a new extension needs to be created, the community comes together, talks it out, and over time a consensus is reached and a new extension is born. In the real world, businesses and organizations are building apps and solutions that use FHIR today. They have needs that need to be met today and they have release deadlines and business deadlines that do not allow the luxury of time. Which means they create extensions, making many of the decisions around those extensions themselves. This is not going to change — not in the real world. So how do we make the best of a less than ideal situation? Before creating a new extension, ask yourself these questions: 1. Are you sure you need an extension? Maybe your use case is already handled by resources or elements you’re unfamiliar with. 2. Does an extension already exist that meets your requirements? An official extension, an unofficial extension, or a full-on Implementation Guide. 3. Is the extension filling a need met in a different version of FHIR? Consider using a backport extension. 4. Has the community already addressed your need? Ask on the FHIR chat forum. Chances are someone has had your requirement in the past and a solution was offered. If none of the above leads to an answer, if there’s no alternative to creating a new extension to meet your requirement, then make the decision with confidence. Here’s a post I wrote a year ago documenting the 10 steps to create a new FHIR extension: https://lnkd.in/gXtR4Ei7

85

13 Comments

I often get the question: ”How can you offer data from providers like RocketReach, PDL etc. at half the price you'd pay directly with them?" The simple explanation: It’s all about economics of scale. As we have large volumes, we get large discounts. So we can pass the cost savings on to you. And our solid partnerships with each provider make that possible. Simple as that. What are you using for contact data enrichment? 👇

24

13 Comments

Are you using JSON:API in production? Is it any good? The only notable implementation I can find is unit.co Are there others? Please share below. The spec doesn't seem to have lived up to its expectations.

8