I suspect, since this is HN, you're looking for something more open and hackable. But you might want to check out SIG Connect if you just want something that works out of the box.
Sorry I can't get into "how it works". Feel free to DM me for any questions.
One thing I see missing from some other replies to your comment is a discussion of determinism. That is given the same input, always produce the same output.
Determinism is often valued in safety critical systems. The system can't work _sometimes_. The system can't even work correctly _eventually_. It must produce the desired result in the time allotted. Actuating the thing 20ms too late could be as bad doing it incorrectly depending on the application.
I'm no ML expert, but that seems to be a problem for those types of solutions in some spaces.
We’ve had some success with similar methods. In addition to the simplicity(it just “plugs into” the existing board), it’s nice to get metrics on the bottlenecks happening on the product side of things. If we can show that it historically takes 2 weeks to refine requirements, we can tighten up our estimates and shine a light on potential problems occurring there. If you only have metrics on the dev work, the more business-minded folks tend to focus improvements only on what they can measure.
I’ve also found that folding product workflows into the Kanban board gives the team more visibility and ownership over that end of the pipeline. We can observe how those items age before it ever gets to the dev team and swarm to fix things as a team earlier in the process.
I would love to have an AWS expert handy at all times, so I tried to upload all AWS documentation using this: https://docs.aws.amazon.com/sitemap_index.xml. I can no longer use the site, so I suspect that busted something.
In hindsight, that was not cool and I'm sorry about it.
I really like this tool (text-based, yes!), thank you for creating this! I'm working on creating estimates at work and it is a real struggle. Creating estimates with a range and probability is awesome because it reflects the uncertainty inherent in any estimate.
It would be nice if the system showed its work somehow. In addition to giving me comfort as the estimator, it's nice to show the person on the receiving side the my inputs and help them understand process being applied. I looked for some docs on this, but I couldn't find anything. At the very least, it would make a great blog post!
Another bit of feedback while I'm here. I tried using {1-2d} for days and {budget 10d} for budget. It seemed to work for estimates, but not for the budget. Looked for docs on the syntax, but I couldn't find it and it all the examples in the quickstart use hours.
P.S. I'd love to talk to you about how I'd like to use this if you're looking for more feedback / collaboration. This has legs!
You can conditionally deploy resources by setting the count on most resources. So you can have an environment variable with something like has_cache. Then in your terraform use a ternary or something to set the count to 1 if has_cache is true and 0 if it’s false. I have done this without much fuss.
I’ve been reading the Economist digitally using their app for years. They had a few issues over the years - I think they prevented copy/paste for a minute. I was pissed about that.
But now I love the app. The typography is decent, they support light/dark themes, you can play human-read audio of every piece individually, etc.
I know you might be looking for something more DIY, but this simple service has been really refreshing to me: https://bearblog.dev/
It’s so simple and easy. If you want to focus on content instead of tinkering with your blog endlessly (like I have done several times), this is a great option.
> Instead of storing the data on-chain, NFTs instead contain a URL that points to the data. What surprised me about the standards was that there’s no hash commitment for the data located at the URL.
I've been recently exploring the Solana[0] NFT ecosystem. The situation is similar there and I admit it took me by surprise at first. However upon further inspection, there's more to the story.
As others here have mentioned, most serious ETH collections address this problem using IPFS. But on Solana, Arweave[1] is a popular solution. I had never heard of Arweave before and it's a seriously cool concept. In a nutshell, it's a system that allows you to pay for 200+ (potentially much more) years of storage _up front_. I won't pretend to understand it all, but it effectively pays the network of miners to host your assets indefinitely. The up front payment - which is steep when compared to traditional hosting - provides a "sustainable endowment" for these mining rewards. This allows you to guarantee that the asset will be available without counting on some random hosted storage system.
It seems that NFTs are the main use case for such a system at the moment. However I can imagine other use cases could emerge for an answer to this question I never really thought to ask: "How can I ensure that an asset is hosted "forever?" Interesting problem and an interesting solution that a network like this - with its marriage of decentralized technology and economic incentives - is uniquely poised to address.
I often find it useful to relate the Web3 movement to the introduction of the internet. What problem was did that attempt to solve?
The internet solved problems that were only apparent in hindsight. The same could be true of Web3. It could also be nonsense, but I don’t think so. The absence of a particular problem to solve doesn’t necessarily render it useless.