Every ID check assumes you can see.
I'm Team One Voice (solo)
I built Aria, voice-guided ID verification on Meta AI.
Talk through consent → licence scan → selfie → verdict. No UI needed.
Spark narrates, Wonder reads the ID, Transcribe listens.
@housecor I might be missing something here but I don't get how the dialog manages it's own visibility, it still is managed by it's parent.
I think inverting the control for <MyDialog /> will do the trick
@housecor What is your opinion on using getOr/propOr functions from utility libs like Ramda/remeda, instead of optional chaining?
e.g. const book = { name: 'JS fundamentals' }
const author = R.propOr('', 'author', book)
instead of
const author = book?.author ?? ''
@allenholub When you hide unfinished things behind feature flags, does it involve pushing incomplete feature work which might not have any tests? Or do you think we should always push tested changes even if it's hidden by feature flag?
The tradeoff of being based on primitives is people can do whatever they want. Like adding 2-way binding to @solid_js when I did everything possible to discourage the pattern.
I can't get mad about this. That's the point of the library. To put control back in developers' hands.
I managed and grew many Engineers into leaders in Startups and Big Tech.
Tech Leads, Team Lead, Staff+ "Architects," Managers of Managers, etc.
I've also reported up to EVPs, CTOs, and CEOs.
Eleven hard truths about engineering leadership 👇
My first blog on how to functionally program in JavaScript. Any feedback/comment is appreciated.
"A simple way to learn Functional Programming (FP) in JavaScript (JS)" by Akshay Harti #DEVCommunity https://t.co/Juw4saTYDo
#javascript
It’s remarkable how much better life is on a development team with this simple rule:
Code is automatically deployed to production when merged.
No more long release coordination threads.
No tedious approval processes.
No manual, repetitive, time-consuming steps.
Just merge.
Our biggest enemy is complexity.
Often, when I say that, people think only of the code we’re writing. Reducing complexity includes reducing the complexity of the entire system, however, not just the code.
@davidfowl This is exactly why F# is winning me over and has made a strong case for me to come back to .net land. @ScottWlaschin thanks for all the talks