Frontend

Cypress (ala React, Front-end) is the beans…!

I’ve recently become an expert in Cypress (largely e2e testing, and for me/us largely ala React).  It is fantastic, and combines all the right techniques you know and love. I’ve spent years in Jest/Jasmine and other test/frameworks, and they lack so much.  But the reality is that testing front-end/GUI is just HARD!  It’s not like …

Cypress (ala React, Front-end) is the beans…! Read More »

New paper! Best Modern React Data Sharing Approaches

Too much confusion and far too complicated data-sharing use-cases cause many React developers to become more discouraged concerning how to share data between React components and classes while preserving one-flow direction and asynchronous updates to the UI often from server-side changes or companion components.  Even talented React developers do not truly understand ‘state’, ‘hooks’, ‘context’, …

New paper! Best Modern React Data Sharing Approaches Read More »

Special oddness with useState()/useEffect()

This is interesting/weird.  The following code does NOT work: const [refresh, setRefresh] = useState(10); useEffect(() => { setInterval(() => { console.log(“Timeout, refresh:”, refresh); setRefresh(refresh + 3); }, 1000); return list.unsubscribe; }, []); What happens is that each time the timer-interval goes off, the value of ‘refresh’ is still at 10. Why? The value goes to …

Special oddness with useState()/useEffect() Read More »

A different approach to data-sharing of server data/lists across components.

  I ran into a new challenge when I was refactoring and organizing code and components into smaller reusable pieces.  I ran into a case where HOC-like approaches wont work, but perhaps an Inheritance model will, and settled on a much different approach. Let’s discuss the use case.  Imagine your server holds a list of …

A different approach to data-sharing of server data/lists across components. Read More »

Some in-the-trenches tips/experiences with React/Jest (autotesting)

I love React, and mostly like Jest (and Jasmine and Java predecessors) but I will say: I spent a WAY MORE ENORMOUS time chasing simple debugging of jest scripts. Simple stuff. Why? I really dont know. It wasn’t designed for what I really want. It is designed for HUGE systems (like Citibank, Bank America, Amazon) …

Some in-the-trenches tips/experiences with React/Jest (autotesting) Read More »

Risk Management – Leverage Excel for fast, easily revised Risk Analysis

Product release to the customer often requires a FMECA (Failure Modes Effects and Criticality) along with the Reliability Prediction to complete the delivery package; in addition, revisions are common along with the pressure to update the Risk Analysis package quickly and accurately.  Excel provides data import, lookup, merge and formatting to automate this process and …

Risk Management – Leverage Excel for fast, easily revised Risk Analysis Read More »

AWS and PEM madness–ever lost or hurt your PEM file?

Yeah, we all have. What I went thru many of you (I hope!) wont…but ever faced that “Lose your PEM file and you’re dead” from AWS? Been there. Turns out, it is survivable. AND do you even know what the files mean? I did not. It happens. Sometimes you lose or trash your PEM file …

AWS and PEM madness–ever lost or hurt your PEM file? Read More »

Correctly using React this.state and truly being a state machine

We are all trained in React that NEVER EVER do this.setState() (or derivative) in your render() method, right? It is considered evil.  There is general fantasy that render() should be 100% benign, no side effects, 100% repeatable no matter how often re-called, right? There are two main reasons for this fantasy. One is some purist …

Correctly using React this.state and truly being a state machine Read More »