<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>consulting on Brave New Geek</title><link>https://bravenewgeek.com/tag/consulting-2/</link><description>Recent content in consulting on Brave New Geek</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Fri, 10 Jun 2022 10:25:44 -0600</lastBuildDate><atom:link href="https://bravenewgeek.com/tag/consulting-2/index.xml" rel="self" type="application/rss+xml"/><item><title>Meeting notes lose value the moment you finish writing them—and it’s time to fix that</title><link>https://bravenewgeek.com/meeting-notes-lose-value-the-moment-you-finish-writing-them-and-its-time-to-fix-that/</link><pubDate>Fri, 10 Jun 2022 10:25:44 -0600</pubDate><guid>https://bravenewgeek.com/meeting-notes-lose-value-the-moment-you-finish-writing-them-and-its-time-to-fix-that/</guid><description>&lt;p&gt;I like to be prepared in meetings. In some ways it’s probably an innate part of my personality, but it also became more important to me as my role has changed throughout my career. In particular, the first time I became an engineering manager is when I started to become a more diligent notetaker and meeting preparer. I think this is largely because my job shifted from being output-centric to more people- and meeting-centric. I still took notes and prepared when I was a software engineer, but it was for a very different context and purpose. As an engineer, my work centered around code output. As a manager, my work instead centered around coordinating, following up, and supporting my team. If you’ve never worked as a manager before, this probably just sounds like paper-pushing, but it’s actually a lot of work—and important! The work product is just &lt;em&gt;different&lt;/em&gt; from that of an individual contributor.&lt;/p&gt;</description></item><item><title>We suck at meetings</title><link>https://bravenewgeek.com/we-suck-at-meetings/</link><pubDate>Tue, 10 Nov 2020 13:16:18 -0600</pubDate><guid>https://bravenewgeek.com/we-suck-at-meetings/</guid><description>&lt;p&gt;&lt;img loading="lazy" src="https://bravenewgeek.com/wp-content/uploads/2020/11/dilbert.gif"&gt;&lt;/p&gt;
&lt;p&gt;I’ve worked as a software engineer, manager, consultant, and business owner. All of these jobs have involved meetings. What those meetings look like has varied greatly.&lt;/p&gt;
&lt;p&gt;As an engineer, meetings typically entailed technical conversations with peers, one-on-ones with managers, and planning meetings or demos with stakeholders.&lt;/p&gt;
&lt;p&gt;As a manager, these looked more like quarterly goal-setting with engineering leadership, one-on-ones with direct reports, and decision-making discussions with the team.&lt;/p&gt;
&lt;p&gt;As a consultant, my day often consists of talking to clients to provide input and guidance, communicating with partners to develop leads and strategize on accounts, and meeting with sales prospects to land new deals.&lt;/p&gt;</description></item><item><title>Digitally Transformed: Becoming a Technology Product Company</title><link>https://bravenewgeek.com/digitally-transformed-becoming-a-technology-product-company/</link><pubDate>Wed, 05 Feb 2020 09:46:47 -0600</pubDate><guid>https://bravenewgeek.com/digitally-transformed-becoming-a-technology-product-company/</guid><description>&lt;p&gt;More and more established businesses are attempting to reinvent themselves as technology companies. At the heart of this is the &lt;a href="https://trends.google.com/trends/explore?date=all&amp;amp;geo=US&amp;amp;q=digital%20transformation"&gt;digital transformation&lt;/a&gt;, a journey many organizations are undertaking in order to better compete and serve their customers. As a result, companies are pouring tons of cash into digital transformation strategies. For some, this means broader adoption of agile or DevOps practices. For others, it’s modernizing product offerings or moving to the cloud. Regardless of the changes, many are struggling to find success transforming themselves due to low throughput, quality issues, or failing to deliver the right thing at the right time. In a few cases, digital transformation has ended in &lt;a href="https://www.theregister.co.uk/2019/04/23/hertz_accenture_lawsuit/"&gt;&lt;em&gt;outright disaster&lt;/em&gt;&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>Planting Perennials Next to Potholes</title><link>https://bravenewgeek.com/planting-perennials-next-to-potholes/</link><pubDate>Fri, 26 Apr 2019 14:35:24 -0500</pubDate><guid>https://bravenewgeek.com/planting-perennials-next-to-potholes/</guid><description>&lt;h4 id="silos-bikesheds-and-focusing-on-what-matters"&gt;&lt;strong&gt;Silos, bikesheds, and focusing on what matters&lt;/strong&gt;&lt;/h4&gt;
&lt;p&gt;If you’ve ever flown into Des Moines then you’ve had the privilege of driving on what might be the most decrepit major road in the metro area. An important artery, Fleur Drive is the &lt;em&gt;only&lt;/em&gt; way to get to and from the airport, and the pavement is marginally better than that of a dirt road. Cars weave back and forth to dodge potholes and massive cracks in the asphalt as people race to catch their flights. There always appears to be some kind of construction going on somewhere along the six mile stretch of road, and yet, it never seems to actually &lt;em&gt;improve&lt;/em&gt;. The road is also located in a major floodplain, so sometimes the city just closes it when the nearby river rises too much. It’s basically what you’d get if you agiled your way through urban planning.&lt;/p&gt;</description></item><item><title>How to Level up Dev Teams</title><link>https://bravenewgeek.com/how-to-level-up-dev-teams/</link><pubDate>Thu, 03 Jan 2019 11:21:05 -0600</pubDate><guid>https://bravenewgeek.com/how-to-level-up-dev-teams/</guid><description>&lt;p&gt;One question that clients frequently ask: how do you effectively level up development teams? How do you take a group of engineers who have never written Python and make them effective Python developers? How do you take a group who has never built distributed systems and have them build reliable, fault-tolerant microservices? What about a team who has never built anything in the cloud that is now tasked with building cloud software?&lt;/p&gt;</description></item><item><title>Multi-Cloud Is a Trap</title><link>https://bravenewgeek.com/multi-cloud-is-a-trap/</link><pubDate>Fri, 14 Sep 2018 11:16:09 -0500</pubDate><guid>https://bravenewgeek.com/multi-cloud-is-a-trap/</guid><description>&lt;p&gt;It comes up in &lt;em&gt;a lot&lt;/em&gt; of conversations with clients. We want to be cloud-agnostic. We need to avoid vendor lock-in. We want to be able to shift workloads seamlessly between cloud providers. Let me say it again: &lt;em&gt;multi-cloud is a trap&lt;/em&gt;. Outside of appeasing a few major retailers who might not be too keen on stuff running in Amazon data centers, I can think of few reasons why multi-cloud should be a priority for organizations of &lt;em&gt;any&lt;/em&gt; scale.&lt;/p&gt;</description></item><item><title>How is Software Valued?</title><link>https://bravenewgeek.com/how-is-software-valued/</link><pubDate>Sat, 08 Jun 2013 22:48:34 -0600</pubDate><guid>https://bravenewgeek.com/how-is-software-valued/</guid><description>&lt;p&gt;I was talking to a friend a few weeks ago who was putting together a business presentation for potential investors. He was developing a plan for a campground kiosk system that would rely on GIS data to allow guests to view and check in to camp sites. The plan was reasonable enough and mostly feasible. He carefully considered all the costs—licensing for a third-party GIS, kiosk hardware, line trenching—and then there was software.&lt;/p&gt;</description></item></channel></rss>