I had a virtual card in my @CashApp and thought it would be great to have a physical card. What they don't tell you is they remove the virtual card and you wait 14 days without access. Talked to support and they know this happens but "can't change the system".
So it looks like the --filter option doesn't run scripts *in* packages, in runs the root script against the filtered package. Still can't get basic { "dep": "workspace:*" } working. I must be horrible misaligned with this tool and I have no way to know.,.
Used pnpm for the first time for workspaces, really unimpressed. Docs are mostly pure reference, no focus on outcomes. Even had to rm -rf all the node_modules and reinstall because of install error. Really don't understand relationship between root and rest of packages
@AdamRackis Sounds like a strawman argument. The concerns are real, but equally applicable because web problem. If a user does a new search and some of the rows keys happen to exist already, are you saying the screen reader should not read those rows? See, not really so simple.
@DavidKPiano But it is used as a blanket excuse to claim high implementation complexity (over-engineering) is because of high inherent complexity in the use case. "Just trust us it's hard"๐ What I see more is the confusion of unfamiliar with complex
Another jab at dynamic typing in JavaScript. A decorator beef with an outrageous strawman and a "isn't JS bad enough" conclusion.
Decorators improve syntax () for runtime type composition. You don't always need a static compiler at your back. Test. Who punches ducks anyway?
A concise example of why I really don't like decorators that much.
IMO, decorators should have been metadata only. We already have enough ways to duck-punch JavaScript into oblivion. ๐๐ฅ๐ฆ
Used pnpm for the first time for workspaces, really unimpressed. Docs are mostly pure reference, no focus on outcomes. Even had to rm -rf all the node_modules and reinstall because of install error. Really don't understand relationship between root and rest of packages
@notphanan Great tip to lean into the browser @notphanan!
For those complaining, client-side validation is a courtesy to catch mistakes. Never trust client-side data sent to the server, period. Requirements are *not* the same and using built-in browser tech makes good sense.
@ryanflorence Perhaps not a matter of tech, but the line between pre-competitive and competitive. Whether real or perceived, these choices define a culture, product, or company in a way that makes it unique in an important way
Lot's of innovation happening in AI. Itโs important to recognize we have agency in the uses of AI we want to create. My focus is on creating AI that elevates and supports people. Personalized AI trained in spiritual traditions to cultivate understanding, empathy, and growth.
AI for the best in us. Join the waitlist for https://t.co/U8qybo4yDr, a personal AI Shaman (and our first production her at Ghost in the Machine LLC).
https://t.co/ynNFJ7fSSI
Co-organizing new meetup to create a Portland developer community for those making or interested in LLM-based apps (Large Language Models, think ChatGPT). Will have presentations and time for actual codingย surrounded by skilled and like-minded developers. https://t.co/dFBy8sBa2k
Much rings true with our experiences at @AlchemyCodeLab. I was naive in thinking creating an opportunity meant folks would always work hard to make it happen. Needs to be a financial commitment at stake, be it $500 or $5K, otherwise ISAs are too easy to walk away from.
I launched an Income Share Agreement (ISA) company in 2019.
Our company survived, but our use of ISAs did not.
Overall, I think the ISA experiment has failed and is not the revolution we hoped would transform training and education.
Here's what I learned ๐
@AdamRackis Having grown up as a dev with C# in the 00s, the perception at the time was C# was for business to build internal tools with, whereas Java was what you ran large enterprises. I think MS' penchant for lock-in at the time was also a factor, vs more open Java ecosystem