I defended my PhD at TU Darmstadt! 👩‍🎓 I am grateful for the invaluable learnings from this journey, leading to a memorable defence, get-together, and weekend with friends. Heartfelt thanks to everyone who supported me, joined my defense, or celebrated with me.🙏 .#PhD #PhinisheD

RT @golangFrankfurt: Go 1.23 is released. 🥳 It's time for a new release karaoke meetup. Join us on the 29th of August @ioki_mobility for ou….

RT @golang: 🥳 Go 1.23.0 is released!. 📝 Release notes: ⬇️ Download: #golang https://t.co/….

Excited to share our latest findings that advance the reporting of API misuses @SANERconf! Join my presentation tomorrow - Friday 15.3 - at the Program Analysis session (session start 9:00, talk: 9:59) to learn more. Don't miss out! . #SANER24 #APImisuses #staticanalysis.

RT @fabiopalomba3: How to bring the power of AI to your apps? Krzysztof Cieślak is about to start his keynote speech @SANERconf! https://t.….

This work was in my idea stack for quite a while. I'm glad that @M_Schlichtig and I revisited this idea while working on another paper, refined it, and had the opportunity to work together with two awesome students to tacke a step into advancing the reporting of API misuses. 🎉🙏.

Our work advances the reporting of API misuses, and our changes enabled us to fix previously known false positives of CogniCrypt. The latest @cognicrypt release 3.1.0 has basic support for subsequent error detection. 🥳.

We conduct an expert interview to understand if our approach advances the usability of analyses. Our results indicate that reporting the fix location (root error) supports users in fixing the misuses.

Further, we have shown that our changes in the static analysis, CogniCrypt @cognicrypt, is negligible in practice. Our approach, CogniCrypt_SUBS, adds a median runtime overhead of 1% to 4% depending on the chosen configuration.

We use a crypto API (JCA) in Java for our evaluation, as previous work showed that this domain will benefit from our approach. Our empirical study shows that every second project with API misuses has dependent errors, and some classes "heavily" depend on others.

Idea behind the hidden predicate approach: .- specify API misuses to be able to track those connections.- track properties between (object) transitions.✅ ensured predicate: all specifications are fulfilled.❌ hidden predicate: if no ensured predicate is generated

Context: Static analyses benefit from a low false-positive rate. So far, analyses tend to report the manifestation rather than the fix location of API misuses/vulnerabilities. If an analysis reports both, the connection is unreported and may result in effective false positives.

Accepted 📄 @SANERconf 🥳. We present the hidden predicate approach to track dependencies between API misuses and show that every second project has dependent errors. 👩‍🎓 @akwickert, @M_Schlichtig, Marvin Vogel, Lukas Winter, @m_mezini, and Eric Bodden.

RT @GopherCon: Today we celebrate and honor the invaluable contributions of women in technology! 💻. From developers to engineers, leaders t….

RT @GopherCon: The #GopherCon stage is ready for your brilliance, and we want YOU to take the spotlight! If you have a talk idea that revol….

RT @gopherconeu: Excited for #gopherconEU in Athens next month with @ardanlabs? If you missed the talk submissions, fear not! Our lightning….

RT @NataliePis: Tomorrow Avigail is turning 4 and I’m organizing her birthday party in Berlin. She won’t attend bc she’s held hostage by t….

RT @GopherConAUNZ: Axel Wagner going in hard with the theory #gopherconau

RT @GopherConAUNZ: And now, @mmontagnino with Back to the Future: Modernizing CLIs Using #golang #gopherconau