@chaos_monster I only want to confirm that ๐ it's a trade off and finding the right balance is the work of a team. First line of thinking for me: first try to write code which is self explaining by naming, structuring, splitting, ... Then document what's necessary for a fellow to understand
@chaos_monster I am talking about documentation bload, a 4 line function body, which doesn't have magic, doesn't need to be documented, only because you have configured your IDE in a way, that it automatically put a 10 line docstring above.
@JustAnotherPM@TechPdM Make it quick and easy/dirty, but expecting the code to be scalable, extendable, and easy to change. All 3 things need work and thinking about e.g. abstractions, architecture, deployments and testing)... The classical MVP trap. #unvisible work to be done
@JustAnotherPM Clarity about goals, the why behind. No over specificity. Edge cases were thought about upfront. Explicit is better than implicit. Side effects has been addressed (to other businesses processes e.g. like BI)
@nurijanian For the basics systems design is explained very well by @bytebytego . Topics for PMs: understand authentication, identity, authorization, caching, communication protocols, different kind of APIs, different databases, CI/CD ... My 2 cents
A hack I discovered recently as a PM: learning more about software architecture
In a way, good PMs have to possess a lot of similar skills as architects:
- influence without authority
- systems thinking
- seeing horizontally across the org
Here's a place to start๐๐ฝ
Hinweis fรผrs Treffen des #AIProductCircle heute Nachmittag: aufgrund von Krankheit mรผssen wir das Meetup leider verschieben. Am Donnerstag, 04. April werden wir euch nun zeigen, wie wir die ideale Customer Journey mit #GenAI bauen. RSVP! ai-circle.gs-9.com/meetup-26-marzโฆ
@garrytan The world consists of two kind of people: the ones who want to create a future by accepting failures, and those who make fun of them, now on social Media with their smartphones filled with electricity ๐คท๐ฝโโ๏ธ
The car was invented in 1886 but horses werenโt replaced as a means for transportation until 1920โs for early adopter regions and 1950โs everywhere.
Transformative technology doesnโt appear everywhere immediately. The future is not evenly distributed and not easily distributed.