CTOs potentially having cofee

/cto40

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!

What technical debt is keeping you up at night?
What would you do differently if you had twice the resources?
What technical debt is keeping you up at night?
For teams with >5 devs, how do you score on the DORA metrics?
https://dora.dev/quickcheck/

This being Fc and cutting edge, my guess would be quite high.
What would you do differently if you had twice the resources?
What technical debt is keeping you up at night?
What would you do differently if you had twice the resources?
What technical debt is keeping you up at night?
What would you do differently if you had twice the resources?
What technical debt is keeping you up at night?
What would you do differently if you had twice the resources?
What technical debt is keeping you up at night?
What would you do differently if you had twice the resources?
A curious truth about software: We start simple, with hard-coded values. Then we get clever. Config files. Rules engines. DSLs. Each step more complex than the last. Until one day, over beers, someone says "We're just hard-coding again, but in a worse language." 🎯

The clock turns. The old solutions become new again. Sometimes the simplest answer is right: Write good code. Deploy fast. Skip the elaborate configuration systems. Not every problem needs infinite flexibility. True wisdom is knowing when to stay simple. 🤔

http://mikehadlow.blogspot.com/2012/05/configuration-complexity-clock.html
Communication style is the cornerstone of great any /cto
Solve the problem – don’t just build the feature.
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.
"If it's not on a list, it's not real" - @cameron today on /okbanger stream