8

I know no Latin, but playing around with Google Translate I came up with "Non insectum opus est". Insectum seems like a good stand in for a generic bug, but maybe blatta is better (see http://www.catb.org/jargon/html/B/bug.html)? And opus carries the connotation that the entire program is as designed.

Joonas Ilmavirta
  • 113,294
  • 21
  • 192
  • 587
ManicPolymath
  • 177
  • 1
  • 4
  • As a counterfactual study into the matter, I wonder if there is any language that translated 'bug', 'feature' and is using as a standard in daily language. I feel like all developers just gave up and they are using all these terms in English anyway. So if Latin was alive, it could possibly take the same road. I think, to have these words in Latin, we would need to first author many software books in Latin to have a real playground, otherwise everybody might invent their own. Might be good to find some examples in internet to see if people intuitively came up with the same words. – oguzalb Sep 07 '20 at 07:56
  • 7
    @oguzalb I'm no developer, but in normal Finnish I'd express "not a bug but a feature" as "ei vika vaan ominaisuus", which literally has the somewhat broader meaning of "not a fault but a property". Words like this exist in many languages, including Latin, but their meaning is rarely confined to software. – Joonas Ilmavirta Sep 07 '20 at 13:38
  • 2
    @oguzalb: you seriously underestimate us, French people who decided to rewrite computer language so that the world may have a laugh. The French word for "bug" is "bogue" (http://jargonf.org/wiki/bogue - it is actually the name of the spiky cover of chestnut and was allegedly chosen as such on purpose) – WoJ Sep 08 '20 at 05:43
  • It needs to be noted that "It's not a bug, it's a feature" is often used as an excuse for re-categorizing the perceived aberrant behavior. And sometimes it's used in a jocular fashion. – Hot Licks Sep 08 '20 at 22:13
  • @WoJ well the same approach is also tried for Turkish in some universities, and those scholars are actually teaching with those words. I mean words that also cover "register", "chip" etc and Turkish is not based on Latin words, so they are totally new and very different to the English ones. But those don't reach to the actual sector, people generally make fun of them Thanks for the link though, I can read some French, will have a look, will be very interesting – oguzalb Sep 09 '20 at 22:37
  • @oguzalb: we have a culture of strongly protecting our language. This is sometimes great, and sometimes simply ridiculous. There was an official dictionary of computer-related words built in the '90s. Some of the words proved that the writers were clearly under influence when they invented the words. Some others caught up. Today we use a mix, sometimes several words for one action (say, to reboot will be rebouter (an anglcism - it will be written as rebooter), or redémarrer (restart)). – WoJ Sep 10 '20 at 06:22

1 Answers1

27

Google Translate is unreliable with Latin and you should not take anything it gives seriously. The suggestion non insectum opus est sounds like "an insect is not work".

I am not aware of good Latin words for "bug" or "feature". Therefore I would take a different approach and suggest:

Non forte sed ratione.
Not by chance but by design.

Another option is to go with participles:

Non ruptum sed designatum.
Not broken but designed.

If you refer to something specific, remember that the Latin participle needs the correct form (gender and number). As just a general rule without referring to any single thing, I think singular neuter works well.

You can also substitute erratum (misstep, mistake) for ruptum (broken). This should be seen as a noun (errare is intransitive, so erratum is best seen as a derived noun rather than a participle). If you want to shift nuance from "broken" to "misstep", you can say Non erratum sed designatum.

Joonas Ilmavirta
  • 113,294
  • 21
  • 192
  • 587
  • 1
    Playing off of that format, which to me retains the general flow and feel of the english, what about something like Non comminutus sed ratione, "not broken but by design". – Adam Sep 07 '20 at 13:27
  • 1
    @Adam I think the parallelism works better if you have two participles, "not broken but designed". How does non ruptum sed designatum sound? – Joonas Ilmavirta Sep 07 '20 at 13:35
  • 2
    I like that! This is a phrase I encounter at work a lot, so I'm very familiar with the original. Oh, one additional I idea from my wife: non erratum sed designatum – Adam Sep 07 '20 at 13:46
  • 1
    @Adam I haven't checked carefully, but my impression is that errare is "to take wrong step" rather than "to break". Which one is more appropriate depends on context, but I think breaking fits a little better. But I'd be happy to see other suggestions! There must be a number of nouns, participles, adjectives, and adverbs one could use. – Joonas Ilmavirta Sep 07 '20 at 13:58
  • 2
    "Wrong step" is absolutely perfect for a programming bug! – ManicPolymath Sep 07 '20 at 17:15
  • 1
    @ManicPolymath I added a note on that. – Joonas Ilmavirta Sep 07 '20 at 17:22
  • Perhaps "not by error but by design", which (I think?) would be something like non errato sed designato (ablative, rather than nominative). – chepner Sep 07 '20 at 18:17
  • or perhaps use intentio? – Hagen von Eitzen Sep 07 '20 at 20:15
  • There are some nice suggestions in these comments. They should be given as other answers; I'm happy enough with mine and I don't think I'll expand further. – Joonas Ilmavirta Sep 08 '20 at 04:55
  • 2
    The problem with this excellent answer is that the phrase "feature, not bug" is used to refer to the properties of software that were in fact not designed. Usually this phrase is used to express "I didn't intend for it to be that way, but the code is already written and I'm satisfied with its behaviour even if you are not". In Hebrew, lacking the word "feature", I would substitute the word "advantage". Other viable words might be "trait", "property", or "difference" if Latin has those words. – dotancohen Sep 08 '20 at 18:42
  • @dotancohen Oh! I always took it so that the saying referred to the program working as planned despite the user thinking otherwise. The key message here is: If one asks a translation question and wants specific nuance, the nuance must be explained explicitly in the question. With no explanation, we can't really tell what the intention here was. I'd be happy to read if anyone wants to take the point of view you propose and write a second answer. – Joonas Ilmavirta Sep 08 '20 at 20:02
  • 1
    When I asked the question I had indeed thought about "feature" being "as explicitly designed", but I am curious what the Latin would be for "not a failure, but a happy accidental success". – ManicPolymath Sep 09 '20 at 23:39
  • @ManicPolymath To get visibility for that question, I recommend asking it separately as a new question. I would be curious to read the answer(s) too! – Joonas Ilmavirta Sep 10 '20 at 05:57