I got an idea about a code view as a comment lines. Just sharing, might hope someone to grab and build his next AI startup: https://www.linkedin.com/posts/ahmetson_idea-make-a-recipe-from-the-code-comments-activity-7330996208393490432-iatA?utm_source=share&utm_medium=member_desktop&rcm=ACoAABKP8C0BqAZeDHplB5MIP1xfu7-fWDyyUK4

This is cool. I used to be a diehard Refactoring/Martin Fowler fan, but then a friend pointed out that what qualifies as "well-written code" depends on the audience/situation. They broke it down into a few situations: • Debugging - Temp variables and print statements are good here. Sometimes, long functions without too many subroutines can be easier to reason about. • Refactoring - Temp variables are bad since they created dependencies throughout code. Long functions generally bad. DRY. • Writing code - You're pushing paint around on the canvas and you probably should be copy/pasting and duplicating things while you figure out what's going to work. • Reading code - Comments, clear variable names, etc. • Production runtime - Performance > readability It will be cool if AI will adapt the code to whatever context we're in