Happy & proud we've reached an amazing milestone: AI source code assistance at Google contributes the same amount of characters as are manually typed in the IDE. Feels like the beginning of an exciting journey - we're getting started transforming how software is developed. :-)
Today on the blog, read all about how we are bringing together the latest foundation models and software development data to assist with software engineering at Google, including what we’ve learned and where we expect the next wave of this work to go. →https://t.co/yYXItgmxCG
Great to see the positive responses from Googlers confirming that this works well for them (responses to the original @GoogleAI tweet and @JeffDean's tweet)
ML assisted coding is helping thousands of Google software engineers.
"We see a 6% reduction in coding iteration time (time between builds and tests) [vs. control]" &
"Currently, 3% of new code (measured in characters) is now generated from accepting ML completion suggestions."
@SergeStinckwich Not sure why you're asking (this is from 30 years ago) but the IDE was likely OTI's port of Smalltalk/V to 68K processor machines. Perhaps running on a Sun workstation as per the message on the screen. The Macintosh 68k version can be downloaded: https://t.co/uOXaWL6yxB
Kind of cool to see OTI appear on the debug console of this old Tektronix oscilloscope that I bought on eBay. Working on repairing it - the Smalltalk side already works without issues :-)
Still looking for an engineering manager for part of my team in Munich, working on internal developer tools / Web IDE at Google: https://t.co/NfalJer8IH
I have an open position on my team, looking for an engineering manager (domain: internal developer tools / IDE). Is there anyone you would recommend? For Google, in Munich, Germany.
In related news, after four years in (internal) Search, I somehow found the way back to the developer tools space - since April, I'm responsible for internal code search, code review, and web IDE at Google.