I found it hard to use entities with more than 4 Attributes when defining them as simple compounds like

person(Firstname, Lastname, Gender, Age, State, Country).

Accessing the attributes by position makes the code hard to read because one has to remember the position and mistakes are not catched because there is no type system.

Would you recommend using the libray record or using dicts in swi-prolog? This would make the code non portable. Moreover, do you recommend dedicated strings or list of atoms to represent strings?

Hey! Grakn person here.

The Prolog syntax is very elegant but it could be clunky, I totally agree. Our syntax has resource and role names instead of relying on position:

e.g.

match $x has lastname "some last name";

I wonder what is the best strategy to this problem:

You take the initiative and develop a new feature, automate a task, increase productivity, optimise costs, or increase revenue. You would like to reap the benfits (promition, bonus) but not increase your workload or take the blame for bugs that are unavoidable in the new tech.

1. Automate tasks and keep it to yourself or your immediate team and hopefully work less.

2. Talk to your boss before you reveal your solution, such that he will 'discover' it and let it be his idea. Depending on your idea, this might be hard.

Any other ideas?

Develop your solution but don't actually implement it. When the problem is discussed offer to fix it in a short amount of time (faster then the actual time). Everybody will remember you as the one being most profitable for the company.