Joined May 2012
- Tweets 1,931
- Following 1,383
- Followers 815
- Likes 1,280
511 Photos and videos
Pinned Tweet
Mar 26
📌 Codee 2026.1 – Faster, More Precise & Reliable Analysis at scale
✔️ Stable Incremental Static Analysis
✔️ New Quality and Fortran Checks
✔️ SEI CERT C Compliance
✔️ Codee Formatter – brand-new line-breaking algorithm
📘 Explore what’s new → codee.com/codee-2026-1-relea…
2
78
Apr 28
Legacy Fortran/C/C codebases don’t break. They slowly become unmanageable.
Codee helps teams regain control: correctness, modernization, security, performance, and coding standards—built for HPC and large-scale systems.
🔗codee.com/
52
Apr 23
Legacy code isn’t the problem. Lack of control is.
What you actually need:
Continuous correctness (beyond tests)
Consistent formatting (control, not aesthetics)
Real CI gates (not just compilation)
Baselines (measure before fixing)
That’s what Codee brings back.
40
Apr 21
Most code issues don't crash, they just hide. 😶🌫️
In ICON (663K lines), correctness was unmeasurable until we automated the checks in CI.
The shift:
🔹100s of hidden bugs surfaced
🔹Quality became a process, not a guess
👉 Download the case study: codee.com/case-study-icon-dk…
1
1
62
Apr 16
Our Open Catalog brings expert guidelines for correctness, modernization, security, portability, and optimization in C, C and Fortran.
Each check explains real issues and how to fix them.
Codee detects them directly in your code, automatically.
🔗 open-catalog.codee.com/
1
54
Apr 14
Today is World Quantum Day ⚛️
Quantum progress isn’t isolated, it’s collective, across disciplines and generations.
And behind it all: the software that powers simulations, models, and research. From HPC to decades of scientific code.
#WorldQuantumDay
39
Apr 9
One of the biggest hidden problems in Fortran codebases isn’t performance. It’s consistency.
Multiple contributors → multiple styles → slower reviews, debugging, onboarding.
Automating formatting fixes it.
Try Codee Formatter (free): codee.com/codee-formatter/
1
43
Apr 7
Fortran wasn’t built for security.
Now it powers critical systems.
Legacy code (30–40 years old) must meet modern cybersecurity standards — without rewriting.
#SAST helps bring visibility into real risks.
We wrote a whitepaper on how to approach it: codee.com/use-case-security/
1
1
68
Apr 1
One coding style for all #ICON contributors✔️
668K lines, 1,172 files → formatted in ~5s with #CodeeFormatter
Consistent, readable code. Zero review friction.
Want the same for your scientific codebase?
codee.com/codee-formatter/
See the full case study:
codee.com/case-study-icon-dk…
62
Mar 30
ICON climate model: 600K lines, ~1,000 contributors. ✅ Correctness is tough.
DKRZ solved it with GitLab CI Codee formatting & static analysis.
Real DevOps for scientific software.
👉Download the case study: codee.com/case-study-icon-dk…
#HPC #Fortran #DevOps #ScientificComputing
74
Mar 24
Modern Fortran is way cleaner than most people give it credit for… ✅ Modules ✅ OO ✅ Coarrays ✅ Generic programming.
Yet many still cling to F77-style COMMON blocks…
Can we unlock its full potential, or are legacy patterns holding us back? 👇
1
43
Mar 19
Did you know there’s an asteroid named after #Fortran?
☄️(9548) Fortran
– ~5.4 km wide
– Larger than 99% of asteroids
Fortran isn’t just used to simulate the universe.
It’s part of it.
spacereference.org/asteroid/…
👀Is this Fortran’s most underrated feature?
1
48
Mar 17
Your climate model runs.
But inside the code:
→ global variables
→ missing INTENT
→ memory & vectorization issues
We analyzed 𝗜𝗖𝗢𝗡 (667K lines, 23K checks).
Not bad code. Just normal scientific code.
The hard part isn’t fixing it.
It’s seeing it clearly first.
1
46
Mar 12
We ran Codee Analyzer on #PHASTA, a CFD solver for large-scale fluid simulations.
📊 64K lines analyzed
⚙️ 718 functions | 1,456 loops
🔎 14,463 checks in ~19 min
Static analysis quickly reveals structural issues impacting correctness and maintainability in HPC codes.
1
1
65
Mar 5
Fortran still powers critical simulations.
But subtle correctness issues can stay hidden for years.
Examples: uninitialized variables and implicit SAVE.
How static analysis detects them 👇
codee.com/improving-fortran-…
#HPC #simulation #Fortran #C #Cpp #software
1
3
51
Feb 26
Who is Codee for?
Scientific software (Fortran / C / C ) has two pressure points:
👩💻 Developers → structural feedback
⚙️ CI / DevOps → enforceable standards
Codee connects both.
In scientific computing, quality isn’t cosmetic. It’s structural.
42
Feb 24
LLMs for HPC optimization? A GMU & ORNL study found strong instruction-following — but also correctness limitations in complex scenarios.🔗dl.acm.org/doi/10.1145/37507…
LLMs can assist. They shouldn’t be trusted alone.
They also evaluated Codee, breakdown here:
codee.com/codee-analyzer-vs-…
1
59
Feb 19
Scientific software was built for performance.
Now it must also be built for security.
Aligning static analysis with CWE, ISO/IEC 24772-8, and SEI CERT helps bring structured security reasoning to legacy Fortran systems.
More in our webinar: codee.com/webinars/fortran-s…
1
41
Feb 17
Fortran code can compile — and still be wrong.
Our whitepaper compares correctness detection across Codee, GFortran, and Fortitude.
Focus: uninitialized variables.
📄 Methodology & results → → codee.com/use-case-correctne…
41