☀️ JOIN SPN MOBILE
Forums
New posts
Guru Granth Sahib
Composition, Arrangement & Layout
ਜਪੁ | Jup
ਸੋ ਦਰੁ | So Dar
ਸੋਹਿਲਾ | Sohilaa
ਰਾਗੁ ਸਿਰੀਰਾਗੁ | Raag Siree-Raag
Gurbani (14-53)
Ashtpadiyan (53-71)
Gurbani (71-74)
Pahre (74-78)
Chhant (78-81)
Vanjara (81-82)
Vaar Siri Raag (83-91)
Bhagat Bani (91-93)
ਰਾਗੁ ਮਾਝ | Raag Maajh
Gurbani (94-109)
Ashtpadi (109)
Ashtpadiyan (110-129)
Ashtpadi (129-130)
Ashtpadiyan (130-133)
Bara Maha (133-136)
Din Raen (136-137)
Vaar Maajh Ki (137-150)
ਰਾਗੁ ਗਉੜੀ | Raag Gauree
Gurbani (151-185)
Quartets/Couplets (185-220)
Ashtpadiyan (220-234)
Karhalei (234-235)
Ashtpadiyan (235-242)
Chhant (242-249)
Baavan Akhari (250-262)
Sukhmani (262-296)
Thittee (296-300)
Gauree kii Vaar (300-323)
Gurbani (323-330)
Ashtpadiyan (330-340)
Baavan Akhari (340-343)
Thintteen (343-344)
Vaar Kabir (344-345)
Bhagat Bani (345-346)
ਰਾਗੁ ਆਸਾ | Raag Aasaa
Gurbani (347-348)
Chaupaday (348-364)
Panchpadde (364-365)
Kaafee (365-409)
Aasaavaree (409-411)
Ashtpadiyan (411-432)
Patee (432-435)
Chhant (435-462)
Vaar Aasaa (462-475)
Bhagat Bani (475-488)
ਰਾਗੁ ਗੂਜਰੀ | Raag Goojaree
Gurbani (489-503)
Ashtpadiyan (503-508)
Vaar Gujari (508-517)
Vaar Gujari (517-526)
ਰਾਗੁ ਦੇਵਗੰਧਾਰੀ | Raag Dayv-Gandhaaree
Gurbani (527-536)
ਰਾਗੁ ਬਿਹਾਗੜਾ | Raag Bihaagraa
Gurbani (537-556)
Chhant (538-548)
Vaar Bihaagraa (548-556)
ਰਾਗੁ ਵਡਹੰਸ | Raag Wadhans
Gurbani (557-564)
Ashtpadiyan (564-565)
Chhant (565-575)
Ghoriaan (575-578)
Alaahaniiaa (578-582)
Vaar Wadhans (582-594)
ਰਾਗੁ ਸੋਰਠਿ | Raag Sorath
Gurbani (595-634)
Asatpadhiya (634-642)
Vaar Sorath (642-659)
ਰਾਗੁ ਧਨਾਸਰੀ | Raag Dhanasaree
Gurbani (660-685)
Astpadhiya (685-687)
Chhant (687-691)
Bhagat Bani (691-695)
ਰਾਗੁ ਜੈਤਸਰੀ | Raag Jaitsree
Gurbani (696-703)
Chhant (703-705)
Vaar Jaitsaree (705-710)
Bhagat Bani (710)
ਰਾਗੁ ਟੋਡੀ | Raag Todee
ਰਾਗੁ ਬੈਰਾੜੀ | Raag Bairaaree
ਰਾਗੁ ਤਿਲੰਗ | Raag Tilang
Gurbani (721-727)
Bhagat Bani (727)
ਰਾਗੁ ਸੂਹੀ | Raag Suhi
Gurbani (728-750)
Ashtpadiyan (750-761)
Kaafee (761-762)
Suchajee (762)
Gunvantee (763)
Chhant (763-785)
Vaar Soohee (785-792)
Bhagat Bani (792-794)
ਰਾਗੁ ਬਿਲਾਵਲੁ | Raag Bilaaval
Gurbani (795-831)
Ashtpadiyan (831-838)
Thitteen (838-840)
Vaar Sat (841-843)
Chhant (843-848)
Vaar Bilaaval (849-855)
Bhagat Bani (855-858)
ਰਾਗੁ ਗੋਂਡ | Raag Gond
Gurbani (859-869)
Ashtpadiyan (869)
Bhagat Bani (870-875)
ਰਾਗੁ ਰਾਮਕਲੀ | Raag Ramkalee
Ashtpadiyan (902-916)
Gurbani (876-902)
Anand (917-922)
Sadd (923-924)
Chhant (924-929)
Dakhnee (929-938)
Sidh Gosat (938-946)
Vaar Ramkalee (947-968)
ਰਾਗੁ ਨਟ ਨਾਰਾਇਨ | Raag Nat Narayan
Gurbani (975-980)
Ashtpadiyan (980-983)
ਰਾਗੁ ਮਾਲੀ ਗਉੜਾ | Raag Maalee Gauraa
Gurbani (984-988)
Bhagat Bani (988)
ਰਾਗੁ ਮਾਰੂ | Raag Maaroo
Gurbani (889-1008)
Ashtpadiyan (1008-1014)
Kaafee (1014-1016)
Ashtpadiyan (1016-1019)
Anjulian (1019-1020)
Solhe (1020-1033)
Dakhni (1033-1043)
ਰਾਗੁ ਤੁਖਾਰੀ | Raag Tukhaari
Bara Maha (1107-1110)
Chhant (1110-1117)
ਰਾਗੁ ਕੇਦਾਰਾ | Raag Kedara
Gurbani (1118-1123)
Bhagat Bani (1123-1124)
ਰਾਗੁ ਭੈਰਉ | Raag Bhairo
Gurbani (1125-1152)
Partaal (1153)
Ashtpadiyan (1153-1167)
ਰਾਗੁ ਬਸੰਤੁ | Raag Basant
Gurbani (1168-1187)
Ashtpadiyan (1187-1193)
Vaar Basant (1193-1196)
ਰਾਗੁ ਸਾਰਗ | Raag Saarag
Gurbani (1197-1200)
Partaal (1200-1231)
Ashtpadiyan (1232-1236)
Chhant (1236-1237)
Vaar Saarang (1237-1253)
ਰਾਗੁ ਮਲਾਰ | Raag Malaar
Gurbani (1254-1293)
Partaal (1265-1273)
Ashtpadiyan (1273-1278)
Chhant (1278)
Vaar Malaar (1278-91)
Bhagat Bani (1292-93)
ਰਾਗੁ ਕਾਨੜਾ | Raag Kaanraa
Gurbani (1294-96)
Partaal (1296-1318)
Ashtpadiyan (1308-1312)
Chhant (1312)
Vaar Kaanraa
Bhagat Bani (1318)
ਰਾਗੁ ਕਲਿਆਨ | Raag Kalyaan
Gurbani (1319-23)
Ashtpadiyan (1323-26)
ਰਾਗੁ ਪ੍ਰਭਾਤੀ | Raag Prabhaatee
Gurbani (1327-1341)
Ashtpadiyan (1342-51)
ਰਾਗੁ ਜੈਜਾਵੰਤੀ | Raag Jaijaiwanti
Gurbani (1352-53)
Salok | Gatha | Phunahe | Chaubole | Swayiye
Sehskritee Mahala 1
Sehskritee Mahala 5
Gaathaa Mahala 5
Phunhay Mahala 5
Chaubolae Mahala 5
Shaloks Bhagat Kabir
Shaloks Sheikh Farid
Swaiyyae Mahala 5
Swaiyyae in Praise of Gurus
Shaloks in Addition To Vaars
Shalok Ninth Mehl
Mundavanee Mehl 5
ਰਾਗ ਮਾਲਾ, Raag Maalaa
What's new
New posts
New media
New media comments
New resources
Latest activity
Videos
New media
New comments
Library
Latest reviews
Donate
Log in
Register
What's new
New posts
Menu
Log in
Register
Install the app
Install
Welcome to all New Sikh Philosophy Network Forums!
Explore Sikh Sikhi Sikhism...
Sign up
Log in
Discussions
Hard Talk
Interviews
Spread The Word: Math Is The New Sexiness In IT
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="rajneesh madhok" data-source="post: 158163" data-attributes="member: 10692"><p>Spread the word: Math is the new sexiness in IT</p><p>By Derrick Harris Dec. 16, 2011, 3:00pm PT 5 Comments</p><p> </p><p> </p><p>“If you go to an eighth grader and ask them how many want to be applied mathematicians, not many hands will go up.”</p><p></p><p>So says Dhiraj Rajaram, founder and CEO of Mu Sigma, a Chicago-based startup providing analytics (or “decision sciences” as the company calls it) as a service to a large pool of Fortune 500 customers. He’s probably right, and that’s a problem.</p><p></p><p>We need math to improve sales … and manage servers</p><p></p><p>Organizations, even large ones, might be masters of the fields in which they do business, but they’re not masters of applied mathematics, which is at the core of the growing data science trend. When it comes time to undertake a big data strategy that requires turning advanced algorithms on potentially massive data sets, many fast realize they don’t have, or have nearly enough of, the necessary skills internally. Attempts to hire these skills might prove largely fruitless as the small population of employees with the predicate acumen in both business and calculus are quickly snatched up by an equally small number of companies.</p><p></p><p>Analyzing traditional business data held in a data warehouse is one thing, but doing big data and, more specifically, data science is quite another. McKinsey & Co. predicts that by 2018, the United States will have a shortage of “1.5 million managers and analysts with the know-how to use the analysis of big data to make effective decisions,” and a shortage of almost 200,000 people with the deep analytical skils necessary for data science.</p><p></p><p>But enough about big business data. In an era of webscale computing and large clusters running big-data workloads, we’ll also need more people who can apply mathematics to data with the goal of automating and troubleshooting distributed systems. Sure, predictive analytics can be great for determining how consumers are likely to react to changes to their favorite products, but they also can be very helpful in helping ensure that complex systems such as Google’s run smoothly.</p><p></p><p>Case in point: Software bugs at Google</p><p></p><p>On Wednesday, two members of the Google engineering team wrote a blog post explaining their surprisingly simple new algorithm for detecting particularly troublesome code. The problem, as authors Chris Lewis and Rong Ou present it, is that with such a large, growing and increasingly complex code base — and thousands of developers working on it — it becomes nearly impossible for code reviewers to identify “hot spots.”</p><p></p><p>The authors define hot spots as code that “creates issues again and again, as developers try to wrestle with the problem,” as opposed to just a piece of necessarily difficult code to carry out a complex function. If it’s the former, reviewers need to be alerted to its status up front so they know to give it their utmost attention, or perhaps even hand it off to some with more experience.</p><p></p><p>Based on some research on how to best predict if there are bugs within particular code, the team decided on a simple method for flagging files: “files are flagged if they have attracted a large number of bug-fixing commits, no more and no less.” How the algorithm goes about filtering commits down to only the valid bug fixes is a little more complex, of course. After discussing the results of early experiments with developers, the authors’ team also decided to work in a time variable so that newer bug-fixing commits score higher than old ones that might have already been dealt with.</p><p></p><p>Their algorithm looks like this:</p><p></p><p>As explained by the authors, “n is the number of bug-fixing commits, and ti is the timestamp of the bug-fixing commit represented by i.”</p><p></p><p>Here’s what it looks like plotted:</p><p></p><p></p><p></p><p>It’s relatively simple, but it’s not as if one can always just choose the simplest-possible algorithm and run with it. As author Chris Lewis noted in the Hacker News thread on his and Ou’s post, this algorithm came to be only after much experimentation with far more-complex algorithms to solve the same problem. He had “spent a lot of time trying to implement FixCache, a pretty complicated algorithm that looks at things such as spacial locality of bugs (bugs appear close to each other), temporal locality of bugs (bugs are introduced at the same time) and files that change together (bugs will cross cut these)” before coming across the research that led to the ultimate strategy.</p><p></p><p>In another comment, Lewis suggested the future might involve some much more-difficult concepts, such as machine learning. “[W]e don’t have good tools (yet) to have a computer properly check the semantic meaning of our code,” he wrote. “Bug prediction sits as a sort of baby step. It’s the computer making a best-effort guess of where issues will be.“</p><p></p><p>We’re just getting started</p><p></p><p>Companies such as Google and Facebook are doing alright in solving some of their problems, but what they’re doing now is just the tip of the iceberg. As Lewis indicated, there’s real value in evolving their current efforts further, to the point where machine learning and other techniques will let computers do everything from review code to, perhaps, predict problems with overall system health. And as the next generation of web companies start scaling up, they’ll start running into their own unique systems issues that they’ll have to solve.</p><p></p><p>Data science as it relates to business decisions is an obviously valuable area, and all the talk about big data probably ensures a fair investment in learning those skills. For organizations without internal skills, they can always outsource data science to companies such as Mu Sigma and Opera Solutions that exist to provide just such services. New, higher-level software products from startups such as Odiago, Platfora and others promise to alleviate some business-oriented analytic pain, as well.</p><p></p><p>But applying data science to data about software code or webscale system activity doesn’t always have a direct connection to income, which means it doesn’t get talked about as much. Those skills, however, are arguably as important to our growing Internet economy as big business data is to companies of all types. Hopefully, the message gets out and teenagers start to realize that if they want high-paying jobs with the coolest companies around, they’d better get a lot more interested in math.</p><p></p><p>If big data does indeed write the book about the future of business, Mu Sigma’s Rajaram says the climax will be “that mathematicians take the prom queen home.”</p><p><a href="http://gigaom.com/cloud/spread-the-word-math-is-the-new-sexiness-in-it/" target="_blank">http://gigaom.com/cloud/spread-the-word-math-is-the-new-sexiness-in-it/</a></p><p></p><p>Rajneesh Madhok</p></blockquote><p></p>
[QUOTE="rajneesh madhok, post: 158163, member: 10692"] Spread the word: Math is the new sexiness in IT By Derrick Harris Dec. 16, 2011, 3:00pm PT 5 Comments “If you go to an eighth grader and ask them how many want to be applied mathematicians, not many hands will go up.” So says Dhiraj Rajaram, founder and CEO of Mu Sigma, a Chicago-based startup providing analytics (or “decision sciences” as the company calls it) as a service to a large pool of Fortune 500 customers. He’s probably right, and that’s a problem. We need math to improve sales … and manage servers Organizations, even large ones, might be masters of the fields in which they do business, but they’re not masters of applied mathematics, which is at the core of the growing data science trend. When it comes time to undertake a big data strategy that requires turning advanced algorithms on potentially massive data sets, many fast realize they don’t have, or have nearly enough of, the necessary skills internally. Attempts to hire these skills might prove largely fruitless as the small population of employees with the predicate acumen in both business and calculus are quickly snatched up by an equally small number of companies. Analyzing traditional business data held in a data warehouse is one thing, but doing big data and, more specifically, data science is quite another. McKinsey & Co. predicts that by 2018, the United States will have a shortage of “1.5 million managers and analysts with the know-how to use the analysis of big data to make effective decisions,” and a shortage of almost 200,000 people with the deep analytical skils necessary for data science. But enough about big business data. In an era of webscale computing and large clusters running big-data workloads, we’ll also need more people who can apply mathematics to data with the goal of automating and troubleshooting distributed systems. Sure, predictive analytics can be great for determining how consumers are likely to react to changes to their favorite products, but they also can be very helpful in helping ensure that complex systems such as Google’s run smoothly. Case in point: Software bugs at Google On Wednesday, two members of the Google engineering team wrote a blog post explaining their surprisingly simple new algorithm for detecting particularly troublesome code. The problem, as authors Chris Lewis and Rong Ou present it, is that with such a large, growing and increasingly complex code base — and thousands of developers working on it — it becomes nearly impossible for code reviewers to identify “hot spots.” The authors define hot spots as code that “creates issues again and again, as developers try to wrestle with the problem,” as opposed to just a piece of necessarily difficult code to carry out a complex function. If it’s the former, reviewers need to be alerted to its status up front so they know to give it their utmost attention, or perhaps even hand it off to some with more experience. Based on some research on how to best predict if there are bugs within particular code, the team decided on a simple method for flagging files: “files are flagged if they have attracted a large number of bug-fixing commits, no more and no less.” How the algorithm goes about filtering commits down to only the valid bug fixes is a little more complex, of course. After discussing the results of early experiments with developers, the authors’ team also decided to work in a time variable so that newer bug-fixing commits score higher than old ones that might have already been dealt with. Their algorithm looks like this: As explained by the authors, “n is the number of bug-fixing commits, and ti is the timestamp of the bug-fixing commit represented by i.” Here’s what it looks like plotted: It’s relatively simple, but it’s not as if one can always just choose the simplest-possible algorithm and run with it. As author Chris Lewis noted in the Hacker News thread on his and Ou’s post, this algorithm came to be only after much experimentation with far more-complex algorithms to solve the same problem. He had “spent a lot of time trying to implement FixCache, a pretty complicated algorithm that looks at things such as spacial locality of bugs (bugs appear close to each other), temporal locality of bugs (bugs are introduced at the same time) and files that change together (bugs will cross cut these)” before coming across the research that led to the ultimate strategy. In another comment, Lewis suggested the future might involve some much more-difficult concepts, such as machine learning. “[W]e don’t have good tools (yet) to have a computer properly check the semantic meaning of our code,” he wrote. “Bug prediction sits as a sort of baby step. It’s the computer making a best-effort guess of where issues will be.“ We’re just getting started Companies such as Google and Facebook are doing alright in solving some of their problems, but what they’re doing now is just the tip of the iceberg. As Lewis indicated, there’s real value in evolving their current efforts further, to the point where machine learning and other techniques will let computers do everything from review code to, perhaps, predict problems with overall system health. And as the next generation of web companies start scaling up, they’ll start running into their own unique systems issues that they’ll have to solve. Data science as it relates to business decisions is an obviously valuable area, and all the talk about big data probably ensures a fair investment in learning those skills. For organizations without internal skills, they can always outsource data science to companies such as Mu Sigma and Opera Solutions that exist to provide just such services. New, higher-level software products from startups such as Odiago, Platfora and others promise to alleviate some business-oriented analytic pain, as well. But applying data science to data about software code or webscale system activity doesn’t always have a direct connection to income, which means it doesn’t get talked about as much. Those skills, however, are arguably as important to our growing Internet economy as big business data is to companies of all types. Hopefully, the message gets out and teenagers start to realize that if they want high-paying jobs with the coolest companies around, they’d better get a lot more interested in math. If big data does indeed write the book about the future of business, Mu Sigma’s Rajaram says the climax will be “that mathematicians take the prom queen home.” [url]http://gigaom.com/cloud/spread-the-word-math-is-the-new-sexiness-in-it/[/url] Rajneesh Madhok [/QUOTE]
Insert quotes…
Verification
Post reply
Discussions
Hard Talk
Interviews
Spread The Word: Math Is The New Sexiness In IT
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.
Accept
Learn more…
Top