Ainsofs Blog: Technology insights from the Pacific Islands

TL; DR AI has significantly impacted my business. I have leveraged it to be more productive and more knowledgeable on different aspects of my work. From learning different languages to researching different approaches to a problem. It’s not perfect, but it’s a tool that needs to be used by every developer. It’s been over a year since I started experimenting with AI. I've been using it in the following ways: Content creation - You can ask it to generate an outline for a presentation, workshop, or blog post. I've also used it draft technical reports and systems specifications. Ideation - Exploring ideas and flushing them out. Coding – From generating code, to code review, generating documentation to writing tests. If you provide the appropriate context, it does a great job. Troubleshooting - Copy and paste errors into the AI to provide an explanation of potential causes and fixes. Research - When you want to find out more a

I've started experimenting with DDEV for local development environments. It provides simple commands to quickly get you up and running compared to docker4drupal . However docker4drupal has the upper-hand when you want to restore databases into your dev environment. Its easier and faster compared to drush sqlc or DDEV commands. To enable this feature on docker4drupal, uncomment these lines in the mariadb container. Next create a folder called mariadb-init and drop your db in there then start up your container. It will pickup any files with *.sql or *.sql.gz If your container is already running you'll need to restart it. I find that its easier to destroy it and start again. docker compose stop mariadb && docker compose rm -f mariadb && docker compose up -d Tip: Ive made this easier by adding an alias called dbdb to run the above. Now if I need to debug an issue using a snapshot of production data, I can load it into the mariadb-init folder and run dbdb to start