Harrison Strowd

👋 Hi, we’re Go Between, a strategically small software design and development studio that loves helping folks build great products. Check out our site to learn more about our services! gobetweenlab.com

Improving a companies culture takes an ongoing commitment of time and effort. Most often this starts with improving communication and trust in existing relationships throughout the organization. getmarginal.com offers a way to do just that. Check it out!

Even for companies that identify culture as an area for improvement, too often they either consider it to be something that is impossible or impractical to solve, or they seek out a "quick fix" solution that doesn't get to the root of the matter.

Had a great conversation with @ShereenSater yesterday about her work helping companies improve their corporate culture. This topic is neglected far too often, even though its impact can be widespread across the business (e.g. collaboration, dedication, retention, etc).

@zorn Sure thing. I'll share something directly. Thanks for the feedback. We're working updates to the website, including an introductory video covering how the product works and its key features. But as a small team, we're always having to prioritize aggressively.

@hstrowd I apologize for the delayed reply. It's hard for me to tell how this site works in practice. Is there a video showing a live book club using it? Hard to imagine how it all works cause the home page is just component-level screenshots and not the whole.

👨‍💻Yesterday’s book club covering chapter one of Testing Elixir went great. Lots of interesting conversations. This was shared as a resource regarding test flakiness. Looks interesting. blog.appsignal.com/2021/12/21/eig…

Software development projects using Ruby, JavaScript/TypeScript, or Elixir and architecture/system design projects for web applications of a variety of shapes and sizes tend to be the best fit for my experience and services. See my full portfolio at haresoft.dev

I’m looking forward to diving into a new project at the start of next year and am searching for one that will be a good fit. I’ll have 20 hours per week to devote to this. Please share the word and if you know of a project that might be a good fit, I’d love to connect. Thanks!

@trumanshuck I often feel this artificial pressure to ship things ASAP. In these cases it can be helpful to think about the cumulative time spent, not only on the initial implementation, but also maintaining and extending it. This helps balance both the needs of the present and of the future.

While this is far from an exhaustive list, I believe that a team focusing on just these three characteristics has a much better chance of achieving great results and enjoying their work in the process. Are there others you feel are more important? I'd love to hear them.

Having a shared set of clearly defined goals is another common trait of great teams in my experience. This aligned the teams definition of success and allowed us to track and celebrate incremental progress toward these objectives, further energizing the entire team.

I've been pondering on what separates good tech teams from great tech teams and the following 3 characteristics stand out in my experience. Are there specific qualities that come to mind for you or specific steps you've seen a team take to go from good to great?

Looking to build a stronger team that can collaborate more effectively and solve the big challenges facing your business? Activities with the following three characteristics are most effective at achieving this.

In summary, it's been fun to play around with @GitHubCopilot but I don't plan to continue using it after the end of my trial. I'm open to revisiting it at a later date and could foresee it improving significantly with time, but for now I find it more distracting than beneficial.

If I were newer to the language I work in or found I had to bounce between Google and my code more frequently, these suggestions would potentially save a lot of time (e.g. write out the interface for a function, review the suggested implementation, and tweak it as needed).

I've been experimenting with @GitHubCopilot for the past month. The following is a summary of my findings.