9 ways ChatGPT saves me hours of work every day, and why you’ll never outcompete those who use AI effectively. — from linkedin.com by Santiago Valdarrama

Excerpts:

A list for those who write code:

  1. Explaining code…
  2. Improve existing code…
  3. Rewriting code using the correct style…
  4. Rewriting code using idiomatic constructs…
  5. Simplifying code…
  6. Writing test cases…
  7. Exploring alternatives…
  8. Writing documentation…
  9. Tracking down bugs…

Also relevant/see:

A Chat With Dead Legends & 3 Forecasts: The Return of Socratic Method, Assertive Falsehoods, & What’s Investable? — from implications.com by Scott Belsky
A rare “Cambrian Moment” is upon us, and the implications are both mind blowing and equally concerning, let’s explore the impact of a few forecasts in particular.

Excerpts:

Three forecasts are becoming clear…

  • Education will be reimagined by AI tools.
  • AI-powered results will be both highly confident and often wrong, this dangerous combo of inconsistent accuracy with high authority and assertiveness will be the long final mile to overcome.
  • The defensibility of these AI capabilities as stand-alone companies will rely on data moats, privacy preferences for consumers and enterprises, developer ecosystems, and GTM advantages. (still brewing, but let’s discuss)

…

As I suggested in Edition 1, ChatGPT has done to writing what the calculator did to arithmetic. But what other implications can we expect here?

  • The return of the Socratic method, at scale and on-demand…
  • The art and science of prompt engineering…
  • The bar for teaching will rise, as traditional research for paper-writing and memorization become antiquated ways of building knowledge.