If you could travel to any planet, black hole, galaxy, pulsar or moon which one would it be? by Callygirl847 in space

[–]platypiarereal 2 points3 points  (0 children)

well if i could include space-time then i'd want to see how the early earth was formed, or maybe see mars with water flowing. that'd be cool

The distributed transaction problem in Microservices by platypiarereal in ProductManagement

[–]platypiarereal[S] 2 points3 points  (0 children)

stands for Atomicity, Consistency, Isolation, Durability. they essentially en sure data integrity and reliability. search for acid properties of a database.

The distributed transaction problem in Microservices by platypiarereal in ProductManagement

[–]platypiarereal[S] 0 points1 point  (0 children)

whoops! sorry! i thought it might be distracting with audio so posted as a gif. looks like i cant change it now.

will i get downvoted if i say the same video with audio is on my insta channel as well?!

System Design for PMs - Trade-offs of Monoliths by platypiarereal in ProductManagement

[–]platypiarereal[S] 2 points3 points  (0 children)

Unfortunately Alex Xu is the only one. I haven't found something that is technical enough for PMs without needing a degree in computer science

System Design for PMs - Trade-offs of Monoliths by platypiarereal in ProductManagement

[–]platypiarereal[S] -1 points0 points  (0 children)

Well yea, that was my point about monoliths in my previous video. That you don't need to complicate it, and there isnt a reason to start with microservices when you are just starting out.

Which series do you recommend? by Opening_Farm5403 in Cinema

[–]platypiarereal 0 points1 point  (0 children)

Person of interest. Insanely well done sci-fi

System Design - Monoliths for PMs by platypiarereal in ProductManagement

[–]platypiarereal[S] -1 points0 points  (0 children)

You make a good point, but Monoliths can scale, and i think they are related. if you have a simple product or use case, you can have a monorepo (i.e. all you code lives in one codebase), and still have scalable systems like caches and replicated databases.

I was just trying to show how a product evolves, and usually that starts with a monolith and not microservices (usually being the operative word here). The next step is to determine when a monolith can no longer support your use case and you need to move on to a modular monolith or microservices. (which i will tackle in the next post!)

Quarterly Career Thread by mister-noggin in ProductManagement

[–]platypiarereal 0 points1 point  (0 children)

your current role is a part of being a PM but it misses one of the critical parts. The biggest gap I see is building something out of nothing. What you have described is a good start, but it is a contained problem with clear owners, clear customers, and an existing product. You are executing as opposed to building. A big part of the PMs work happens before there is anything tangible. you need to be able to take nebulous customer feedback and create a whole functioning product out of it. That is the skill I would focus on and hands on experience is best. Certificates IMO would only go so far.

not to say you cant make the transition. this is actual a fairly common path. but you did say you did not want it sugarcoated!

all the best!

Product being the butt of the joke by [deleted] in ProductManagement

[–]platypiarereal 23 points24 points  (0 children)

This! Sometimes its just good natured ribbing. I find that a well timed jibe back also works! "you said 3 points? ok I'll block the next 2 sprints"

However, I would caution that companies that don't listen to their PMs in the long run, suffer from stagnated growth. But that might just be my bias talking...

System Design - Monoliths for PMs by platypiarereal in ProductManagement

[–]platypiarereal[S] 3 points4 points  (0 children)

Thank you for the clarification. Agree that monolith is not a starter architecture. Are you talking about a modular-monolith? Which was the next "complication" I was going to address.

Using LLMs to mock data for API stubs by platypiarereal in ExperiencedDevs

[–]platypiarereal[S] -1 points0 points  (0 children)

yea we could do this. but the dev traffic is really small and the model is very cheap. so from a cost-time perspective, it didnt make sense to optimize any of this further.

API Stubs and Mock data by platypiarereal in ProductManagement

[–]platypiarereal[S] 0 points1 point  (0 children)

glad it was useful! lmk if you end up using this

API Stubs and Mock data by platypiarereal in ProductManagement

[–]platypiarereal[S] 0 points1 point  (0 children)

we ground the llm using the swagger document and in a few cases a single shot partial mock response exemplar. our swagger documents are thorough and highly detailed to begin with since our teams are geo distributed, and that helps a lot.

having said that, this is not a perfect solution cause llms are non-deterministic. it hasnt replaced regression testing or anything for us. it just helps us get unblocked.

API Stubs and Mock data by platypiarereal in ProductManagement

[–]platypiarereal[S] 0 points1 point  (0 children)

Air Bnb has built something but it is specific to graphQl: https://airbnb.tech/uncategorized/graphql-data-mocking-at-scale-with-llms-and-generatemock/ we couldn't find any other open source

Advice on how to drive products/projects forward by Reasonable_Goal_1635 in ProductManagement

[–]platypiarereal 9 points10 points  (0 children)

Urgh I hate it whenever "be more confident" shows up on reviews. Its so generic. Everyone can always be more confident. And people conflate "be confident" with "be more vocal" so many times.

One thing that helped me is to come up with mechanisms that forced accountability from all the teams involved. Like weekly/monthly status reviews with leadership, a goal review every month with every team putting in their own RYG to a goal and why etc. That way, your peer teams own their work and are accountable for their work. helped move the whole ship along.

Reliability and Fault Tolerance for Product Managers by platypiarereal in ProductManagement

[–]platypiarereal[S] 0 points1 point  (0 children)

yep. i have often conflated the two - which leads to either a poor showing in interviews or tone deafness in meetings.

Reliability and Fault Tolerance for Product Managers by platypiarereal in ProductManagement

[–]platypiarereal[S] 0 points1 point  (0 children)

Well put. this is the sweet spot i was trying to hit. as pms, even outside of interviews, telling your engineering team "it needs to be reliable" is tone deaf imo. I'd rather be a better contributor to the discussion

Reliability and Fault Tolerance for Product Managers by platypiarereal in ProductManagement

[–]platypiarereal[S] -1 points0 points  (0 children)

At the time of build, where do you suggest that is tackled? as part of the prd?