HN user

tomashm

50 karma

meet.hn/city/no-Drammen

Posts3
Comments29
View on HN

And with AI writing code, why use libraries, which makes us more vulnerable to 0-day attacks?

Our simulation core components are pure Fortran, no libraries, all written by Claude/Cursor/Codex.

Personally, I’m selling my U.S. stocks and bond holdings in my pension portfolio. Partly because I see them as a risk, and partly for moral reasons: I don’t want to support what I see as the current U.S. oligarchy. I'm also sad to say I've also bought 4 Teslas until I realized how bad things are, but I'll send no more money in that direction from now on, and I try to convince people I know to do the same.

Our company cloud infrastructure at Azure has already been replaced by VPSs at Hetzner in Europe.

Making advanced multiphysics simulations and optimizations accessible through a simple web interface and AI chat agents. I’m building SimuPort (https://simuport.com ) to lower the barrier to running and iterating on complex simulations. I’m interested in hearing from anyone who has needed these kinds of simulations in practice (e.g., optimizing airflow in devices, analyzing thermal–structural interactions in prototypes) or who has experience with tools like Ansys, OpenFOAM, COMSOL, SimScale, or similar. What worked, what didn’t, and what’s still missing?

tldr; Adding key examples to a specification makes it much easier to understand.

I learned programming with Pascal at university. It had a very formal, math-like syntax, complete with BNF-style grammar.

The next course used the famous K&R book (The C Programming Language), and what a breeze that was! It taught by showing lots of relevant, working examples.

Since then, I’ve realized that while examples aren’t a substitute for a clear specification, well-chosen examples make specs far easier to grasp.

I recommend reading Gojko Adzic’s thoughts on this (https://www.linkedin.com/in/gojko/). He’s the author of Specification by Example.

He argues that identifying and refining key examples is a great way to raise the quality of documentation and shared understanding.

The same logic applies to voting in elections. One could argue that a single vote rarely changes the outcome, so why bother participating?

Yet I believe that when enough individuals make the same choice—whether at the ballot box or with their wallets—it creates meaningful impact. Collective consumer decisions send powerful signals to companies and their leadership, just as collective voting shapes our democracy.

[dead] 2 years ago

The Helseplattformen project, aiming to implement Epic as a unified electronic health record (EHR) system in Central Norway, has come under severe scrutiny from the National Audit Office. Initially budgeted at $370 million, costs have skyrocketed to $600 million, with the rollout heavily criticized for poor planning, patient safety risks, and a frustrating user experience. Healthcare professionals report that the system is unintuitive and time-consuming, hampering their ability to provide efficient care.

Epic, a U.S.-based EHR system, is widely used globally, but the Helseplattformen project took a highly customized, waterfall approach to implementation, which involved tailoring the system extensively to local needs. This has led to significant rigidity and operational inefficiencies. In contrast, other regions in Norway have opted for more agile methodologies, emphasizing standardization, open communication protocols, and flexibility to better integrate various healthcare systems.

The "one system fits all" philosophy behind Helseplattformen has been seen as a misstep, with experts now advocating for a more modular, ecosystem-based solution that allows for easier adaptation and interoperability across the healthcare sector.

[dead] 2 years ago

The Helseplattformen project, aiming to implement Epic as a unified electronic health record (EHR) system in Central Norway, has come under severe scrutiny from the National Audit Office. Initially budgeted at $370 million, costs have skyrocketed to $600 million, with the rollout heavily criticized for poor planning, patient safety risks, and a frustrating user experience. Healthcare professionals report that the system is unintuitive and time-consuming, hampering their ability to provide efficient care.

Epic, a U.S.-based EHR system, is widely used globally, but the Helseplattformen project took a highly customized, waterfall approach to implementation, which involved tailoring the system extensively to local needs. This has led to significant rigidity and operational inefficiencies. In contrast, other regions in Norway have opted for more agile methodologies, emphasizing standardization, open communication protocols, and flexibility to better integrate various healthcare systems.

The "one system fits all" philosophy behind Helseplattformen has been seen as a misstep, with experts now advocating for a more modular, ecosystem-based solution that allows for easier adaptation and interoperability across the healthcare sector.