To Bit Or Not To Bit

Content Backend developers: Frontend developers just coloring buttons Frontend developers: Backend developers just processing JSON Backend Developers:

Content If you know, you knowle Quora Search Quo Dating and Friendship Gender Friendship Advice Friendship Dating Advice Personal Question like girl A. We are very good friends. A's best friend B likes me. Also, A likes a guy C who is my best bro and C likes another girl D who is in a relationship with another guy. What should we do? " Answer a) Follow - 143 Request 000 90 Answers Priyanka Dhaka, studied at Indian Institute of Technology, Delhi Updated Jul 28, 2014 Originally Answered: I like girl A. We are very good friends, but her best friend B likes me. Also, A likes guy C, who is my best bro. C likes another girl D, who is in a relationship with another guy. What should we do? You can apply Bipartite Matching algorithm of Graph Theory. All you have to do is: 1. Put all girls as vertices (a's) in Part A, and boys as vertices (b's) in Part B. 2. Draw an edge between vertex a to vertex b if a likes b. 3. It will be a bipartite graph (there are no edges within vertices of Part A, and same for Part B) unless your friends are not straight. 4. Then find maximum matching for this bipartite graph. (refer this link Maximum Bipartite Matching - GeeksforGeeks C) 5. You will get maximum matching as output and the matched edges will be the pairs who should be together. 6. You can apply weighted bipartite matching algorithm if you know how much they lovelike each other. In that case, assign weights according to their amount of love. and repeat step 4 and 5. Thanks for asking this question. Finally I have found a real life problem which can be solved by what Prof Panda has been teaching us for 2-3 years. P.S. I can provide you code for both weighted and unweighted maximum bipartite matching which I made for my project. 203.1K views View 13.701 upvotes : View 1 share

The evolution of programmer excuses is a beautiful thing to witness. First, you've got "algorithm" – the fancy word we throw around when we just don't feel like explaining our spaghetti code to the junior dev. Then there's "heuristic" – perfect for when you cobbled together a solution at 3 AM that somehow works but you've genuinely forgotten how. And finally, the boss level: "machine learning" – where even YOU don't know what your code is doing anymore. The model is just vibing in n-dimensional space making decisions while you nod confidently in meetings. The progression is basically: "I won't tell you" → "I can't tell you" → "Hell if I know."

Content Kotli

Content What are the 7 deadly sins of programming? John Purcell. Creator of CaveOfProgramming.com Updated Dec 2, 2017 Upvoted by Les Howie, Software professional for 40 years. and Hasib Al Muhaimin, IOl participant '13, '14, '15, ACM-ICPC World Finalist 2016 Author has 5.9k answers and 9.3m answer views 1. Using spaces instead of tabs. You should always, always use tabs, not spaces. 2. Using tabs instead of spaces. You should always, always use spaces, not tabs. 3. Not using auto-formatting. Forget all that tabsspaces rubbish, what's wrong with you - auto-format your code and then people won't have to look at vour weird ideas about brackets and spaces. 4. Using IDEs, which have features such as auto-formatting and nicely- coloured buttons. All code should be written in vi or Emacs, thus ensuring the purity of the programming experience. 5. Not using IDEs. No-one wants to pay for all the time it's going to take you to type things that you could have done at the click of a button, or scroll up and down using some ridiculous key combination invoked using LISP. 6. Failing to learn C and C. It's really important to learn the two absolute essential languages. You think Java is just as good? Fine, write me a real- time control system for racing cars in Java and I'll believe you. 7. Learning C or C when you could be using something modern like Java instead. Admit it - all your schedules involving C or C overrun by five years. And even then the software turns out to have critical flaws that Java would not even have allowed you to create. 8. Overrunning the end of an array. 356.1k views View 11.9k Upvoters View Sharers

Content (00000006900600900000060000009090909006000090900098069000, 3 COOP000000600P8000000060006060000000600000000000006000000 NOILIONO3 NONE A 200000000000000000000000000000 0000700000000000000000000000000000000 00000000000000000000000000 cocoongoosevadooooooooooooooo.000000000000000000 JOIS HIM 300000000000000000000000000000000000090000000 SOCOLO DODOOD dO CO CO DO90 0 080 600.O 6.00 0806 0 60006.000 6 0600.00000 5 5 POCOLOCO8 06 0 60 00 00 8.0.000.06.000 60 6 06.00 060 0 96.00060 6 0000000005