I had a good day today. There are plenty of folks who didn’t, and I hope tomorrow is better. Let’s read some tech news and be optimistic about what’s ahead of us.
[article] The best open source software of 2023. Solid list of projects, some new (e.g. Bun, LangChain) some old (e.g. PostgreSQL, Istio). Skim through and find one or two that are new to you.
[article] How to Stop Taking Work So Personally. I’ve definitely had to stop and disconnect my personal identity from my work at times. It’s not necessary, or healthy, to wrap yourself up in the work you do.
[blog] Dev First Founder Toolkit. This links to a set of posts that help startups (and really, anyone) focused on developer products.
[blog] .NET 8 Top 10 New Features. .NET seems to ship new language versions every other day, but each time, there are nice new optimizations.
[blog] Model Collapse: An Experiment. When you train AI models using their own output, good things don’t happen. Original content is as important as ever.
[blog] Automating dead code cleanup. Some guidance from the engineering folks at Meta, with particular focus on dependencies.
[article] Despite the Hype, Engineers Not Impressed with DORA Metrics. The headline doesn’t reflect the piece itself; teams that know about DORA use the metrics, and only 6% thought the metrics weren’t useful. But hey, controversy sells!
##
Want to get this update sent to you every day? Subscribe to my RSS feed or subscribe via email below:
Happy Monday. I had an enjoyable weekend, including a couple of bike rides with my daughter. Now I’m sore, but she’s happy, so that’s all that matters. For today’s reading list, you’ll get some AI, some developer categorization, and an intro to “slowification.”
[blog] Rearchitecture is a sign of success not failure. Short post, good reminder. If you have to rearchitect a system, manage tech debt, or run a legacy system, that’s indicative of something that produced value.
[blog] Data Duets with BigQuery and Gen AI. Getting help writing or understanding SQL queries is useful, right? This post shows that capability in BigQuery and Colab.
[article] Primer: Cloud Development Environments, or CDEs. If you’re not using these now, I suspect you’ll put an entry into your 2024 plan to explore them further. Worthwhile investigation.
[article] An incident management lens on DORA 2023. The latest State of DevOps Report is rich with insight, and this article takes a closer look at the findings around reliability and incident management.
[blog] GKE Stateful High Availability (HA) Controller now in public preview. Plenty of folks are running stateful workloads on Kubernetes, but there’s a real cost to achieving legit high availability. I like this new option which gives you good resilience, without over-architecting.
##
Want to get this update sent to you every day? Subscribe to my RSS feed or subscribe via email below:
That was quite the week. How you doing? Take a breather, and check out some thought-provoking content here on team structures, architectures, and tools.
[blog] The Product Model at Spotify. This piece offers substantial insight into what motivated Spotify to organize their teams and workflow as they did.
[docs] Overview of Generative AI on Vertex AI. The diagram on this page is very informative. It’s a good way to digest the pieces that come together in a generative AI workflow.
[blog] Vertical Slice Architecture in ASP.NET Core. The .NET angle doesn’t matter here; it’s really about explaining a pattern (vertical slicing) that I prefer for any language/framework.
My team’s grown lately, and I’ve been thinking more and more about the type of manager/leader I want to be. I wrote this back in 2016 when thinking of my favorite managers. But I’ve also learned that I shouldn’t just be the type of manager I want for myself, but also personalize my behavior to each person who may want/need something different. Work in progress!
[blog] Slides from SaaStock: What Founders Need to Know About Product Marketing. Whether you’re at a ten person company, or ten thousand person company, there’s someone doing marketing. Product marketing, specifically. Check out this post for a useful description of the purpose and function of the role.
[blog] The State of WebAssembly 2023. What are people using WebAssembly for, which languages are most popular, and what are the most desired new features? These survey results shed some light.
[blog] Introducing Ruvy. Speaking of WebAssembly, this new open source project from Shopify takes your Ruby code and creates a WASM module.
[blog] Understanding Open Source Licensing. Can’t tell your MIT from your GPL? I hear you. But there are major implications that come along with which OSS license you’re dealing with.
I was in an all-day meeting today, and again found myself grateful to work with so many bright folks. Long day though, and closing it out by reading a couple more interesting items. Enjoy!
[article] Do You Manage Too Many People? I’ve definitely made mistakes in this department, and now work to have a more reasonable number of direct reports.
[article] C# Overtaking Java in Popularity Index. There are lots of factors here, including the split JVM attention due to Kotlin, as well as C# being a good language with an open ecosystem.
In between meetings today, I was reading up on how embeddings and vector databases actually work. At some point, I’ll build a demo to see it for myself. Meanwhile, I read other content today as well.
[blog] Switching Build Systems, Seamlessly. The Spotify Engineering team shared their experience upgrading the build system for their iOS client.
[article] What is -1 to 0? A Philosophy of Ideation. You might have heard the term “0 to 1” which refers to the practice of creating something new. This post looks at how you decide where to put your energy in the first place.
[blog] This Will Make You Feel More Positive: 11 Secrets From Research. I’m one of those annoyingly positive people. It doesn’t mean I don’t experience or observe hardship and pain, but I choose to not be focused on it. This post has advice for resetting your frame.
It was a beautiful SoCal weekend, and I snuck in a little time to write up a blog post about gen AI and software architects. Today’s links cover a wide range of topics, and a couple of them have useful reflections about the past.
[article] Oh No, the Software Consultants Are Coming! The dreaded outside consultant. I’ve been that person, and worked with that person. Most of the time it’s great. Sometimes not. But don’t fear the consultants.
[blog] How to Measure Developer Experience. Whether you’re serving internal devs or external ones, a good developer experience matters. Adam gives you 13 things to look for, and offers advice on how to get supporting data.
[article] Developer Onboarding and Ramp-Up Time. Good summary of some recent research at Google. Learn more about what gets in the way of successful onboarding.
[blog] How AI and imagery keep speed limits on Google Maps updated. Admittedly, I’m easily impressed. But still, I think it’s pretty cool when I’m driving and my nav system knows the speed limit of the road I’m on. Here’s insight into how that works.
Much has been written—some by me—about how generative AI and large language models help developers. While that’s true, there are plenty of tech roles that stand to get a boost from AI assistance. I sometimes describe myself as a “recovering architect” when referring back to my six years in enterprise IT as a solutions/functional architect. It’s not easy being an architect. You lead with influence not authority, you’re often part of small architecture teams and working solo on projects, and tech teams can be skeptical of the value you add. When I look at what’s possible with generative AI today, I think about how I would have used it to be better at the architecture function. As an architect, I’d have used it in the following ways:
Help stay up-to-date on technology trends
It’s not hard for architects to get stale on their technical knowledge. Plenty of other responsibilities take architects away from hands-on learning. I once worked with a smart architect who was years removed from coding. He was flabbergasted that our project team was doing client-side JavaScript and was certain that server-side logic was the only way to go. He missed the JavaScript revolution and as a result, the team was skeptical of his future recommendations.
If you have an Internet-connected generative AI experience, you can start with that to explore modern trends in tech. I say “internet-connected” because if you’re using a model trained and frozen at a point in time, it won’t “know” about anything that happened after it’s training period.
For example, I might ask a service like Google Bard for help understanding the current landscape for server-side JavaScript.
I could imagine regularly using generative AI to do research, or engaging in back-and-forth discussion to upgrade my dated knowledge about a topic.
Assess weaknesses in my architectures
Architects are famous (infamous?) for their focus on the non-functional requirements of a system. You know, the “-ilities” like scalability, usability, reliability, extensibility, operability, and dozens of others.
While no substitute for your own experience and knowledge, an LLM can offer a perspective on the quality attributes of your architecture.
For example, I could take one of the architectures from the Google Cloud Jump Start Solutions. These are high-quality reference apps that you deploy to Google Cloud with a single click. Let’s look at the 3-tier web app, for example.
It’s a very solid architecture. I can take this diagram, send it to Google Bard, and ask how it measures up against core quality attributes I care about.
What came back from Bard were sections for each quality attribute, and a handful of recommendations. With better prompting, I could get even more useful data back! Whether you’re a new architect or an experienced one, I’d bet that this offers some fresh perspectives that would validate or challenge your own assumptions.
Validate architectures against corporate specifications
Through fine-tuning, retrieval augmented generation, or simply good prompting, you can give LLMs context about your specific environment. As an architect, I’d want to factor in my architecture standards into any evaluation.
In this example, I give Bard some more context about corporate standards when assessing the above architecture diagram.
In my experience, architecture is local. Each company has different standards, choices of foundational technologies, and strategic goals. Asking LLMs for generic architecture advice is helpful, but not sufficient. Feeding your context into a model is critical.
Build prototypes to hand over to engineers
Good architects regularly escape their ivory tower and stay close to the builders. And ideally, you’re bringing new ideas, and maybe even working code, to the teams you support.
Services like Bard help me create frontend web pages without any work on my part. And I can quickly prototype with cloud services or open source software thanks to AI-assisted coding tools. Instead of handing over whiteboard sketches or UML diagrams, we can hand over rudimentary working apps.
Help me write sections of my architecture or design specs
Don’t outsource any of the serious thinking that goes into your design docs or architecture specs. But that doesn’t mean you can’t get help on boilerplate content. What if I have various sections for “background info” in my docs, and want to include tech assessments?
I used the new “help me write” feature in Google Docs to summarize the current state of Java and call out popular web frameworks. This might be good for bolstering an architecture decision to choose a particular framework.
Quickly generating templates or content blocks may prove a very useful job for generative AI.
Bootstrap new architectural standards
In addition to helping you write design docs, generative AI may help you lay a foundation for new architecture standards. Plenty of architects write SOPs or usage standards, and I would have used LLMs to make my life easier.
Here, I once again asked the “help me write” capability in Google Docs to give me the baseline of a new spec for database selection in the enterprise. I get back a useful foundation to build upon.
Summarize docs or notes to pull out key decisions
Architects can tend to be … verbose. That’s ok. The new Duet AI in Workspace does a good job summarizing long docs or extracting insights. I would have loved to use this on the 30-50 page architecture specs or design docs I used to work with! Readers could have quickly gotten the gist of the doc, or found the handful of decisions that mattered most. Architects will get plenty of value from this.
A good architect is worth their weight in gold right now. Software systems have never been more powerful, complicated, and important. Good architecture can accelerate a company or sink it. But the role of the architect is evolving, and generative AI can give architects new ways. to create, assess, and communicate. Start experimenting now!
I’ve got lots of good items for you to check out below, whether you’re looking for strategic pieces or lower level tech details. Dig in!
[blog] Top 100 product marketing books: Your definitive guide. Don’t let the title fool you. This is a list of books that many types of people would benefit from. If you want to improve how you think strategically and communicate with others, pick a few from this list.
[youtube-video] AlloyDB Omni on Google Compute Engine Quickstart. This is everything I want out of a video demonstration of tech: it’s short, it’s visual, and it includes commentary about WHY the presenter is making certain choices.