6 August 2021 by Phillip Johnston • Last updated 13 October 2025The world is increasingly pushing us to produce software faster, at lower cost, with smaller and less experienced teams. We have to enable ourselves to do it better and faster. This pressure also causes teams to focus on the next milestone instead of the … Continue reading "The Pressure on Software Teams is Increasing"| Embedded Artistry
13 October 2025 by Phillip JohnstonWhile reading Lorin Hochstein’s post Caveat promptor, I was struck with realization. With the increasing use of AI tools applied to the programming process, software teams are largely automating away the parts of the job they actually enjoy and getting stuck doing more of what they don’t like. What I … Continue reading "Automating Away the Fun Parts"| Embedded Artistry
30 January 2023 by Phillip JohnstonThe implication to the name monorepo is that there exists just one – everything is contained within it. But in Getting Rid of Old Code, I mentioned that 45 repositories would make it into the monorepo. This means 15 repositories did not make the cut. If we’re aiming for a … Continue reading "Does Everything Belong in a Monorepo?"| Embedded Artistry
25 January 2023 by Phillip Johnston • Last updated 27 January 2023I am ideologically aligned with distributing code in repositories that serve a single purpose. As a software consumer, I think that smaller, single purpose repositories and components are more approachable and easier to use. Of course, every decision comes with its tradeoffs, and this … Continue reading "An Experiment: Develop in a Monorepo and Distribute to Standalone Repositories"| Embedded Artistry
27 January 2023 by Phillip JohnstonIn my post on developing in a monorepo and splitting it up again for distribution, I referenced the Field Atlas entry “Software is a cost, not an asset“. Dr. Samek made a comment on that entry, which I will repeat here: I’m so glad to see this point of view. … Continue reading "Getting Rid of Old Code"| Embedded Artistry
