CTOs potentially having cofee

/cto34

You're a CTO or looking for one, this is the right place. Welcome! Feel free to share an intro, what you do and what you'd like to learn from the community! Web3 knowledge is not required. We're all learning!

Had a great jam session with @yurinondual.eth a few minutes ago.

Brilliant initiative!
With the changes to channels, please reach out if you want to post here.

Will sort some membership ideas out.
When guiding a team, how do you feel about constraints?

Self-imposed or external, constraints are powerful tools.

Ikea is notoriously famous for they constraints the define during the design process.

What are some constraints you found useful? Either imposed on yourself or on the team.

Here are 2 intriguing ones:

- must be completed in 1 day
- must involve collaboration with 5+ people
- must be done outdoors
Aiming for zero technical debt is as futile as getting to zero emails in your inbox or having all your laundry washed and put up.

The shit just keeps flowing. You just have to get used to it and go with the flow.
Set the Stage:

Non-judgement is important. Eliminate a defensive environment to increase accurate results and information.

How do you nurture this within your team?

1 aswer only.
Moving from GCP/AWS to Lidl was not on my 2024 bingo card.
Remember that feature from two months ago? I've built three things since then and totally forgot how it works. A quick 10-minute prep before the meeting makes all the difference. Agenda, please!
"Managers have no clue what developers need to be productive and happy"

This article disects the data in a new research published by Atlassian, which is ironic.

Listening is scarce.

https://thenewstack.io/why-do-developers-lose-1-day-a-week-to-inefficiencies/
The flow-state visualized.

How do you get into it and how do you protect it?
A good overview of how engineers at Stripe operate, in terms of tools and practices.

Is it worth cherry-picking the ones that make sense to you?

https://blog.nelhage.com/post/stripe-dev-environment/?ref=techmanagerweekly.com
"People are valuing their cars more than their computer? They don’t have any idea what a computer is, they’re just using it to play movies"

Alan Kay interviewed by Adam Fisher in Palo Alto, August 2014 – Valley of Genius podcast Season 1, Episode 5 (https://twit.tv/shows/valley-of-genius/episodes/5)
“The long-term popularity of any given tool for software development is proportional to how much labour arbitrage it enables.”

overly pragmatic or spot on?

https://www.baldurbjarnason.com/2024/react-electron-llms-labour-arbitrage/
Linear Cycles might be under-appreciated.

In my experience, they have the missing elements of Sprints from agile practices.

https://linear.app/docs/use-cycles
The $ you spend on engineers is probably the least of your concerns when it comes to thinking about ROI.

John Cutler, The Beautiful Mess
How do you deal with slow PR review times?

A while ago I drew this chart to illustrate increased levels of escalation measures to guarantee your PRs get reviewed.

Unfortunately this doesn't scale with team size.
The problem with Test-Driven Development is that you have to think about what you want the code to do before you write it. And that ruins the surprise.
Building something people want is often misunderstood.

Is it a science?
Is it a gut feeling?
Is it hindsight or foresight?
A mix?

As a software engineer I often try to engineer and analyze it.

A lot of advice is plain survivorship bias.