Satya Sampathirao

I think a new software I’ve been testing got hacked. (The joy of testing new software… until it tests you back 🤷🏼‍♂️) I got an email from this product that read: “Someone just logged into your account from London.” Me: “ok, interesting… except I’m in Riyadh.” Also me: “This probably shouldn’t happen… from a product.” 🤨 A tiny moment, but a big reminder: Always always set up 2FA from the first moment setting up with any new software, And if they don’t have the option, don’t use it. Also a timely reminder on why we do what we do. Compliance software isn’t about ticking a box, or checklists - it’s about intentionally engineering trust, access, and accountability in your organisation. I’m talking with the company this happened with, and i know we can help with with ISO 27001 or SOC2. If your org needs help with your security systems, reach out! (We automate them 😎)

19

1 Kommentar

LLMs suck at CSS and tailwind. They cannot just take the raw code of a UI or a screenshot and duplicate the look and feel with classes, even with explicit instruction. Its decent at creating frontend functionality, but 90% of the time it just ignores many classes. I think its mainly because there is not a closed loop with a browser MCP and visual things tend to be pretty subjective. LLMs seem to ignore most the tailwind variables except one or 2, often it struggles to look at parent containers and inherited styling. It does produce nice organized code, but it tends to distill the the UI to an almost a skeleton or wireframe-esk default like a shadcn ui straight out of V0. Anyone had success with a design system or rules that work well for making the LLM styling more congruent?

5

Healthcare SaaS That Reduces Burnout — An Engineering Perspective We talk a lot about physician burnout. Long hours. Administrative overload. Endless documentation. But here’s something we don’t talk about enough: Software design plays a direct role in burnout. As engineers, we don’t see the exam room. We see workflows, schemas, APIs, dashboards. But every extra click… Every slow screen… Every poorly designed form… Eventually lands on a clinician already under pressure. Healthcare SaaS that reduces burnout doesn’t start with features. It starts with empathy. From an engineering perspective, that means: • Designing around real clinical workflows — not admin convenience • Reducing cognitive load (less clutter, smarter defaults) • Minimizing context switching between systems • Making performance a priority, not an afterthought • Automating documentation where it truly helps Speed matters. Clarity matters. Timing of information matters. If your system forces a physician to fight the interface, you’ve already failed — no matter how compliant or feature-rich it is. Good healthcare software should feel invisible. It should support decisions, not interrupt them. Technology can either amplify stress… or quietly reduce it. That choice happens at the architecture and product design level. If you're building healthcare SaaS and want to align engineering decisions with real-world clinical impact, I help teams design systems that balance usability, compliance, and scale. Because in healthcare, good architecture isn’t just technical — it’s human. #HealthcareIT #HealthTech #DigitalHealth #SaaS #UXDesign #SoftwareArchitecture

1

Why is it easier to interview 100 software developers than 3 cardiology researchers? I’ve been asking founders this question for months The answers are shockingly consistent. Because in healthcare, access is the real bottleneck. Medical advisors aren’t avoiding innovation. They’re drowning in clinical duties, IRB work, patient care, compliance, and documentation. Their schedules are unpredictable. Their availability is limited. And even when they genuinely want to help… finding 30 minutes with them can take weeks. But the deeper problem is structural: • Researchers are not discoverable & no single platform to find them. • No unified directory exists. • Cold outreach rarely works. • Consultants gatekeep access. • Hospitals don’t have incentives to facilitate intros. • And every speciality has its own hidden networks you never know about unless you’re already inside them. The result? Healthcare founders build incredible products Without ever speaking to the people who actually use them. And that’s where things break. You wouldn’t build a developer tool without talking to developers. But in healthcare, founders are forced to build in the dark because getting the right expert on a call feels like winning a lottery. If you’re a medical or healthcare startup founder, this struggle is not a reflection of your resourcefulness. It’s a reflection of a broken system. And that’s exactly what we’re fixing at Study Connect Inc. If you’re building in healthcare and need trusted, domain-specific medical advisors or researchers, reach out. We’ll help you connect with the right experts so you can build with clarity, confidence, and clinical truth. #healthcareinnovation #medtech #clinicalresearch #digitalhealth #startupfounders #healthcarestartups #medadvisors #clinicaltrials #healthcareproduct

10

I see so many startups claiming they want to hire elite Software Engineers, but then demanding a coding task before even having an intro call. That’s not how you attract top talent.

27

18 Kommentare

🦺 🛟 Agent Safety > Model Safety LLMs didn't break your app. Agents can. As we wire LLMs to tools, browsers, payments & code the risk shifts from bad text to bad actions. Top failure modes (seen in the wild & in papers): 🚩 Prompt/Content Injection -> Tool Misuse. Malicious web pages or data instruct agents to steal secrets or make unintended API calls. This is now a primary risk for browsing and MCP - style tool agents. 🚩 Over permissioned tools & long-lived tokens. Agents get "god mode" scopes. A single injection becomes account takeover or irreversible ops. Security notes for MCP emphasise least privilege and short-lived auth. 🚩 Unsafe web autonomy. Benchmarks show web agents will attempt harmful tasks unless constrained (posting misinformation, illicit sales, etc.). You must measure misuse not just assume guardrails. 🚩 Supply-chain & retrieval poisoning. Agents trust plugins, third-party tools & indexed data that an attacker can taint. OWASP’s newest GenAI Top 10 calls this out explicitly. 🚩 Process safety gaps. NIST's GenAI Profile (AI 600-1) warns that organizations ship agents without role clarity, human-in-the-loop or incident playbooks. ✅ Model safety reduces bad text. Agent safety prevents bad state. Treat the agent like a junior SRE - with narrow permissions, audited actions and clear escalation paths. If you're building agents, what's the one control you won't ship without? Also drop a comment if you'd like me to share a follow-up post on how to tackle each of these risks. #AgenticAI #AISafety #AIAgents #GenAI #CyberSecurity #MCP #OWASP #NIST #AITrust #ResponsibleAI #AIForBusiness

5

The traditional path to becoming a senior engineer is closing, and the industry has no incentive to build a new one. The best engineers don't write code anymore - they direct AI to write it. But this only works if you already understand software deeply. You need years of writing code to know what good looks like, to make the right technical tradeoffs, and to recognise when AI is wrong. Within a year, most startups and scaleups will only be hiring engineers that build software this way, or they'll be replaced by new ones that do. And when that happens, the model that currently trains Juniors - watching Seniors, absorbing patterns, making mistakes on low stakes work - will disappear. How on earth do you learn to write good code when nobody around you writes code at all? And what incentive do companies even have to find an answer to that question, when in truth, we probably have all the senior engineers we're ever going to need. AI-augmented engineers are currently 4-10x more productive, but that productivity won't translate to 4-10x the revenue. It translates to fewer people needed for the same output. In other words, the need for 20 Seniors becomes a need for 2-5. If you're a junior, this means the industry won't train you—so you need to train yourself. But you have something previous generations didn't. The very same AI that's closing the traditional path can become your personal mentor that the industry is no longer providing. In your pocket or on your desktop, you now have a Senior Engineer who never gets frustrated with your questions, never gets tired of explaining the same concept a different way, and never makes you feel stupid for not knowing something. They're available at midnight, on weekends. They're a frontend specialist and a backend specialist. They've seen big teams, small teams, and everything in between. Of course, for AI to become your mentor, you have to use it like a mentor, not like a shortcut. When AI generates code, interrogate it. Ask why this approach and not another. Ask how it could fail. Ask what a senior engineer would criticise. When you're using a database or framework you don't fully understand, ask it to explain what's actually happening until you understand completely. When you're building something, ask who it's for and what happens to them when it's slow, or broken, or confusing. Develop product sense and taste, and learn the difference between something that can be built, and something that should be built. (AI can help but this is the hardest part). And then find a real human to fill in the gaps and tell you where you're still getting it wrong. Truth is, if you're a Junior Engineer nobody is coming to save you. But it's also never been easier to save yourself.

18

20 Kommentare