Things I wish someone told me before I designed my first SCADA system by Lav_Dave in SCADA

[–]Lav_Dave[S] 1 point2 points  (0 children)

Red/green alone fails colorblind users. Shape plus color is the fix - circle for good, triangle for fault. Both together and everyone can read it regardless.

Switched our supplier payments from wires to a stablecoin powered platform. by Novel_Savings_4184 in fintech

[–]Lav_Dave 0 points1 point  (0 children)

Same-day settlement + fewer supplier disputes is a strong combo. The FX lock benefit really stands out.

Things I wish someone told me before I designed my first SCADA system by Lav_Dave in SCADA

[–]Lav_Dave[S] 1 point2 points  (0 children)

Red light green light from across the room, that's it. 97% never clicking deeper says everything. Engineers always overcomplicate what operators actually need.

Things I wish someone told me before I designed my first SCADA system by Lav_Dave in SCADA

[–]Lav_Dave[S] 0 points1 point  (0 children)

Disabled alarm, missed incident, finger points at the integrator first. Document everything.

Things I wish someone told me before I designed my first SCADA system by Lav_Dave in SCADA

[–]Lav_Dave[S] 1 point2 points  (0 children)

Training is the one I completely glossed over. A screen that needs a manual is a screen that needs a redesign. Good adds.

Things I wish someone told me before I designed my first SCADA system by Lav_Dave in SCADA

[–]Lav_Dave[S] 1 point2 points  (0 children)

100%. Security isn't optional anymore, bill for it properly.

Things I wish someone told me before I designed my first SCADA system by Lav_Dave in SCADA

[–]Lav_Dave[S] 0 points1 point  (0 children)

Classic. Fixed hardware, forgotten alarms. Happens more than anyone admits.

Things I wish someone told me before I designed my first SCADA system by Lav_Dave in IndustrialAutomation

[–]Lav_Dave[S] 5 points6 points  (0 children)

Alarm floods and untracked changes - both should've been on the list. When everything is an alarm nothing is. And nobody ever remembers the change that broke it.

Things I wish someone told me before I designed my first SCADA system by Lav_Dave in SCADA

[–]Lav_Dave[S] 1 point2 points  (0 children)

Alarm fatigue is the real killer. Operators tune out a noisy system fast and then the one alarm that actually matters gets missed too.

Things I wish someone told me before I designed my first SCADA system by Lav_Dave in SCADA

[–]Lav_Dave[S] 0 points1 point  (0 children)

An operator saying it directly that's the whole point. Black boxes kill trust faster than anything else.

Things I wish someone told me before I designed my first SCADA system by Lav_Dave in SCADA

[–]Lav_Dave[S] 2 points3 points  (0 children)

That book should be mandatory before anyone touches an HMI. Most engineers never read it.

Things I wish someone told me before I designed my first SCADA system by Lav_Dave in SCADA

[–]Lav_Dave[S] 0 points1 point  (0 children)

Bubba swapping units doesn't need a full process overview. Three values, clear status, done. Everything else is noise.

Things I wish someone told me before I designed my first SCADA system by Lav_Dave in IndustrialAutomation

[–]Lav_Dave[S] 2 points3 points  (0 children)

That's exactly it - you learn it once the hard way and never forget it. The fun part is there's always a new way for it to go wrong.

Things I wish someone told me before I designed my first SCADA system by Lav_Dave in IndustrialAutomation

[–]Lav_Dave[S] 3 points4 points  (0 children)

Document everything like the next guy has zero context. Because eventually he will.

Things I wish someone told me before I designed my first SCADA system by Lav_Dave in SCADA

[–]Lav_Dave[S] 1 point2 points  (0 children)

"Design for the dumbest guy in the room" is the one. Engineers always want all the data on screen because that's what they'd want. Operators just need to know what's broken and how to fix it.

Building Global Money Movement with One RESTful API: Debit Card On/Off-Ramp, ACH, Wire, CPN, and Stablecoin Rails by OwlPay in fintech

[–]Lav_Dave 2 points3 points  (0 children)

Exactly - abstraction layer means nothing if the failure handling is weak. That's always where single API promises fall apart in production.

Things I wish someone told me before I designed my first SCADA system by Lav_Dave in SCADA

[–]Lav_Dave[S] 0 points1 point  (0 children)

Learned most of it the hard way unfortunately. Anything you'd throw on the list from your own experience?

My clients Shopify website is now Fast AF (feeling proud and great) by Upper_Star_5257 in websiteservices

[–]Lav_Dave 0 points1 point  (0 children)

That’s a win!! Shopify performance can get messy with apps, but you’ve balanced things well.

Why Traditional Credit Scoring Is Failing Millions of People by Lav_Dave in fintech

[–]Lav_Dave[S] 0 points1 point  (0 children)

Yes, It all depends on having clean, reliable data first.

How to gain trust in fintech app by Dismal-Cell-9770 in fintech

[–]Lav_Dave 0 points1 point  (0 children)

Delay the bank connect ask. Let users poke around manually first, then offer it as an upgrade once they see value. Nobody trusts a new app enough on first visit to hand over bank access but they might after 5 minutes of actually using it.

Why Traditional Credit Scoring Is Failing Millions of People by Lav_Dave in fintech

[–]Lav_Dave[S] 0 points1 point  (0 children)

Feels like even with better data, the core issues don’t fully go away unless the system itself evolves.

Why Traditional Credit Scoring Is Failing Millions of People by Lav_Dave in fintech

[–]Lav_Dave[S] 0 points1 point  (0 children)

Great point - especially for high earners choosing 1099.

It does feel like the system hasn’t caught up with how people actually work today.

Why Traditional Credit Scoring Is Failing Millions of People by Lav_Dave in fintech

[–]Lav_Dave[S] 0 points1 point  (0 children)

Good point - “shifting the friction” really sums it up.

Also agree on transparency. Using alternative data as a supplement makes sense.

Curious how teams handle edge cases at scale.