Codee @codee_com

Automated code inspection tool for correctness, security, modernization, portability and optimization. #Fortran #C #Cpp codee.com Worldwide Joined May 2012

Tweets

2K
Followers

816
Following

1K
Likes

1K

Codee @codee_com

a month ago

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

0 0 0 49 0

View Details

Codee @codee_com

a month ago

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.

0 0 0 38 0

View Details

Codee @codee_com

a month ago

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-ico…

0 1 1 61 0

View Details

Codee @codee_com

2 months ago

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

0 0 1 54 0

View Details

Codee @codee_com

2 months ago

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

0 0 0 38 0

View Details

Codee @codee_com

2 months ago

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-formatte…

0 0 1 43 0

View Details

Codee @codee_com

2 months ago

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-secur…

0 1 1 67 0

View Details

Codee @codee_com

2 months ago

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-formatte… See the full case study: codee.com/case-study-ico…

0 0 0 61 0

View Details

Codee @codee_com

2 months ago

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-ico… #HPC #Fortran #DevOps #ScientificComputing

0 0 0 73 0

View Details

Codee @codee_com

2 months ago

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? 👇

0 0 1 42 0

View Details

Codee @codee_com

3 months ago

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/9548-… 👀Is this Fortran’s most underrated feature?

0 0 1 48 1

View Details

Codee @codee_com

3 months ago

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.

0 0 1 44 0

View Details

Codee @codee_com

3 months ago

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.

0 1 1 62 0

View Details

Codee @codee_com

3 months ago

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-fort… #HPC #simulation #Fortran #C #Cpp #software

0 1 3 50 0

View Details

Codee @codee_com

3 months ago

We ran our latest release on 𝗤𝘂𝗮𝗻𝘁𝘂𝗺𝗘𝗦𝗣𝗥𝗘𝗦𝗦𝗢 7.3.1 (~629K LOC). Full analysis in ~1 hour. Key patterns: • Encapsulation evolving • OpenMP scoping • Memory layout drives performance Even mature HPC codes accumulate complexity. DM for the report. #Fortran #QE

0 0 0 48 1

View Details

Codee @codee_com

3 months ago

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.

0 0 0 42 0

View Details

Codee @codee_com

3 months ago

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/37… LLMs can assist. They shouldn’t be trusted alone. They also evaluated Codee, breakdown here: codee.com/codee-analyzer…

0 0 1 59 0

View Details

Codee @codee_com

3 months ago

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/fortr…

0 0 1 41 0

View Details

Codee @codee_com

4 months ago

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-corre…