GitHub Copilot, ChatGPT, GIT Visualization, Developer Productivity
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.
I am currently reading and experimenting with ChatGPT, Dall-E and related topics, while most things in social media are over-hyped and many challenges need to be solved first (e.g. legal). ChatGPT, Copilot and others can become valuable tools to help with different types of tasks. For the coming issues I will take a curious perspective from a software engineering point of view.
In this curated edition, we will be covering a range of subjects:
Copilot: The research paper explains how OpenAI is leveraging GitHub for training it's model Codex - for software engineering tasks. Codex is the model used for GitHub CoPilot.
Copilot for Business: Recently Copilot for Business became available with an advanced OpenAI model and new capabilities, still a lot of legal questions remain unsolved.
Detect Text generated by ChatGPT OpenAI has launched a tool that tries to detect texts created by AI or a human. Its success rate is still pretty low, but Open AI wants to continuously improve.
GIT command visualizations: The tool git-sim allows generating visualizations or videos for the effects of Git commands on a repository to avoid unexpected effects.
Improving Developer Productivity in the context of Remote Development: The blog Improving Developer Productivity at Uber by Uber engineers explains the challenges the move to MonoRepo caused, how they those were overcome with a disciplined approach to improve Remote development and what still needs improvement.
Improving Collaboration on Clean Code Open Source Style guide: The process of collaboration around the Open Source Style Guide will evolve. In the first step we focused on being able to make decisions. As next step we want to 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.