Skip to main content


The "Code-Rich" Organization: How Automatic Code Generation Will Revolutionize Everything

  I put on paper a couple of thoughts about AI and Large Language Models (LLM) for automatic code generation in the development process. My thesis is that the current organizations are mostly “code-thin”, where only the basic Business Processes are modeled through software, while in the future we will have “code-rich" organizations boosted through the abundant and cheap AI and LLM Generated software code. These “code-rich” organizations, where every possible business process is software based - will outperform the usual "code-thin" organizations, where software is “hand-made” and expensive. Feedback would be very, very appreciated.
Recent posts

Crypto Lorem Ipsum

 After a long pause, I come back to this blog to annouce my last discovery: there is a web site for generating crypto-related Place Holders... no wait, placeHODLers... Incredible! (The problem is, the text it generates is suspiciously similar to a 2018 normal ICO)

Can't use the newest npm when node is installed with brew (MacOs)

Even though I installed and reinstalled node with brew, with last versione 11.8.0, apparently it kept using the last version fdecollibus$ npm install --global gatsby-cli npm WARN npm npm does not support Node.js v11.8.0 npm WARN npm You should probably upgrade to a newer version of node as we npm WARN npm can't make any promises that npm will work with this version. npm WARN npm Supported releases of Node.js are the latest release of 4, 6, 7, 8, 9. npm WARN npm You can find the latest version at /usr/local/Cellar/node/11.8.0/bin/gatsby -> /usr/local/Cellar/node/11.8.0/lib/node_modules/gatsby-cli/lib/index.js + gatsby-cli@2.4.8 npm -v gave me back version 5.6.0. I've therefore noticed that  /usr/local/lib/node_modules had wrong permissions assigned to root:wheel. A chown did not fix the problem: I've had to manually delete the content of the folder (cd / usr/local/lib/node_modules and -careful - type rm -rf

Multiple controllers with Spring Boot

Remember, when you want to have multiple controllers with Spring Boot, you should always name them differently in the annotation, otherwise they will not work So these two together will NOT work (or just one of them will work) These two instead WILL work.

DNS problems when running an Ethereum cluster on Docker Swarm

To run privately an ethereum cluster, the nodes have to find each other through a bootnode. The address of the bootnode has to be an IP address. When we run a bridged network we can set manually the ip address, but this option is not currently supported by the overlay network needed by swarm. Therefore in our init script we run a simple resolution command based on the image name "bootnode". Problem was that the nodes were still unable to connect and no mining would happen. After investigating, I've noticed that the address resolved with the name of the service was not consistent. Inside the docker container: root@84cba6d65c3d:/geth# host ethnode4 ethnode4 has address root@84cba6d65c3d:/geth# host tasks.ethnode4 tasks.ethnode4 has address The right address was .4 where the system was answering , with .3 other containers were not able to connect.  Therefore I change the bash script to fetch the bootnode ip by prepending the hostname with

When adding a property to graph-tool don't forget this

When you are adding a new property to a graph-tool graph ( is_node_customer = network.new_vertex_property("bool") weight = network.new_edge_property("float")  you should never forget to add this network.vertex_properties["is_node_customer"] = is_node_customer network.edge_properties["weight"] = weight Otherwise the properties will not saved or stored together with the graph and you will lose a lot of time