Use cases for AI tools, Code Generation, GitHub Code Search, Clean Code Collaboration
Hi colleagues,
in this edition of the engineering ecosystem newsletter, we are switching to a curated format that features a selection of different topics. Our plan is to alternate between this format, which provides an overview of several subjects within the engineering ecosystem, and a format that focuses on a single, in-depth topic. Since I am too busy right now with work and private topics, I will stay with the curated form for the next weeks.
In this curated edition, we will be covering a range of subjects:
Exploration of use cases for search and AI tools: The blog Oh Bing, Please Don't Be Evil: The blog compares how the different tools (like Google search, Bing and Chat GPT) compare for different use case like creative work, doing activities, searching an answer for different kinds of questions.
AI Tools for code generation and the difficulty of proofreading: Code Generation with AI tools like ChatGPT and Copilot result in very high importance of code proofreading, which can get very difficult. Besides, unit testing and additional AI tools are needed. Wayne Hittel explores these topics in the blog Programming AIs worry me.
Architecture behind Google new code search with language support The blog The technology behind GitHub’s new code search explores how GitHub rebuild the search engine with Rust.
Fuzz Testing with Jest Fuzz Testing now also works with Jest. If you have not heard about Fuzz Testing or care about open source security, I would recommend to learn more with the blog Fuzzing 100+ open source projects with OSS-Fuzz - lessons learned or video How fuzzing with Jazzer helped find a partial bypass for the original log4j fix.
Clean Code Collaboration: Recently I have published a blog on how we are preparing and making decisions about code style changes. The next step is to improve the process when it comes to involving the community in shaping the future of the clean code guide - we want to especially improve the collaboration when it comes to the open GitHub issues.
Thanks and Regards,
Klaus
Subscription: If you want to get updates, you can subscribe to the free newsletter:
Mark as not spam: : When you subscribe to the newsletter please do not forget to check your spam / junk folder. Make sure to "mark as not spam" in your email client and move it to your Inbox. Add the publication's Substack email address to your contact list. All posts will be sent from this address: ecosystem4engineering@substack.com.
✉️ Subscribe to the newsletter — if you aren’t already.
❤️ Share it — The engineering ecosystem newsletter lives thanks to word of mouth. Share the article with someone to whom it might be useful! By forwarding the email or sharing it on social media.