💥 Marco Stipek

6.7K posts

💥 Marco Stipek banner
💥 Marco Stipek

💥 Marco Stipek

@codeprophet

Full Stack #CEO, #Founder @JSKongress 🦏 , @geekspace9 🤓 #productengineering, #scaling , #ai in product development

München Bergabung Mayıs 2013
0 Mengikuti1K Pengikut
Denny Klisch
Denny Klisch@KiwiDenny·
What is Product-Market-Fit? WRONG answers only!
English
20
1
9
4.4K
💥 Marco Stipek me-retweet
Turing 42
Turing 42@turing_42·
Do it like our colleague Cornelia: Be like Pippi when it comes to #GenAI 🙃 🤸
Turing 42 tweet media
English
0
0
1
213
Denny Klisch
Denny Klisch@KiwiDenny·
Unpopular opinion: 95% of the roadmaps are not worth the paper they are written on.
English
16
2
46
5.2K
💥 Marco Stipek
💥 Marco Stipek@codeprophet·
@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
English
0
0
0
32
💥 Marco Stipek
💥 Marco Stipek@codeprophet·
@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.
English
0
0
0
18
💥 Marco Stipek
💥 Marco Stipek@codeprophet·
@Maggysche Vielleicht bietest du ihm das nächste Mal einfach eine Ausbildung zum erfolgreichen Rekruiter an 🤔
Deutsch
0
0
1
35
💥 Marco Stipek
💥 Marco Stipek@codeprophet·
@JustAnotherPM Product management != Project management != Requirements engineering and leadership != Management
English
0
0
1
119
JustAnotherPM | Sid
JustAnotherPM | Sid@JustAnotherPM·
Product managers, what did you have to learn the hard way?
English
14
3
9
5.2K
💥 Marco Stipek
💥 Marco Stipek@codeprophet·
@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
English
0
0
1
47
JustAnotherPM | Sid
JustAnotherPM | Sid@JustAnotherPM·
Software engineers -- what do you think differentiates a GOOD vs BAD product requirement?
English
7
2
12
8K
💥 Marco Stipek
💥 Marco Stipek@codeprophet·
@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)
English
0
0
2
203
💥 Marco Stipek
💥 Marco Stipek@codeprophet·
@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
English
1
1
3
182
George from 🕹prodmgmt.world
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👇🏽
English
4
3
19
3.7K
💥 Marco Stipek me-retweet
Turing 42
Turing 42@turing_42·
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…
Turing 42 tweet media
Deutsch
0
1
0
106
💥 Marco Stipek me-retweet
Pau Labarta Bajo
Pau Labarta Bajo@paulabartabajo_·
Machine Learning models do not predict the future. They just find patterns in the past.
English
18
110
726
38.5K
💥 Marco Stipek
💥 Marco Stipek@codeprophet·
@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 🤷🏽‍♀️
English
0
0
0
16
Garry Tan
Garry Tan@garrytan·
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.
English
90
245
1.8K
312.8K
💥 Marco Stipek
💥 Marco Stipek@codeprophet·
@_Chorge 😂 ok. Verstehe, im Alter ändert sich die Temperatur Wahrnehmung 🤷🏽‍♀️
Deutsch
0
0
0
13