Maxime Racki retweeted
🗞️Extra, extra! There is a new free tier of SonarQube hosted in the cloud! Free users can now experience SonarQube without the hassle of installing and managing servers 😎👌☁️ What else? Read the news: bit.ly/3Zdj9Dl #SonarQube #Cloud #DevOps #Developers
2
3
536
Maxime Racki retweeted
If you live in the Bay Area or are attending #QCon, then make sure to join the #SonarTeam and Diffblue on Wednesday at the second Sonar SF meetup! We'll have drinks, bites, and a panel about AI in the SDLC. Let us know if you can join by RSVPing 😄. sprou.tt/11Ec3mMbhh5
1
1
97
Maxime Racki retweeted
In case you missed it, here's the recording of our #HEXACON2024 talk "Exploiting File Writes in Hardened Environments"! It's a short and sweet 30-minute talk, so grab a coffee and sit back while @scryh_ goes from HTTP request to ROP chain in Node.js ☕ piped.video/watch?v=ltmZNTP2…
15
39
3,569
Maxime Racki retweeted
👏 That's a wrap at GitHub Universe! Thanks to all the amazing folks who joined us at this year's event, between our Community Meetup, booth talks, and Demo Stage presentation! We'll see y'all at the next conference.
2
5
437
Maxime Racki retweeted
We’re heading to #GitHubUniverse! We’ll be giving booth demos on Sonar AI Code Assurance, our newly launched capability that helps ensure high-quality and security of #GenAI code.
1
1
1
329
Maxime Racki retweeted
🚨 THIS WEDNESDAY ☁️ Webinar: Introducing Sonar AI Code Assurance & AI CodeFix! 🌐 Register here: bit.ly/3U6qGkB Tune in to learn how these exciting features are helping developers test, fix, and improve the quality of their AI-generated code! #SonarAISolutions
2
6
690
Maxime Racki retweeted
🔧 Learn about the top 3 code security flaws: SQL injection, Deserialization Injection, Logging Injection, and how to prevent them! Our newest blog by Sonar Developer Advocate @vilojona 🥑 Read here 👇 bit.ly/3XEM1CA
2
3
423
Maxime Racki retweeted
.@SonarSource now supports Python code analysis in Jupyter Notebooks! If you are working with libraries like #TensorFlow Pandas, & Numpy this is something that will help you code better. Available in SonarCloud & soon in SonarQube. #Python #JupyterNotebooks #DataScience
1
2
204
Maxime Racki retweeted
Java #CleanCodeTip! The usage of generic exceptions prevents the calling methods from handling different system-generated exceptions and application-generated errors
2
2
450
Maxime Racki retweeted
Looking to maximize your investment in #Cleancode? Join our webinar to learn how #SonarQube Enterprise Edition can unlock features that will help you get the most out of your Clean Code initiative.
3
2
73
2,319,884
Maxime Racki retweeted
Looking to maximize your investment in #Cleancode? Join our webinar to learn how #SonarQube Enterprise Edition can unlock features that will help you get the most out of your Clean Code initiative.
1
3
63
2,611,700
Maxime Racki retweeted
Developing code with AI? Keep your AI-generated code free of bugs and errors with these helpful tips from the Sonar team. Join our upcoming webinar back by popular demand to learn more!
8
7
68
1,734,594
Maxime Racki retweeted
#CleanCodeTips Whether you're a seasoned C# developer or just starting your journey with .NET, this blog will showcase the types of errors that can creep up and harm the quality of your logs! Read here 👇 bit.ly/3Jf21EC
3
4
549
Maxime Racki retweeted
Using Github Copilot to generate code? Do you find yourself backtracking and fixing unnecessary bugs? With SonarLint + SonarQube, you can whip your code into shape, whether it’s your own, developed with AI, or both! #CleanCodeTip Watch the demo here! 👇 piped.video/qkyD7-Y6AYs
1
2
528
Maxime Racki retweeted
Java #CleanCodeTip! Duplicated string literals make the process of refactoring complex and error-prone, as any change would need to be propagated on all occurrences. Using constants to store string literals will make refactoring easier and improve the consistency of the codebase
1
1
2
527
Maxime Racki retweeted
Java #CleanCodeTip! Leaving TODO comments in the source code leads to code that is not complete and can impact several areas. Leaving it unattended could cause incomplete functionality, missed bug fixes, codebase bloat, and hinder team collaboration.
1
2
1
526