I'm not that familiar with TypeScript/JavaScript - what would be a proper way of handling complex logic? Switch statements? Decision tables?
1,462 karma · joined June 26, 2014
How do you simultaneously revoke all credentials of all your accounts spanning multiple services/machines/users?
The problem is old (and even not so old) apps don't expose those APIs so interactions like UI automation on Wayland is limited, if not impossible. I'd love to grant a specific permission just for selected GUI apps, but I can't because they don't support it.
There's a reason why RPA software on Wayland is limited to web apps inside a browser. Or something extremely janky like taking screenshots of the entire desktop and doing OCR. But then you can't interact with unfocused apps.
Restaurants don't even need a dedicated take-out ordering section since delivery apps cover that too.
I rarely see Squarespace or Wix.
If you want to replicate, you should try the same question on the same custom LLM, not Gemini.
Then the third user shows up. They have an odd edge case and the code isn't working. Fixing it will take some back and forth but it still can be done in a respectable amount of time. All is good. A few more users might show up, but most open source projects will maintain a small audience. Everyone is happy.
Sometimes, projects keep gaining popularity. Slowly at first, but the growth in interest is there. More bug reports, more discussions, more pull requests. The author didn't expect it. What was doable before takes more effort now. Even if the author adds contributors, they are now a project and a community manager. It requires different skills and a certain mindset. Not everyone is cut out for this. They might even handle a small community pretty well, but at a certain size it gets difficult.
The level of communication and collaboration required can only grow. Not everyone can deal with this and that's ok.
As for anthropomorphizing software - we've been doing it for a long time. We have software that reads and writes data. Originally those were things that only humans did. But over time these words gained another meaning.
I don't have resources to set up my own lab. I don't even know if the manufacturer will sell a dozen or so vaccines directly to me. So can't even do a basic stoichiometry on my own. And forget about me setting up a trial with actual people - I have no idea where I could begin to make it possible.
If by research you mean reading already published papers, that's literature review and I wouldn't call that a research. But because doing my own experiments and trials is out of question, I'm willing to settle for that.
Reviewing published papers comes with its own set of problems. A lot of papers are behind paywall and I don't have money for the ongoing journal subscriptions. I suppose I can rely only on open journals and pre-prints but that's not all of them. Messaging the authors directly is also an option but it's doesn't scale well and takes time.
Suppose I get my hands on a couple of relevant papers. How can I be sure what's written there is actually correct? It would be nice if I could double check against the raw data, but often that's not available. And at best all I can verify is that the paper's content matches the source data. I can't verify the data itself. At some point I have to trust the authors. Not to mention I don't have access to the data from research that wasn't published, for example because the experiments didn't show anything novel.
But that's fine. Nothing is perfect and after hours (if not days) of reading and playing with data I came to a conclusion that I'm happy with. Of course I have to review it again in a few years. The new research will be published by then. Maybe they will discover something different and I have to review that too.
Overall, I spent a lot of time and it was exhausting. Diligently reading and cross-referencing all that data is mentally taxing. I can't complain though because I've learned something.
There's one problem though. All of that effort was about just a single vaccine. But there's more of them. For other diseases too. And there are other problems I'd love to research. Windmills. Microplastics. Glyphosate. Dozens of types of food. Economic theories. How can I research all of that in a timely fashion?
I'm genuinely asking because I want to. I realize there will be trade-offs involved, but all of them are either relying on someone else (which we try to avoid) or won't be deep enough to form an informed opinion. And I'm not happy with either.
> Quality Plans
> 6.1 The Supplier shall develop, within [insert number] Working Days of the Effective Date, quality plans that ensure that all aspects of the Services are the subject of quality management systems and are consistent with BS EN ISO 9001 or any equivalent standard which is generally recognised as having replaced it ("Quality Plans").
The Short Form Contract also have optional ISO 27001 or Cyber Essentials (which is, uh, an adventure on its own). But there's also an option for no certification required. It depends on the contract.
But yes, you're right. Dealing with requirements takes time and experience and you likely need a dedicated person (or team) to deal with it.
A prompt to generate similar output would be a good start.
I could, I just choose not to and direct my interests elsewhere. Those interests can change over time too. One day someone with Tailscale can decide to explore Wireguard. Similarly, someone who runs their own mail server might decide to move to a hosted solution and do something else. That's perfectly fine.
To me, this freedom of choice in software engineering is not disheartening. It's liberating and exciting.
n.b.: the above quote is from The Matrix.
TCAS = traffic alert and collision avoidance system
grep is all right, but sometimes I need to tease out a complex data relationship.
What kind of data would satisfy you? I imagine any data coming directly from YC would be untrustworthy and third-party data would be incomplete (say, it wouldn't catch content removed before it's published).
Is there a similar data set for other private platforms?
I imagine reviewing all the code for all the packages for all the published versions gets really expensive. Who's paying for this?
The last time I looked into it, I found out I would have to deal with each compositor separately. On top of that, the target apps would have to be written with the new API in mind.
That's pretty interesting. Can you tell us more what kind of problems your software solved and how you convinced them to move from the spreadsheets?
I tried something similar (in another industry) and it's a mixed bag. Companies often straight up refuse to move past the spreadsheets even though it creates a significant backlog on their side.