Domenico Lupinetti Ostico

La Postazione di Sviluppo Potenziata dall'IA — Cos'è, Perché Funziona e Dove Non Va

Buongiorno a tutti. Voglio parlarvi di qualcosa che sto costruendo e usando da diversi mesi — una postazione di sviluppo che mette l'intelligenza artificiale al centro del flusso di lavoro quotidiano. Non come chatbot in una barra laterale. Come infrastruttura.

Vi guiderò attraverso cos'è lo stack, in cosa è davvero bravo, e — perché credo nell'onestà — dove non funziona e cosa mi dà fastidio.

The AI-Augmented Developer Workstation — What It Is, Why It Works, and Where It Hurts

Good morning everyone. I want to talk about something I've been building and running for the past several months — a developer workstation that puts AI at the center of the daily coding workflow. Not as a chatbot in a sidebar. As infrastructure.

I'll walk you through what the stack is, what it's actually good at, and — because I believe in honesty — where it falls short and what annoys me.

Developer Workstation Backup & Restore Recipe

Back up your AI-assisted development environment and restore it on a fresh machine

Prerequisite: The target machine must have completed developer-workstation-setup.md before restoring
Target: Ubuntu 24.04 LTS / macOS 14+ (same platforms as the setup recipe)
Time: ~5 minutes backup, ~10 minutes restore
Tested with: Signet 0.98.7, OpenCode 1.4.3, Oh-My-OpenAgent 3.12.3

Developer Workstation Setup Recipe

OpenCode + Signet Memory + Oh-My-OpenAgent + Local MCP Tooling

Target: Ubuntu 24.04 LTS (or any Debian-based Linux) / macOS 14+ (Sonoma/Sequoia)
Windows: via WSL recommended — see Windows appendix for native
Audience: Junior developers comfortable with the terminal
Time: ~30 minutes
Tested versions: Node 22, OpenCode 1.4.22, Oh-My-OpenAgent 3.17.5, Signet 0.108.0, uv 0.11.1, Python 3.13

Give your host access to Docker containers with macvlan

Let's assume you have a macvlan interface running.

#$ docker network inspect test_loc-macvlan

[

How to use a custom `resolv.conf` file with systemd-resolved in Ubuntu

Stages

Disable and stop the systemd-resolved service:
```
sudo systemctl stop systemd-resolved
```
Then put the following line in the [main] section of your /etc/NetworkManager/NetworkManager.conf:

Keybase proof

I hereby claim:

I am ostico on github.
I am ostico (https://keybase.io/ostico) on keybase.
I have a public key ASBfbyMT0Msc0514ycsCd1gMb-kfWTDNyP-_MeB8nJ75ygo

To claim this, I am signing this object:

	#!/bin/bash

	#
	# copy this into /etc/profile.d/instance-name-tag.sh
	#
	# you will need:
	# - curl, jq, and aws cli installed
	# - an IAM role that gives the EC2 instance access to describe tags
	#

	# maximum capability of system
	user@ubuntu:~$ cat /proc/sys/fs/file-max
	708444

	# If this limit is too low, you can increase the available limit to say 200000
	user@ubuntu:~$ sudo vim /etc/sysctl.conf

	# add the following line to it
	fs.file-max = 200000

	#!/bin/bash
	ps -ylC apache2 --sort:rss \| awk '{sum+=$8; ++n} END {print "Tot="sum"("n")";print "Avg="sum"/"n"="sum/n/1024"MB"}'