I'll bite. Yes, it's a lot of money. It's several months worth of nice healthy groceries for a family of 4. It's my annual deductible on my health insurance. It's slightly lower than my annual property taxes.
I got quoted $700 by the pond guys to replace it. I ended up buying it for $109 bucks and replacing it myself. It honestly would not have been possible without ChatGPT because I had nothing to go off of and the pipe connection was really specific to that model.
We were experiencing abnormally high electrical bills and I could not figure out what was happening, so I downloaded the granular usage data (15 min increments) from Duke Energy, explained what we had in our house and when we typically used those items (washer/dryer, EVs, etc), provided a rundown of our energy usage plan, then asked Claude to build me a Streamlit dashboard that would help us understand what was going on and predict what was going to happen over the next months. The dashboard had a few simple toggles a levers. Claude was basically able to one-shot this, knew how to manage the XML from Duke Energy, etc... In about 20 minutes of prompting, I had a very comprehensive dashboard that was extremely helpful not only in diagnosing that specific issue but also in helping us understand how to further lower our electrical bills.
Going from one off prototype to robust product is a huge leap.
I think these ephemeral context tailored projects are really great and useful. But these are not to be thought of as products. They work for you specifically, and people who are tech-brained enough to be able to formulate the complex requirements into a coherent prompt are not like the average user you'd have to sell a product to. It's much easier to make software to intelligent users.
> The comment above literally said this took them 20 minutes of prompting. That doesn't sound like much if any value add.
You can say much the same about most small SaaS products of the last decade - the value-add isn't the 20 minutes of prompting, it's that someone else has already tested and validated the damn thing.
And yes, you won't sell many to engineers, because they'd rather prompt their own in-house version. But you might well sell to other folks
How do you approach the market with a random app? Posting on X/HN or something else?
I have a number of solutions from the past year that could be products and for sure would be sellable, but since they were so easy to build I just keep them to myself. It feels like such a long shot to throw up a landing page with a demo and start cold calling.
Homeassistant already has tons of integration into power providers and easily let's you pipe in local data if you have it. In addition - can it be a product if anyone can just type what this guy did into an LLM? What's your moat if anyone can just replicate it?
It doesn't have to be a durable.moat for it to be a product that makes the author money, just right place right time. If it's gonna cost me a bunch of time and effort and tokens, and the cost of the product is lower than the time and effort and tokens, then I'd rather pay for the product.
Right now we're in $1 Uber ride territory. That $20/month OpenAI/Anthropic plan isn't going to last forever. If it's going to cost me $100 in tokens to replicate the product, $20 is a cheap no brainer purchase m
Kids go through changes in how they perceive their engagement with activities. At a very young age, they have little self-consciousness and will happily spend lots of time engaging with things they cannot do well. As they get older, frustration sets in sometimes when they cannot do something perfectly the first time they try it. I think some of the music programs, like Suzuki, try to take advantage of this by getting kids up-to-speed on the violin (or whatever) before they enter the phase where frustration dulls their interest. No parent really wants their kid to enter the cycle of repeatedly trying and quitting activities because of frustration. It eventually leads to a sort of apathy and lack of willingness to engage with things they perceive might be frustrating. This is a hard line to walk sometimes. I guess I'm just saying that you sometimes need to "push" them to remain engaged so that they can work past the frustration. It is a skill to learn that you have the ability to overcome the difficult initial learning curve of a lot of activities, sports, etc. If you can help imbue them with that skill, it can lead them to have a love for learning -- or a least not a fear of trying new things, which ultimately is the skill that can enable them to "flourish broadly," in my opinion.
Regarding documentation, I think the DuckLake docs would benefit from a relatively simple “When should I consider using DuckLake?” type FAQ entry. You have sections for what, how, and why, essentially, and a few simple use cases and/or case studies could help provide the aha moment to people in data jobs who are inundated with marketing from other companies. It would help folks like me understand under which circumstances I would stand to benefit most from using DuckLake.
DuckDB devrel here. You are right. This was in the FAQ but I also added it to the DuckLake documentation's main page at https://ducklake.select/docs/stable/
My employer is in the midst of migrating petabytes of data from Snowflake to DataBricks. They’re sold on the “all in one” nature of the platform and believe they’ll save significant money through a contract locking them into DataBricks running on Azure. It is a wildly disruptive process in an environment where the “Snowflake police” (as we call them) have been hounding everybody to reduce credit usage. Now the IT platform team is trying to explain units of work to non-technical VPs, for example, and there’s mass confusion. All signs point to them ending up in the same situation with expensive DataBricks bills, vendor lock in, and a future migration to try to reduce costs.
I guess what I was trying to say is that DuckLake isn’t even a blip on their radar. Should it be? Could you explain it to a non-technical marketing VP as part of a cost savings measure? What’s the DuckLake equivalent to a Unit of Work on DataBricks or a Snowflake Warehouse? If I needed to join multiple tables with billions of rows, where does the compute happen in DuckLake? Can you run your own cluster like with Clickhouse or StarRocks? How does it scale horizontally with storage and compute? How do I update it? What if there’s a security flaw? How well does it stand up to 500 people querying it simultaneously and what type of setup would I need to achieve that?
The PMs that manage the IT platform team aren’t necessarily deeply familiar with all of the technical details. A compelling introduction to DuckLake would provide the answer to some of these questions in a way that the VPs or PMs could digest it easily while providing the technical details the data workers require. For better or worse, “data lakehouse” and data warehouse and data lake all are industry jargon that is pretty impenetrable to people who don’t spend a lot of time working with the tools but who cut checks and make decisions.
> ... they failed to keep the momentum and stopped taking risks.
This is a problem that infects all of the large studios now, from Epic to EA, Ubisoft, etc. My read on it is that it feels less risky to double-down on an exiting successful live service game like Fortnite or Rainbow Six Siege. That's probably true for ~5 years. After those ~5 years, it's far riskier to continue investing in the game than it is to start winding it down into maintenance mode while working on new titles or IP. The related risk is assuming that since the one title was huge that players are going to crave other titles in the same brand or franchise. For example, Ubisoft's assumption that Rainbow Six Extraction would naturally follow the success of Rainbow Six Siege.
These companies get addicted to the recurring revenue stream and pivot their businesses under the incorrect assumption they will last forever, at the expense of new projects.
I’ve always been mildly bothered by the LED lighting in my home, as if it’s simultaneously bright but not illuminating. In simple consumer terms, if I wanted to shop for a variant that more closely replicated incandescent lighting, what exactly am I looking for on the packaging? Or does this not exist?
It’s called SSI, spectral similarity index. SSI is specified for a color temperature, eg 3200 or 5600. 100 is identical to tungsten or sunlight. Values above 85 are good.
In the UK I've not been able to find high wattage (10-20W) LED lightbulbs with high CRI, some don't even mention it in listings, let alone SSI, which I have never seen.
Where are you seeing these? Is this industrial/commercial suppliers?
I buy the "warm" light LEDs, which look (to my eye) closer to incandescents.
Standard LEDs bulbs are bright white, almost bluish, and yes "bright but not illuminating" describes them well. I feel many modern car headlights have the same issue.
The human eye doesn't focus the blue end of the spectrum very well.
There is no such thing as a “standard LED lamp”. LED lamps come in a huge variety of shapes, various bases, power usage/lumen output, color rendering index, and color temperature.
Lots of companies sell cheap crappy A19 E26 base 5000K lamps, that doesn’t make them the ‘standard’.
Nothing on the box really means anything, so many bulbs claim high CRI and everything but in reality have terrible spectrum. So you can only go off of actual real life testing from a third party.
