Tools for scientific coding have not kept pace with progress in computer science, UX, cloud computing or data management. IronLAB is an ambitious proposal to bring that back on track. IronLAB is not a product (yet). It’s simply an idea and a wishlist. Clap for this story if you wish…

Well, it’s all reappeared now and people at the conference are looking at it, evaluating the tools and figuring out the processes. The last of the six steps is to use the product, then start mapping out the chess game of what to do next. I’ll come back here once we’ve had a decent length of time to do so, and update you with what went on and what we think the next steps are!

It’s Wednesday Afternoon in Copenhagen, and it’s time to deliver both a service and a presentation. This article is for the fifth of our “Six Steps” — you can read the overview here. This article is aimed at engineers, researchers and execs in the Wind Industry, to help understand the…

It’s Wednesday Morning in Copenhagen, and we’re looking at how to populate data into our database. This article is for the fourth of our “Six Steps” — you can read the overview here. This article is aimed at engineers, researchers and execs in the Wind Industry, to help understand the…

It’s Tuesday Afternoon in Copenhagen, and it’s about time to show our hand with some code. This article is for the third of our “Six Steps” — you can read the overview here. This article is aimed at engineers, researchers and execs in the Wind Industry, to help understand the…

It’s Tuesday Morning in Copenhagen, and we’re talking about Architecture with people in the hall. This article is for the second of our “Six Steps” — you can read the overview here. This article is aimed at engineers, researchers and execs in the Wind Industry, to help understand the process…

It’s Monday evening in Copenhagen, and the challenge starts here: at Wind Europe 2023 we’ll be deploying a live data service. This article is for the first of our “Six Steps” — you can read the overview here. This article is aimed at engineers, researchers and execs in the Wind…

I previously wrote that my M1 Mac was unfit for purpose*, and that I was sending it back. What happened since? *The stated purpose being use by scientists and engineers (i.e. not software developers, but people who code for their job) for technical computing. I genuinely was intending to send…

As an engineer / scientist, the system is too problematic for work to be feasible. — Update: The following story is now well out of date. I’ve been watching the ecosystem around the M1 architecture since, and have written a new story, to address the issues I discuss below and more. M1 for technical computing, round two: The Resurrection I previously wrote that my M1 Mac was unfit for purpose*, and that I was sending it back. What happened since?levelup.gitconnected.com