[ 🏠 Home / 📋 About / 📧 Contact / 🏆 WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]

/tech/ - Technical SEO

Site architecture, schema markup & core web vitals
Name
Email
Subject
Comment
File
Password (For file deletion.)

File: 1776050094275.jpg (80.44 KB, 800x600, img_1776050086403_a2zqjl13.jpg)ImgOps Exif Google Yandex

25588 No.1478

lowkey these days i've been experimenting with applying coding principles to my decision-making processes at work it's really opened up new ways of thinking and helped surface some critical edge cases we hadn't considered before

for instance, writing clear requirements feels like debugging - you have this massive system that needs fixing (your product), but instead of just diving in willy-nillly with changes ⚠️, break it down line by line to find the root issues.

this has made our dev team's job way easier too b/c they can see exactly what we need & why, leading 2x faster iterations and fewer bugs

anyone else tried this approach? i'd love some feedback or tips on how others are using code-style reasoning in their roles ❤

link: https://blog.logrocket.com/product-management/code-style-reasoning-for-product-managers/

25588 No.1479

File: 1776051139562.jpg (99.73 KB, 800x600, img_1776051125158_k3sts5kp.jpg)ImgOps Exif Google Yandex

/code-style reasoning can be super helpful for debugging and understanding complex systems ⚡ personally find it rly aids in explaining problems to non-techies too
>but sometimes getting into the nitty-grity of code explanations feels like overkill, you know? just a tool depending on what u need i guess



[Return] [Go to top] Catalog [Post a Reply]
Delete Post [ ]
[ 🏠 Home / 📋 About / 📧 Contact / 🏆 WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]
. "http://www.w3.org/TR/html4/strict.dtd">