<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Local-Development on F. Latini - IT Engineer</title><link>https://latini.dev/tags/local-development/</link><description>Recent content in Local-Development on F. Latini - IT Engineer</description><generator>Hugo</generator><language>en</language><lastBuildDate>Thu, 05 Nov 2026 08:00:00 +0000</lastBuildDate><atom:link href="https://latini.dev/tags/local-development/index.xml" rel="self" type="application/rss+xml"/><item><title>Your Paved Road Starts at git push</title><link>https://latini.dev/posts/your-paved-road-starts-at-git-push/</link><pubDate>Thu, 05 Nov 2026 08:00:00 +0000</pubDate><guid>https://latini.dev/posts/your-paved-road-starts-at-git-push/</guid><description>&lt;p&gt;&lt;strong&gt;TL;DR&lt;/strong&gt; - Ask a platform team what their road covers and they will describe everything that happens after &lt;code&gt;git push&lt;/code&gt;: the pipeline, the deploy, the dashboards, the rollback. Ask what happens before the push and you get a link to a README. That is backwards, because the inner loop - clone, run, change something, see it work - is where developers spend most of their day, and it is the one part of the job every engineer pays for separately, in every repository, every time they move teams. A three-day local setup is not a rite of passage. It is a platform defect with no owner, documented in a file nobody has followed from scratch in a year. Pave it the same way you paved the rest: one command from the template that takes a clean machine to a running service, an explicit decision for every dependency (run it, fake it, or reach a shared one), local credentials from identity rather than a &lt;code&gt;.env&lt;/code&gt; pasted in Slack, seed data that actually exists, and a measured clone-to-running time that a stranger can hit.&lt;/p&gt;</description></item></channel></rss>