RE: https://mamot.fr/@Khrys/116226030767910474

As predicted, humans are being turned into accountability sinks for #AI. AI code doesn’t work? You're fired!

"After outages, Amazon to make senior engineers sign off on AI-assisted changes"

@pluralistic

@elasticsoul @pluralistic Bets that the seniors start not signing off on code they aren't positive really works, with vague comments like "Overly complex, please simplify." or "Insufficient error checking. Please improve."?
@tknarr @elasticsoul @pluralistic
Start with where it puts the curly braces, and tab vs. space indents.
@RealGene @elasticsoul @pluralistic Yes on the first. Using tabs for indentation is an automatic "Fire this person." offense for me. Visual space should always match number of characters.

@tknarr @RealGene @elasticsoul @pluralistic
Tabs are better for visually impaired individuals. Instead of “SPACE SPACE SPACE SPACE {“ it’s a simple “TAB {“. Learning about that is what made me change my mind about tabs v. spaces.

Realistically at this point, if your editor can’t automatically manage tabs vs spaces, you should get a new code editor.

@spaceinvader @tknarr @RealGene @elasticsoul @pluralistic tabs also allow the reader to adjust the tab width to a level that improves their visual scanning, and adapt to different window/screen sizes. E.g. wide indents when docked to my 43” monitor, narrow indents when the laptop is undocked.

Spaces as indent pushes what works for the author and their specific situation onto all the readers. Optimizing for the wrong use case (code gets read more often than it’s written, and by more people).

@peter @spaceinvader @RealGene @elasticsoul @pluralistic Only when everyone agrees on a specific tab width. If the width changes, then you end up either inserting a tab where you otherwise wouldn't or spaces where a tab would normally be. Think indenting 6 spaces with tab = 8, then reducing to tab = 4. Remember that alignment isn't always to a tab stop, it's often to a specific column. Think aligning a multi-line expression.

@tknarr @spaceinvader @RealGene @elasticsoul @pluralistic not at all. Take a look at “Smart Tabs”. Good editors, like SublimeText support them natively (open issue on VS Code).

You use tabs for indenting (1 per indent level), then switch to spaces if the line is a continuation and you need to align with text on the previous line. You can then change tab width without breaking formatting.

See: https://lea.verou.me/blog/2012/01/why-tabs-are-clearly-superior/

Why tabs are clearly superior • Lea Verou

@tknarr @spaceinvader @RealGene @elasticsoul @pluralistic note this doesn’t work well for aligning comments at the ends of lines, you still need spaces there. Only tabs at the beginning of lines, and only to match the indent level.

Frankly, IMO editors should adopt a real “tab stop” model. After non-whitespace, tabs should skip to align with the tabs on previous lines. The whole “skip to the next even multiple” model was broken from day one.

@peter @spaceinvader @RealGene @elasticsoul @pluralistic Yes. The model was based on the one used on typewriters, but badly adapted ignoring that typewriters had adjustable tabs so stops weren't "next multiple of n columns".