1,442 karma · joined March 7, 2018
Seems like this is solvable:
1. Keep rolling out the closed-loop cooling improvements now appearing in new DC designs.
2. Add more desal capacity where it’s cheap (sunny coastlines + renewables) to cover the residual demand.
Sources: - https://aedyr.com/plantas-desaladoras-agua-salobre-espana/
Agentic workflows are a much higher bar that are just barely starting to work. I can't speak to their efficacy but here's a few of the ones that are sort of starter-level agents that I've started seeing some companies adopt:
https://support.zendesk.com/hc/en-us/articles/8187090244506-...
The arguments are essentially:
1. The technology has plateaued, not in reality, but in the perception of the average layperson over the last two years.
2. Sam _only_ has a record as a deal maker, not a physicist.
3. AI can sometimes do bad things & utilizes a lot of energy.
I normally really enjoy the Atlantic since their writers at least try to include context & nuance. This piece does neither.
I don't recommend it for non developers until there is more content, but it's a really neat dev kit device that shows where the future is headed.
Different fine-tune and gave it access to the Internet.
Source: https://x.com/asadovsky/status/1750983142041911412?s=20
Source: https://nypost.com/2023/11/07/media/sphere-cfo-quit-after-ja...
We were affected but it’s blog posts like these that make me never want to move away. Everyone makes mistakes. Everyone has bad days. It’s how you react afterwards that makes the difference.
That's when you know it's going to be amazing. Single best narrative-form overview of the current state of integrating LLM's into applications and the challenges encountered I've read so far. This is fantastic and must have required an incredible amount of work. Massive kudos to the author.
- I ask it to create list of questions that different personas might want to answer with our reports section. I then ask it to categorize those questions & to then provide suggestions for graphs & dynamic filters that would help answer those questions.
- I ask it for help translating emails and documents for international customers.
- I ask it to create markdown, formatted spec documents with really verbose context. Helps me as sort of a foundation for feature sprint kickoffs.
- I ask it to take internal documentation and to simplify it so that we're able to use it for public facing help center documentation.
- I use it as my first resource for asking questions about SQL queries, React patterns, explaining different things eg SVG properties and how to manipulate them. I gut check things with Google when I feel like it might be hallucinating but generally it does really well ~ 90% of the time. Saves lots of time compared to going to Google first.
- I ask it for help writing tests or help refactoring code
- I asked it for help in creating some policy & procedures docs that we needed for compliance. Essentially gives you a decent template to then build from & customize.
- Lots of other things. It replaced Google for so many things in my daily workflow. It also helps a lot when you're not feeling creative and you need some ideas.