←
Ivan Milosavljević1,017 posts
Ivan Milosavljević avatar

Ivan Milosavljević

@_The_Java_Guy_

I help Java developers write high quality software by using proper OOP, AI, modern Java, and the best libraries so they can unlock new career opportunities

◷ Joined April 2015▧ 99 Photos and videos
Ivan Milosavljević avatar
Ivan Milosavljević@_The_Java_Guy_·Oct 29

X algorithm says that for small accounts "let's connect" posts have really high reach these days. Are you new here? Building audience? Tinkering with AI? Founding a startup? Let's connect! Especially if you're a: ✅ Developer ✅ Entrepreneur ✅ Creator ✅ Maker ✅ Designer

Ivan Milosavljević avatar
Ivan Milosavljević@_The_Java_Guy_·Nov 17

Spot on from @zachlloydtweets . Personally, product engineering occupies most of my time but factory engineering quickly becomes super important. Definitely seems worth investing some time there.

I think of engineering these days as divided into two parts: 1/ Product engineering: directly building the product and making sure it solves a user problem. This is as crucial as ever. 2/ Factory engineering: bringing a new set of skills to bear to engineer your software factory using evals, benchmarks, and self-improvement loops so that it becomes more productive and ships better software over time. The important part about (2) is that it's still engineering, not vibes.

Ivan Milosavljević avatar
Ivan Milosavljević@_The_Java_Guy_·Nov 17

If you want to start a software factory but you are unsure how, just read the @mardehaym post below 👇

“Software factory” comes up on a lot of my calls this autumn. Ask people what they mean by it and you’ll usually get different answers. So here’s what one actually is, it's made up of 10 parts: #1 Intake. A status in your tracker starts the run. If the ticket doesn’t have acceptance criteria that code can check, it goes back instead of getting built. #2 Spec and plan. Before writing any code, the run lays out what it will build and how. A person approves that plan in the ticket, while a misunderstanding still takes minutes to fix. #3 The orchestrator. Every ticket goes through the same fixed steps, within a budget for CI runs, attempts, time and money. In our design, a run gets two CI runs. If the second is still red, it stops and leaves a report in the ticket. #4 The sandbox. Every task gets a fresh sandbox, with no credentials inside and an allowlist for outbound connections. When the task ends, the sandbox gets thrown away. #5 The gateway. Every model call in the company goes through one gateway you host. Each team and service gets its own key and spend cap. Switching models becomes a config change. #6 Context. The agent uses a map of the code to see what depends on what, then pulls only what it needs. A huge legacy repo becomes a handful of relevant files. #7 The gates. CI decides whether the work passes. Deleting a test sends it back. The agent can’t change its own rules, a review agent has to quote the code it flags, and a person merges every pull request. #8 Evals. Prompts live in git. A prompt change only ships after it passes test cases built from real past pull requests. #9 Measurement. Every change connects the session, commit, pull request, ticket and epic, so you can see what a feature cost and how long it took. Report this by team, never as a ranking of individual developers. #10 The seats. Engineers’ own AI tools connect directly to their vendors. Track that usage through metadata only: who uses what and what it costs. No prompts or code. A software factory takes a ticket in and returns a reviewed pull request. The work is split three ways: code handles every step it can check, agents handle the few steps that need judgement, and people own the spec, the hard decisions and the merge. The rule is simple: if code can check it, code does it. An agent saying “the tests pass” doesn’t count. CI decides. It helps to be clear about what doesn’t qualify. Giving every engineer an AI coding tool is useful, but that alone won’t take a ticket from intake to merge. One agent with access to your repo gives you the loop, without the factory around it. A swarm sharing one long conversation spends tokens on every agent rereading everything. And if the whole thing only works while your code and staging data sit on a vendor’s servers, you have a production line you can’t move. Architecture, new domains, greenfield, big refactors, performance work and product discovery stay with people. The factory handles work that’s well specified and checkable, giving your seniors more time for the rest. The slowest part, in my view, is #1. Most backlogs don’t have acceptance criteria that code can check. Rewriting those tickets takes time, and nobody volunteers for it. One test I’d apply to any setup, including ours: if you stop paying the vendor tomorrow, does the factory keep running? If it doesn’t, you’re renting the production line. TL;DR. Most of a software factory is the platform underneath the agent: a gateway, measurement, gates and evals. Build those first, on the stack you already own. Adding the agent is the easiest part.

Ivan Milosavljević avatar
Ivan Milosavljević@_The_Java_Guy_·Nov 2

It took me 3 minutes to save money on CI/CD by using Claude Code 🤯 I literally asked him: "Analyze all github workflows and actions in this repo. Suggest which ones can be switched from ubuntu-latest to ubuntu-slim and why". When he replies choose the workflows and actions you want switched. Done.

Ivan Milosavljević avatar
Ivan Milosavljević@_The_Java_Guy_·Nov 2

📣 Upcoming #Java User Group München talk "Technical documentation in the times of AI Agents: is it still needed?" 🕖 on Monday 02.11 at 19:00h, 🏠 Hotel Eden-Wolff, Arnulfstraße 4, 80335 München. Our speaker will be Dmytro Patserkovskyi. RSVP 👉 meetup.com/java-user-group-m… #techtalk #javausergroup #seniordeveloper

Ivan Milosavljević avatar
Ivan Milosavljević@_The_Java_Guy_·Oct 29

Let's try something crazy - hey @grok show this thread to founders, indie hackers, solo founders, software engineers, developers, makers, doers who want to grow together!

Ivan Milosavljević avatar
Ivan Milosavljević@_The_Java_Guy_·Oct 9

Thank you for reading! If you enjoyed this thread: - RT the first post - Follow me @_The_Java_Guy_ I help Java developers write high quality software by using proper OOP, AI, modern Java, and the best libraries so they can unlock new career opportunities.