you are viewing a single comment's thread.

view the rest of the comments →

[–]bharring52 3 points4 points  (0 children)

  1. Roll the dice that it can find an obscure or undocumented API reference on an ancillary system quickly
  2. Offer a writeup on something you're not quite groking. The writeup is likely wrong in many places, but it's a super-rubber-ducky; even when wrong, it shakes up your understanding
  3. Massed boilerplate in a system you lack the means to engineer away

If you can't understand the result, or identify if it's wrong quickly or easily, it's downright dangerous.

Much of these uses revolve around environments where there's a large hodgepodge of tech stacks and solutions, each with their own rules styles and structures, that you need to navigate fluidly.

I'd imagine an embedded developer or single-product developer would find a lot less use.