Show HN: I built jq-like scriptable tool to query CSV and JSON with SQLite https://ift.tt/vBctFk9

Show HN: I built jq-like scriptable tool to query CSV and JSON with SQLite https://ift.tt/ElGAT0F February 24, 2024 at 11:49PM

Show HN: Little Fixes – a spatial forum to improve your city https://ift.tt/xbsDEVQ

Show HN: Little Fixes – a spatial forum to improve your city https://littlefixes.xyz/ February 24, 2024 at 12:24AM

Show HN: Flash Calendar – performance focused calendars for React Native https://ift.tt/tL3Gmio

Show HN: Flash Calendar – performance focused calendars for React Native Hi everyone! I just open sourced my first package: a new way of building calendars in React Native. It uses Shopify's FlashList component as its foundation, along with React optimization techniques to re-render only what changed. I'm using in production for my side-project and it behaves incredibly well. I hope it can be useful for more of you! Bests, Marcelo https://ift.tt/98d1HnO February 23, 2024 at 09:15PM

Show HN: Learn Game Theory Optimal Poker Preflop with Spaced-Repetition https://ift.tt/yuU9Waw

Show HN: Learn Game Theory Optimal Poker Preflop with Spaced-Repetition Hi HN, Sharing my poker preflop trainer product, a subset of my Live Poker Theory project. https://ift.tt/vb6zDm9 Live Poker Theory helps translate complex poker solver strategy to actionable strategies while playing and aims to make studying poker more efficient and more fun. While I usually try to focus on sharing it in poker communities, I saw a few poker articles frontpage this site so I figure it doesn't hurt to share it here. In case you don't know, before 2015 most poker software could only calculate "all-in equity" - if there was no game tree and players could only go all-in or fold. These days, solvers can calculate the full game tree, with a lot of assumptions, and we can use them to generate preflop charts. Sometimes people call this GTO (game-theory optimal) though I prefer the term "theory-based" to recognize how frequently you want to diverge from equilibrium even if you've studied it. Preflop refers to the first two cards you're dealt and the first round of betting which is a very fundamental street. Preflop is a good example of where I find it useful to study equilbrium even if you might diverge in practice - for example, once you understand how often a player should be 3-betting you (re-raising you after you've raised), if you know someone doesn't do it with hands like Ace-Five suited, you can fold hands you'd otherwise continue with. But it's helpful to understand a strong player should frequently be 3-betting Ace-Five suited. Some other info that might be helpful: 1) Rake refers to whether the "house" removes money from the pot which happens at most low-stakes games. Higher stakes games tend to be "time" games where the players simply pay an hourly fee so there's no effect of rake on the game itself. That also may be true at an unraked home game. 2) A straddle is an optional third blind that's often strongly encouraged as something everyone at the table does, and of course the charts are different with that third blind Spaced-repetition is something that only my trainer does, while it's a well understood concept on places like Hacker News, it's not well understood by the poker community. Even if you plan to make adjustments against certain players, there's good reasons to memorize a preflop chart. It helps you stay disciplined if you're "tilted" if you know what a reasonable baseline strategy is. It also helps you clearly define your postflop strategy, both while doing solver work and while playing. For examlpe, frequently the best river bluffs are the "bottom of our range", since our worst hands beneift the most from our opponent folding. But the "bottom of our range" is only clearly defined if our range is clearly defined, so if you've memorized your preflop range, you'll have a better understanding of your overall strategy postflop. One last important note, the charts are based on a 2.5x raise, so in a 2/5 game, a raise to $12, which is fairly rare to see in practice. If you have the solver raise 3x or 4x, the overall strategy is much much tighter. While this is more correct against perfect opponents, in practice frequently we're against weaker opponents and we'd rather play a looser range since we'll have an advantage postflop. By studying 2.5x, we keep a more reasonable loose range but still let the solver give us a reasonable baseline of hands to play. Currently, you can try out Tournament, 50 Big Blind stack depth, Raise First In without an account. With an account and for free, you can study cash or tournament "Raise First In" (whether to raise or fold if it folds to you), "Vs Open" (whether you raise, fold, or call if someone raises before you act), for free, for cash or tournaments. I have paywalled only cash game BB defend (if someone raises when you're in the big blind) for $10/mo or $59/year. I'm also actively adding more preflop charts, developing postflop content with spaced-repetition and a native mobile app. https://ift.tt/vb6zDm9 February 23, 2024 at 01:06AM

Show HN: Strada – Cloud IDE for Connecting SaaS APIs https://ift.tt/miTBFJE

Show HN: Strada – Cloud IDE for Connecting SaaS APIs Hi HN! I’m Arash, one of the founders of Strada ( https://ift.tt/f24etGh ), a cloud IDE for building automation workflows across your company’s SaaS apps. Strada handles integrations, triggers, infrastructure and observability while letting you write core workflow logic in Python (more languages soon). It's for teams that hit limitations with low-code tools while building with internal apps — eg. Zendesk, Jira, Salesforce, Slack. You can access our docs at ( https://ift.tt/Xp6dH43 ). While working on our first product (a unified accounting API), we learned that as companies grow, their integration teams become more technical but typically still use low-code tools. We also observed that as LLMs are becoming popular, these teams (usually outside of engineering) are adopting more code. For example, we spoke with multiple companies that generate integration code with an LLM and use it in their low-code platform. Unfortunately, most integration tools are not designed with code as a first-class citizen. They often have limited support for external libraries, restrict how variables are used, and limit how code blocks interact with other workflow steps. But integration developers put up with them because stitching together authentication, scripts, APIs, infrastructure, and observability is time consuming and not a core focus for their teams. Instead of drag-and-drop blocks, we chose code as the main interface. Tasks that are frustrating in low-code tools become simple with code: conditional logic with layers of branching, complex transformations, or problems that an external library already solves (for example, redacting personally identifiable information with the scrubadub library [1]). Each Strada workflow is a contiguous Python script, and every action configured in the UI can be invoked like a function. We started with Python since it’s popular with teams outside of engineering, like IT, Data, and Ops. Our goal is to help integration builders focus on logic unique to their business by simplifying everything outside of that: - Integrations: we handle authentication and provide abstractions for common app actions; - Triggers: workflows can be triggered by a webhook or run on a schedule; - Infrastructure: one-click deployment with automatic scaling; - Observability: detailed logging of workflow actions, payloads, and errors. Today, customers use Strada for workflows like Customer Support (receive Zendesk ticket webhook, remove sensitive information, perform sentiment analysis using OpenAI, and escalate problematic tickets) and Customer Onboarding (receive webhook with new customer data & files, transform to expected format, send request to third-party API, send request to internal endpoint). What we're currently working on: - More enterprise app integrations; - A self-hosting option; - More runtimes in addition to Python; - AI for code generation. We’re excited for you to try it and share your feedback! [1] https://ift.tt/g0fAKtW https://ift.tt/f24etGh February 22, 2024 at 10:15PM

Show HN: An Experiment with One-Feature Tool Made $7164/Mo https://ift.tt/hSynTCK

Show HN: An Experiment with One-Feature Tool Made $7164/Mo My Raw Story on coming up with an idea, building and growing it. It's very detailed, with the purpose of giving another founder an insider look at one way of doing it. In January I launched an indexing tool called Index Rusher, that forces google to index your pages quicker, to get ranked for SEO faster. This whole project was something I needed myself since I got over 20 products and paying for an external one would simply cost too much. My initial idea was that I would just build an internal tool for my use, that has only 1 feature. No UI really, just 1 button. In the middle of the process, I realized that I could actually run an experiment and launch this tool publically with just one feature. Super simple. I hired a dev who spent a month building it. It looked super easy at first, but it turned out there were so many hidden snakes on the way. Troubles with sitemaps, google APIs, and more. 1 month later I launched it (In Jan). The launch didn't go so great, but I didn't really have high hopes. Because nobody knew about this tool, I had no traffic on the site. I still sold several licenses, which made me pretty happy, it felt like validation, people needed it, even if it solved such a narrow problem. At that point, I declared my next stage of the experiment: Growing the traffic and revenue. I've done a number of growth hacks in the next 30 days, resulting in over $7k in revenue, but what's more important, the traffic on the site has grown a lot and stays high and growing. This means I've done a pretty good job on organic growth too, which will just accelerate over time. Here is what I've done: Cross-linking. I added links in the footer on my other products. This is one hidden effect of having multiple products. Each may serve as a lead magnet for the other one. In my case, I have the same audience for all my tools, people who love one of my tools often check out the rest. Being visible on social media. I monitor discussions around the Google Indexing topics and add my replies there. I don't just spam in replies with my tools, in most cases, I genuinely answer and bring value. If my reply gets a reply, I may include my URL in the next reply. Social Media and Blog posts. I've posted several posts about Growth, where I mentioned Indexrusher since I actually use it for me Growth. Traffic from Directories. This one was the top channel of growth. Over 50% of the paying users arrive from web directories. I used a tool that listed Index Rusher on 100 directories & websites. Sponsored listings. I "sponsored" directories to place a banner for my tool on the top of their page/list. Seeing the effect of "boosted" listings. The ROI was good. About $2.5k of revenue came in from these boosts. Affiliate partners Made a deal with a few affiliate partners who reached out to me on X and he drove a decent amount of traffic and paid users to me since he was launching on PH the same week, The total economy of the project now Dev costs: $1500*3=$4500 - Godaddy domain: $9 - hetzner Hosting: $10/mo - landing page on Unicorn Platform: $9/mo - cost of sponsorships: $800 - Affiliate payouts: $150 - listingbott for backlinks: $499 - seobot ai for blog: $99 - Stripe fees: $654 Total cost: $6711 Revenue: $7164 Profit: $453. So, it's profitable! My next steps will be 1) Promote it to 100,000+ users of my Website Builder and reach out to more website builders and pitch them the integration 2) Increase Word-of-mouth effect 3) Perhaps try some paid ads 4) Add automated emails to remind about Index Rusher users who signed up but didn't buy 5) Launch a directory as a lead magnet 6) Launch little free tools as lead magnets 7) Product Hunt launch 8) AppSumo launch I will make a new post in a month describing how it went. February 22, 2024 at 02:13AM

Show HN: jSuites v4 - A library of ultra-light components and plugins free (MIT) https://ift.tt/mleHCwa

Show HN: jSuites v4 - A library of ultra-light components and plugins free (MIT) https://ift.tt/mYExK9U February 21, 2024 at 10:47PM