There are things that are worth being patient about. Jira isn’t one of them.
“Give not that which is holy unto the dogs, neither cast ye your pearls before swine, lest they trample them under their feet, and turn again and rend you.”
Not sure if this is a part of it, but there are places where "engineer" is a protected title that requires a degree or license. I work with a bunch of folks in Quebec and they have to use the title "software developer" unless they are a member of the Order of Engineers. I find this to be pretty silly considering someone can have a degree in Mechanical Engineering and use the title "Software Engineer" but someone with a degree in Computer Science can't.
The less rigorous and more vague some theory is, the easier it is to use it to make unfalsifiable claims. That's the essence of the current discussion around AGI. No one knows what it is or describe it concretely so it can do anything and everything and everyone's going to lose their jobs.
It's funny because of the irony of "prompt engineering" being as close to cargo culting as things get. No one knows what the model is or how it's structured in a higher level (non implementation) sense, people just try different things until something works, and try what they've seen other people do.
This article is at least interesting in that it takes a stab at explaining prompt efficacy with some sort of concrete basis, even if it lacks rigor.
It's actually a really important question about LLMs: how are they to be used to get the best results? All the work seems to be on the back end, but the front end is exceedingly important. Right now it's some version of Deep Thought spitting out the answer '42'.
I think the analogy is to construction, not engineering.
In construction, architects and designers do different jobs. The software equivalents of those roles map reasonably well to the construction equivalents.
In my (software) experience, the terms are basically interchangeable. Some people will violently defend “architect right, design wrong” and others the opposite, So uh, pretty hard for me, a normal person, to care much about which word is right for the “you sit down and think before you build” part of software engineering.
In my country, we have both the academic title "engineer", and "engineer architect". People view this as "proper engineer" and "not so proper engineer".
Anyway, "you sit down and think before you build" is indeed what you want and the word for that is "strategy".
IMHO there are plenty of available and cheap .com domains but you have to be creative. From my experience ai tools aren't creative enough for coming up with unique and good sounding names.
