181–190 of 265 posts
Been tinkering on this Olmsted-inspired map of all the trees in NYC for a long time - just added some more features (seasonal colors and better search/filtering) recently.
If you're in NYC, try finding some cherry blossoms near you: https://exploretrees.nyc/?species=cherry
tsdevstack — Infrastructure as Framework An open-source TypeScript microservices framework I've been building solo for the 8 months. It generates and deploys an entire production-grade cloud infrastructure (VPC, gateway, WAF, observability, CI/CD) from a single config file. Multi-cloud across GCP, AWS, and Azure. Just shipped v0.2.0. Built it because I got tired of writing the same Terraform, gateway config, and CI/C…
Seems like your approach is a bit more "batteries-included" but I'd curious for your thoughts on the differences.
Also working on a journaling app but it’s still in the works.
I have realized that playing board games with other people makes my mental health better and started work on a community platform and at some point physical space to connect: https://GamesAgainstLoneliness.org Also working on a journaling app but it’s still in the works.
Also, since you are in Germany, have you considered going to the next Spiel Essen board gaming convention? I haven't gotten the chance to go yet, but I imagine it would be a good way to make a lot of connections and get your gaming group known to a bunch of people.
Also, boardgamegeek/rpggeek are places where you could get your name out there(just in case you don't know about those).
Lastly, not sure how common board gaming shops/communities are over there but they are quite popular and common over here in the US so if there is any extra stuff you need to know regarding gaming shops you could probably get a lot of useful info by googling (random big US city like New York City) + "board gaming shop". Star City Games is a super popular one here and they have a high quality website that might be worth studying.
Best of luck from an aspiring board game designer!
Built a SQL interface for DynamoDB. I was tired of constantly trying to find workarounds for querying on a NoSQL database, so I built a direct interface for DynamoDB, which I'm calling DynamoSQL. With it, you can use standard SQL (even JOINs) on DynamoDB. I'm really excited about it, and I'm starting beta trials this week. https://dynamosql.com
So instead of people using the right tool for the right job and learning single table design when using DDB, they are going to use the completely wrong tool. I can just imagine the sub optimal in memory aggregations and expensive use of read and write units.
That said, not everyone using DynamoDB has the luxury of designing perfect access patterns from the start. Real production tables are often messier than the textbook examples. And for analytical or exploratory work (e.g. understanding your data, debugging a production issue, running ad-hoc reports) a slightly more expensive read is a reasonable trade-off for writing SQL in seconds rather than SDK code in minutes.
I appreciate the feedback. The cost visibility question is something worth being clearer about in the docs.
The goal is to make every recipe foolproof on the first try, similar to when you walk into a restaurant and just pick what you want to eat without thinking about the details. The goal is to have the same experience, just pick what you want to eat, with recipes that tells you exactly what to do with no magic involved.
Technically it is probably the most advanced recipe app ever made. The database is a huge graph that captures the relations between ingredients and processes. Imagine 'raw potato'->'peeled potato'->'boiled potato'->'mashed potato'. It is all the same ingredients but different processing. The lines between the nodes define the process and the nodes are physical things. Recipes are defined as subsets of the graph. The graph can also wrap around into itself, which is apparently needed to properly define some European dishes in this system. The graph also has multiple layers to capture different relationships that are not process related.
Why was it designed it in this way? Because food/cooking is extremely complex. This design is the only way I have found that can capture enough of these complex relationships that the computer can also 'understand' what is going on.
My favourite thing about this is that each recipe is strictly defined in the graph. If the recipe skips a step, or something is undefined, the computer knows that the recipe is incomplete. It won't ask you to do 10 things at the same time and then have something magically appear out of nowhere. It is like compile time checking but for recipes.
It also enables some other superpowers, for example:
• Exclude meat part of the graph = vegetarian. Same thing works with allergies.
• Include meat part of graph = only show me recipes that contain meat.
• Recursive search: search for 'potato' and the computer will know that french fries are made from potato. It can therefore tell you that you could make the hamburger meal, but you will need to complete the french fries recipe first, which should take 60 minutes.
• Adjustable recipe difficulty (experimental): It knows which steps can be done in parallell, and which can't based on how the nodes connect. A beginner can get a slower paced recipe with breathing room between steps, while someone more experienced can do a faster pace and do more things in parallell.
If I knew what it would take to build this, I would never have gotten started. I completely underestimated the complexity of the problem I was trying to solve. But here we are, and now it is basically done and working.
The website is slightly outdated but captures the key points from a non-technical point of view, and you can enter your email and get notified when it will launch in your country.
tsdevstack — Infrastructure as Framework An open-source TypeScript microservices framework I've been building solo for the 8 months. It generates and deploys an entire production-grade cloud infrastructure (VPC, gateway, WAF, observability, CI/CD) from a single config file. Multi-cloud across GCP, AWS, and Azure. Just shipped v0.2.0. Built it because I got tired of writing the same Terraform, gateway config, and CI/C…
Very cool! Have you seen https://encore.dev/ ? Haven't used it personally but I saw it on HN last year and have been meaning to try it out. Seems like your approach is a bit more "batteries-included" but I'd curious for your thoughts on the differences.