uhhh tbh using a vertical roomba for that would've been a better option

we could come up with something like that

Nice table lamp there instead of a Mirror.

Mizos and kukis tend to have sharper features than Nagas based on my experiences.

No one talks about his match awareness and future vision 😂😂😂 he can do anything to make his century pr ek baat h jb pndya aaya tha tb geend to hmari bhi pht rhi thi 100 nhi krne dega kholi ko

Top middle girl>>


Holy fuck WHY IS THIS SUB OBSESSED WITH URU, it's always hyderabad better, bengaluru bad and always comparing the cities like nobody gives a shit about hyderbad here

https://maps.app.goo.gl/pZSpFvzkfoyW6x6P9

So why do they entertain Rohingyas and other illegals?

Meiteis with least south Asian ancestry??? Wut

This is a good question and I’m curious what others say. 

A wiki is a start but what I’ve found is they tend to get disorganized over time and people stop using them and it’s hard to find relevant information. 

I believe the key ideas are to make documentation part of everyone’s workflow while keeping relevant documentation close to the problem. I.e. if it’s documentation about how to use a code repository then put it in the code repository README.md. If it’s how to use the product then put it in the product itself via information icons or other “walkthroughs”. Unit tests/integration tests can be documentation. Official training videos as an “internal product”. I think the key is to treat documentation as a product itself and if the documentation gets outdated people will complain because of a  “we broke production” mindset. The processes that are established have to make it hurt to not do documentation correctly. 

### **For Engineering:**  
- READMEs work, but only if they stay updated. Automate key information into dashboards so people see it without searching.  
- Unit and integration tests function as living documentation, but only if they fail when something breaks. Otherwise, they become outdated.  
- PR templates should include a “Docs Updated?” checkbox to ensure every change is documented.  
- Internal APIs should be **self-documenting** using tools like Swagger or OpenAPI. No one should have to ask how something works.  

### **For Sales & Customer Support:**  
- CRM tools like Salesforce or HubSpot need product knowledge **embedded** in deal records. Salespeople won’t check a wiki during a call.  
- Sales scripts and objection handling should be **version-controlled** like code. If someone uses outdated info, that’s their responsibility.  
- Support should maintain a **living playbook** within their ticketing system. Every resolved issue should update or validate existing documentation.  
- Call recordings should be tagged with common issues and linked to relevant documentation. If a support rep answers the same question twice, the third time should be a link.  

### **For Operations & Strategy:**  
- SOPs should integrate with workflow automation. If a process requires a manual step, that step should include a direct link to the procedure. No searching.  
- Internal dashboards should display key policies where they matter. Expense reports should link to reimbursement policies **at submission**, not buried in a wiki.  
- Leadership decisions should be documented in **decision logs** to track policy changes and strategic moves. No rewriting history.  


Documentation shouldn’t be something people have to “go find” later, it should appear exactly where they need it. The real problem isn’t just missing documentation, it’s that people ignore what exists.

Saare ogs hai

chakki wali motor,, boght in 1978

Yes. Will be less. But let’s not tell public it will be less. Then, everyone will be on road. Let’s keep it secret😉

u/Adventurous_Print463 Just today I visited showroom to have a look at the Duke 390, the bike is indeed excellent but I found the handlebar vibrations a huge turn-off, I am wondering if all Duke 390s are like that or it’s just my test vehicle which had that issue??

Upper middle class and above, or great future prospects, or both, foreign prospects/ education, no debts and loans, some people prefer good family background (educated and reputed status), great career, averagely healthy, average or above looks, funny, street smarts, mature, financially capable and responsible, no petulance, no to very little in laws, cooking skills (even upper class expect this nowadays), 1 lpa+ (should be matching or above the bride's salary), no regressive and possessive mindset, no std and genetic diseases. That's it. This is the bride's side expectations.

Groom side : loyal and average+ beauty, compassion, understanding, little to no past relationship baggage (not relationships, but relationship baggage), some prefer the similar salary and career field (people in metro and tier 1 prefer that), some people prefer similar social standing and education, no to little manipulative, non abusive and educated in laws.

aunty clapped at last due to peer pressure while getting angry lmao

https://preview.redd.it/axvqyghjy9le1.jpeg?width=1064&format=pjpg&auto=webp&s=a2d5d5434db3593d227fb82e4bcdb3217c32a016

Here. Couldn't add the image when creating the post.

Now that even based models come with some decent safety features it makes good sense to go with these setup.

Where is the beating? Scumbag troll title.

Chigma