Ask HN: Are you working on interesting technical problems?
I&#x27;m in the exploratory stages of starting a noncommercial project focused on hosting, processing and serving a vast amount of climate data for scientists and researchers. I&#x27;ve &quot;seeded&quot; this project with my own bare metal hardware, electricity and internet access. This includes 136 vCPUs, 512GB of RAM and 128TB of hard drive storage capacity (with room for another 456TB). As my own money permits, I plan to slowly add to this lab over time.<p>My initial consideration is to develop and host a sort of public Wolfram Alpha, but specialized for climate data queries and visualization. I&#x27;m open to other suggestions, as I&#x27;m currently in the process of architecting the system and reaching out to climate scientists for feedback on what they need that isn&#x27;t well-served yet.<p>Once all the infrastructure work is done, I&#x27;d be happy to contribute to climate modeling more theoretically. But for now my prerogative is to develop a central repository for as much climate data as possible, normalize it as reasonable, and store it in a queryable format.<p>There are interesting technical problems here due to the scale of the data, the variety of its native (raw) formats, the frequency with which each source updates and the types of information involved. But speaking directly to the title of this post: I don&#x27;t think anything I&#x27;m doing is strictly an unsolved technical problem, it&#x27;s just a complex technical undertaking. There are plenty of data serving and processing pipelines for this that have already been proven capable.