{"id":2261,"date":"2026-08-19T19:01:15","date_gmt":"2026-08-19T12:01:15","guid":{"rendered":"https:\/\/lazarewww.ru\/cases\/dev-platform-2\/"},"modified":"2026-08-19T19:01:15","modified_gmt":"2026-08-19T12:01:15","slug":"dev-platform","status":"publish","type":"isotope","link":"https:\/\/lazarewww.ru\/en\/cases\/dev-platform\/","title":{"rendered":"Dev Platform"},"content":{"rendered":"
\n\t\n\n
\n\t\t\t\n\n

Introduction:<\/h2>\n\n\t<\/div>\n\n\n\n
\n\t\t\t
\n\t\t\t\n\n

It started with an everyday annoyance. I didn’t want to carry a bulky laptop around and was looking for a way to write code from my phone.<\/p>\n\n\n\n

I tried Linux emulation on Android, installed code-server. Working in a browser was possible, but it wasn’t the full cycle: without plugins and half of what a real editor can do, it never got further than editing a couple of files.<\/p>\n\n\n\n

Meanwhile development itself was changing \u2014 more and more of the work was moving into generation under my control. And then I got a server of my own. That settled the question for good: how do I work from any device without installing anything on it.<\/p>\n\n\t\t<\/div>\n\t<\/div>\n\n<\/div>\n\n\n

\n\t\n\n
\n\t\t\t\n\n
\"Dev
A full terminal on a phone \u2014 the same session that was open on the laptop.<\/figcaption><\/figure>\n\n\t<\/div>\n\n\n\n
\n\t\t\t\n\n
\"Dev
The keys an on-screen keyboard doesn’t have get their own bar, with sticky modifiers.<\/figcaption><\/figure>\n\n\t<\/div>\n\n<\/div>\n\n\n\n
\n\n\n
\n\t\n\n
\n\t\t\t\n\n

How it went:<\/h2>\n\n\t<\/div>\n\n\n\n
\n\t\t\t
\n\t\t\t\n\n

The first version was a terminal in the browser.<\/strong> I put it together on off-the-shelf libraries first, then moved to my own implementation: other people’s solutions hit a ceiling exactly where things got interesting. In May 2026 I rewrote everything on Laravel and Vue \u2014 that version ran for a week alongside the old one, on the same server, so I could compare and roll back.<\/p>\n\n\n\n

Then a team environment was needed.<\/strong> The tool I was building for myself turned out to be useful to more people than me. From that point on the terminal stopped being the product and became one part of the platform.<\/p>\n\n\t\t<\/div>\n\t<\/div>\n\n<\/div>\n\n\n

\n\t\n\n
\n\t\t\t
\n\t\t\t\n\n

The terminal isn’t the point in itself. All the work goes through CLI agents: we treat it as a discipline to set up a proper agent system for every project \u2014 with roles, a review procedure and a canon of its own. A system like that lives in the command line, which means there are a lot of terminals, they run long, and they have to be kept somewhere. Hence the sessions, the splits and everything else around them.<\/p>\n\n\t\t<\/div>\n\t<\/div>\n\n<\/div>\n\n\n

\n\t\n\n
\n\t\t\t
\n\t\t\t\n\n

Sessions instead of a terminal.<\/strong> A work session lives in its own container at the operating-system level: its own file system, its own processes, its own memory and disk limits. Not a project folder but a machine in its own right. A neighbour can’t reach into it, even if they want to.<\/p>\n\n\t\t<\/div>\n\t<\/div>\n\n<\/div>\n\n\n

\n\t\n\n
\n\t\t\t\n\n
\"Dev
Personal and team environments: statuses, entry points, last activity.<\/figcaption><\/figure>\n\n\t<\/div>\n\n<\/div>\n\n\n
\n\t\n\n
\n\t\t\t\n\n
\"A
A live session: the agent is working, output streams in real time.<\/figcaption><\/figure>\n\n\t<\/div>\n\n<\/div>\n\n\n
\n\t\n\n
\n\t\t\t\n\n
\"Two
Two sessions side by side in one window.<\/figcaption><\/figure>\n\n\t<\/div>\n\n\n\n
\n\t\t\t\n\n
\"The
The same split in the dark theme.<\/figcaption><\/figure>\n\n\t<\/div>\n\n<\/div>\n\n\n
\n\t\n\n
\n\t\t\t
\n\t\t\t\n\n

Working with files.<\/strong> Project tree, editor, search. Together with the sessions, that is what closed the original task \u2014 files and terminal together now replace an editor with plugins, and cover more ground than it did. The project didn’t grow into that at once.<\/p>\n\n\t\t<\/div>\n\t<\/div>\n\n<\/div>\n\n\n

\n\t\n\n
\n\t\t\t\n\n
\"Dev
File tree, tabs of open files, and the editor with highlighting.<\/figcaption><\/figure>\n\n\t<\/div>\n\n<\/div>\n\n
\n\t\n\n
\n\t\t\t\n\n
\"Split
Split: two files side by side in one window.<\/figcaption><\/figure>\n\n\t<\/div>\n\n<\/div>\n\n
\n\t\n\n
\n\t\t\t\n\n
\"Dev
Markdown: source on the left, rendered view on the right \u2014 edits show up immediately.<\/figcaption><\/figure>\n\n\t<\/div>\n\n<\/div>\n\n
\n\t\n\n
\n\t\t\t\n\n
\"Project
Project relationship map: 500 of the graph’s 2123 nodes in frame.<\/figcaption><\/figure>\n\n\t<\/div>\n\n<\/div>\n\n
\n\t\n\n
\n\t\t\t\n\n
\"Project
Schema listing: database tables, with the migrations and the model of the selected one on the right.<\/figcaption><\/figure>\n\n\t<\/div>\n\n<\/div>\n\n
\n\t\n\n
\n\t\t\t\n\n
\"Project
Index search: migrations, methods and controllers in one set of results.<\/figcaption><\/figure>\n\n\t<\/div>\n\n<\/div>\n\n\n
\n\t\n\n
\n\t\t\t\n\n

A kanban for development.<\/strong> Task boards with time tracking, team sections, access control. The things without which two or more people can’t use a tool every day.<\/p>\n\n\t<\/div>\n\n\n\n

\n\t\t\t\n\n
\"Dev
The board: columns scroll sideways, a card opens full screen.<\/figcaption><\/figure>\n\n\t<\/div>\n\n<\/div>\n\n\n
\n\t\n\n
\n\t\t\t\n\n
\"Dev
Task boards grouped by team section.<\/figcaption><\/figure>\n\n\t<\/div>\n\n<\/div>\n\n
\n\t\n\n
\n\t\t\t\n\n
\"Dev
A board in use: columns by stage, cards carry a priority and an assignee.<\/figcaption><\/figure>\n\n\t<\/div>\n\n<\/div>\n\n
\n\t\n\n
\n\t\t\t\n\n
\"Dev
Presence: you can see who is in a card right now and how much time has gone into it.<\/figcaption><\/figure>\n\n\t<\/div>\n\n<\/div>\n\n
\n\t\n\n
\n\t\t\t\n\n
\"Dev
Analytics: closed per day and a cumulative curve across all boards.<\/figcaption><\/figure>\n\n\t<\/div>\n\n<\/div>\n\n\n
\n\t\n\n
\n\t\t\t
\n\t\t\t\n\n

Automation.<\/strong> Since August a bot has been picking up tasks from the kanban: it takes a card from the right column, spins up a session, drops the brief into it and drives it to a result. The verdict on readiness is a separate step \u2014 «done» doesn’t happen by itself. A snapshot of the state is attached to the card, and a notification goes out to the messenger.<\/p>\n\n\t\t<\/div>\n\t<\/div>\n\n<\/div>\n\n\n

\n\t\n\n
\n\t\t\t\n\n
\"Dev
The card: description, checklists, attachments, discussion \u2014 and the brief for the agent.<\/figcaption><\/figure>\n\n\t<\/div>\n\n<\/div>\n\n\n
\n\t\n\n
\n\t\t\t\n\n
\"The
The bot panel: binding to a board and an environment, and a log of its steps on the task.<\/figcaption><\/figure>\n\n\t<\/div>\n\n<\/div>\n\n\n
\n\t\n\n
\n\t\t\t
\n\t\t\t\n\n

A word on verification, separately, because in work like this it is the main thing. The trouble with generation isn’t broken code \u2014 broken code shows itself straight away. The trouble is a plausible result with an invented justification. So verification here isn’t the goodwill of whoever did the work, it’s a mandatory stage.<\/p>\n\n\n\n

Once I had to restore all of it.<\/strong> In June the server disk died. The platform came back from backups in twenty-four hours.<\/p>\n\n\t\t<\/div>\n\t<\/div>\n\n<\/div>\n\n\n\n

\n\n\n
\n\t\n\n
\n\t\t\t\n\n

Result:<\/h2>\n\n\t<\/div>\n\n\n\n
\n\t\t\t
\n\t\t\t\n\n

The platform has been in use since June 2026. There are six teams on it now \u2014 development, product and adjacent departments. Each has an environment of its own, plus personal ones that are started and shut down as needed.<\/p>\n\n\n\n

Inside: sessions in isolated environments, files, an editor, task boards, automation, backups, quotas. From the outside \u2014 a single link in a browser. A phone will do.<\/p>\n\n\n\n

The original task it all started with was solved along the way: you can work from any device.<\/p>\n\n\t\t<\/div>\n\t<\/div>\n\n<\/div>\n\n\n\n

\n\n\n
\n\t\n\n
\n\t\t\t\n\n

My role:<\/h2>\n\n\t<\/div>\n\n\n\n
\n\t\t\t
\n\t\t\t\n\n

The project is entirely mine \u2014 the idea, the architecture, the code. I wrote every version, from the first terminal to the platform as it is now.<\/p>\n\n\t\t<\/div>\n\t<\/div>\n\n<\/div>\n\n\n\n

\n\n\n
\n\t\n\n
\n\t\t\t\n\n

Stack:<\/h2>\n\n\t<\/div>\n\n\n\n
\n\t\t\t
\n\t\t\t\n\n

Laravel \u00b7 PHP 8.3 \u00b7 PostgreSQL 18 \u00b7 Redis \u00b7 Vue 3 \u00b7 TypeScript \u00b7 Incus \u00b7 WebSocket<\/p>\n\n\t\t<\/div>\n\t<\/div>\n\n<\/div>\n","protected":false},"excerpt":{"rendered":"

An internal workspace for a development team: work sessions in isolated environments, task boards with time tracking, and full-scale work from any device.<\/p>\n","protected":false},"featured_media":2089,"template":"","isotope_tag":[90,89],"class_list":["post-2261","isotope","type-isotope","status-publish","has-post-thumbnail","hentry","isotope_category-web-apps-en"],"acf":[],"_links":{"self":[{"href":"https:\/\/lazarewww.ru\/?rest_route=\/wp\/v2\/isotope\/2261","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/lazarewww.ru\/?rest_route=\/wp\/v2\/isotope"}],"about":[{"href":"https:\/\/lazarewww.ru\/?rest_route=\/wp\/v2\/types\/isotope"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/lazarewww.ru\/?rest_route=\/wp\/v2\/media\/2089"}],"wp:attachment":[{"href":"https:\/\/lazarewww.ru\/?rest_route=%2Fwp%2Fv2%2Fmedia&parent=2261"}],"wp:term":[{"taxonomy":"isotope_tag","embeddable":true,"href":"https:\/\/lazarewww.ru\/?rest_route=%2Fwp%2Fv2%2Fisotope_tag&post=2261"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}