vodQA Pune, to be held on October 13th in Pune, is an event for software testing and QA professionals.
In this edition of vodQA, the focus is on testing beyond the usual. The discussions will range from functional and cross-functional areas like Security, Usability, Scalability and Performance, to understanding testing practices within industries such as Manufacturing and Banking, among others.
The call for speakers. If you can give a talk (30 minutes), a workshop (60 minutes), or a quick lightening talk (5 minutes) in one of the above areas, you should apply. (Sorry, it appears that the call for speakers is now closed.)
For more details of vodQA, see the vodQA Pune 2012 page. (Note: although this page says that the last date for submitting a proposal has already passed, they are still accepting submissions.)
The event itself is free and open for anyone to attend. Register here. The event is on 13th October, from 9:30am to 4:30pm, at Thoughtwords, Panchshil Tech Park, Yerwada, Pune.
(NASSCOM’s EmergeOut Conclave is one of the top conferences in the country for software companies, and for the first time this year it is coming to Pune. Although PuneTech normally does not promote paid events, we make exceptions for exceptional events, and this is one of them, and also because there is a 35% discount for PuneTech readers. See below for details.)
What to expect at the EmergeOut Conference
Keynote address by Industry stalwarts and new age successful entrepreneurs – including the IT Secretary of Maharashtra, Ganesh Natarajan CEO of Zensar, Hitesh Oberoi, CEO of Naukri.com, Jaspreet Singh, CEO of Druva.com, and Mahesh Murthy, co-founder of SeedFund
Series of workshops and high powered panel discussions – including how to cross 50cr in revenues (Anand Deshpande), Whitespaces in Cloud Technologies, Mobile Technologies, How can a small company make it big (Mukul Kumar, Pubmatic, Harbinger), Big Data and Analytics, Marketing, Sales, Social Media,
Showcase – Your Story: a showcase of the top IT startups in India
The Indian IT Industry has been the poster boy success story of the new age India in the last two decades and continues to do so. The Emerge Community is one of the important pillars and back bone of any industry and more so in case of the IT Industry. These companies are more agile, hungry for success and ever ready to face challenges, of course all this comes with a handicap of size, financial constraint and competition, which makes the space more exciting for an entrepreneur.
The power of small is in being together. This one day conference will facilitate one on one interaction, share best practices, help you explore new opportunities and learn from others failures and success. The sessions and topics of the day are custom made for you to learn, benefit and contribute. More and more Indian companies are aspiring to join the Billion dollar club and are well on track on getting there. “Breaking the Glass Ceiling” and exploring beyond, forms the core theme of Emerge Out Pune.
Emerge Out Pune is all about participation of companies from the product, mobility, services space and beyond and offers a unique opportunity for organisations to collaborate and partner with the key stake holders. We have tried our best to package the day in a way that there is something and more for everyone to take away, as we know for an Emerge company, it is always “Yeh Dil Mange More”
(BMC Software Pune has created a by-the-techies, for-the-techies group, called The Ninja Club, to give the technical individual contributors in the company a place to learn, hang out, and get recognition for their work. This article about the Ninja Club is by guest author Neeran Karnik, an Architect at BMC.)
The problem is well known in the IT industry in India – why are smart techies tempted to switch to the management ladder, a few years into their careers? The industry loses technical talent, and quite possibly, gets saddled with mediocre management talent in the bargain! Techies who stay on the technical track complain about a lack of control, a lack of visibility, and a lack of rewards. Society also seems to treat “managers” as an exalted breed, and someone who remains an individual contributor is seen as having stagnated in his or her career.
The Ninja Club at BMC is a techies-only club, created to provide cross-team visibility for techies, encouraging collaboration, peer reviews of design and code, and in general, letting the smartest techies interact with each other more easily.
Organizations are taking different approaches to tackle this problem – including creating explicit technical ladders, giving more high-profile recognition for technical accomplishments, even awarding junkets for creating IP. At BMC Software, we have taken a somewhat different approach – a grassroots effort in the technical community that is backed by, but not actively promoted by management. It’s loosely patterned after the martial arts, and is called the Ninja Club.
The Ninja Club is a forum created by techies, for techies. Its membership is self-selected (by invitation), purely on the basis of demonstrated accomplishments on the technical front. As such, membership itself is a badge of honour. In addition however, like in a martial arts discipline, members qualify for different coloured belts – starting with white, and earning their way to black. These belts are completely independent of the usual grades or bands in the HR system, and unrelated to promotions and performance evaluations. A points system has been put in place – a Ninja earns points for activities such as technical talks, participating in coding contests and ideation sessions, filing invention disclosures, publishing conference papers / whitepapers, etc. Points make you eligible for ‘promotion’ to the next coloured belt: white –> yellow –> green –> red –> black. But promotion is not necessarily automatic – in addition to points, the Ninja may have to get past, for example, an online programming test or an interview by other Ninjas at the higher belt level.
Like martial artists, the idea is that Ninjas get together regularly to practice their skills – coding, design, etc. – and to learn from each other. To that end, the Ninja Club organizes various activities such as coding contests, design review sessions, etc. for club members. We are also starting Special Interest Groups (SIGs) focused around technology areas like Big Data, Cloud Computing, SaaS, etc. Discussions can also be around the business domain (IT management and data centers, in BMC’s case) and customer use-cases, not necessarily on technology. Smaller groups of Ninjas can get together in SIGs to discuss, brainstorm, and do small side projects on such topics of their interest.
Such activities enable techies to network across their product teams, find role models and/or mentors, benefit from peer review of their ideas, and expand their sphere of influence. However, the club also organizes wider events that are open to everyone at BMC, not just its members. Over the past year, Ninja Club has organized the following different types of events:
Ninjutsu: Quizzes focused on technology and programming – with questions ranging from tech trivia to ‘spot the bug in a snippet of code’
Kaigi: Technical talks on hot topics like Hadoop, Android development…
Tougi: Debates, where teams argue for or against a given proposition, such as the effects of Consumerization of IT, “BYOD”, or Desktop Virtualization
Online contests like treasure hunts, crosswords, etc.
A screenshot of one of the pages in the Ninja Club, powered by eMee.
One key element of Ninja Club is its online presence, in the form of a gamified social network called eMee. This was developed at Persistent Systems, and heavily customized by them for BMC. Ninjas get their own profiles and avatars on eMee, using which they can showcase their technical skills, certifications and accomplishments. Points earned for various activities can be exchanged for ‘gifts’ that are used for decorating your house. Promotion to a higher belt results in your moving to a fancier house! Like in the martial arts, a Ninja can have ‘followers’. You can follow your role models or mentors, to keep track of their activities and status updates. Common news items are published to the “Ninja Times”, and visible to all. Non-Ninjas also get their own limited profiles, and the ability to follow Ninjas. A search mechanism allows anyone to find people with specific skills. This melding of the real and virtual worlds in eMee levels the playing field for smart programmers who may not be very social in the real world!
The hope is that this Ninja Club initiative will improve the technical vitality of the organization, and make technical careers more desirable and rewarding. By providing cross-team visibility, encouraging collaboration, and peer reviews of design and code, product functionality and quality should also improve over time. Success will eventually be measured in terms of the quality and growth of the technical populace at BMC Software, and being seen as the techies’ employer of choice in the region!
About the Author – Neeran Karnik
Neeran Karnik is an architect at BMC for their Bladelogic Server Automation product. Before that Neeran has worked at IBM India on the datacenter automation and cloud computing products in the Tivoli group, and as a Technical Director and Research at Symantec, and a Research Staff Member at IBM India Research Lab. Neeran has a Ph.D. in Computer Sciences from University of Minnesota, USA.
Neeran is also one of the co-founders of Cricinfo.
Do you have a cool app that is making life of a customer easier, helping them save time and be more productive? Do you have an app which is enabling people to connect them to their family and friends – easily, and in a fun way to help them come closer? Is it desirable, usable and consumable? If yes, then here is the place for you.
NASSCOM would like to provide visibility to your application at the NASSCOM EMERGEOUT Forum. The conference will showcase the Top 8 mobile applications that are part of the ecosystem as game changers and provide recognition to them.
Last date for submission is 25th September, 2012. The finalists will be announced by 5th October 2012, after which the shortlisted contestants will have to showcase the same on the 12th of October during the Emergeout Conclave, Pune. For any queries, write to Darryl@nasscom.in.
Criterion for selection:
The eligible entries which match up to the criteria will be judged by our jury members, constituting of industry experts. An overview of the criteria is appended below:
Accessibility and Availability: What mobile platforms the
application can successfully run?
Usability/Creativity: The application demonstrates superior user
experience (UI, graphics, etc.) e.g. by leveraging the latest technologies.
Uniqueness/Novelty Value: Display creativity in applications, use
established technology in a unique and innovative way, leverage the latest
technologies, etc.
Market Potential: Size of target market for which the app is
relevant and accessible. Potential to monetize.
Traction: Current downloads, revenue generated, partnerships for
distribution etc.
Submission Requirement & Eligibility:
This Contest is open only to start-ups & EMERGE companies headquartered in India only. Register here
The call for speakers for the IndicThreads’ software technology conference is open. The conference is in December, but the CFP closes this week (22 September), and you should submit a proposal
IndicThreads have been holding tech conferences in Pune for the last 7 years, and their conferences are the top pure technology conferences in Pune. An IndicThreads conference is one of the best places to hear about the latest trends in the software industry, and to meet techies from large and small companies of not only Pune, but the rest of the country too.
The conference itself is paid, but becoming a speaker is a good way to get into the conference for free.
This time around, the conference will cover a wide range of technologies from Java, Cloud Computing, Mobile App Development to emerging technologies like Big Data, Gamification, HTML5. (Traditionally, IndicThreads used to have a Java conference – but this year, they are broadening the theme.)
The CFP calls for submissions in these areas:
Software Architecture
Cloud Computing: IaaS, SaaS, PaaS
Design methodology
Mobile Software Platforms
Mobile Software Development
Software Testing
Optimization, Scaling, Caching and Performance Tuning
Java Language Specs & Standards
Enterprise Java (JavaEE)
JVM Languages
Software Security
Development Frameworks
Big Data
NoSQL Software Development
Agile
HTML5
New and emerging technologies
Case Studies and Real World Experiences
But feel free to submit other topics in software technology too. The audience consists mostly of software architects and project leads from various product and services companies across India. If you have done any interesting work in one of the areas above, you should submit a proposal. For now, all you need to do is submit a one paragraph abstract of what you’d like to talk about.
Why?
Because you get a free pass to the conference
Get recognized amongst the community as an expert in an area
It strengthens the tech community in Pune, which benefits all of us.
(This is a liveblog of a lecture on Network Neutrality by V. Sridhar, a Fellow at Sasken. This talk was delivered as a part of the Turing100@Persistent Lecture Series in Pune. Since it is being typed as the event is happening, it is not really well structured, but should rather be viewed as a collection of bullet points of interesting things said during the talk. For more information about Dr. Sridhar, see his website)
The Problem of Net Neutrality
The principle of “Net Neutrality” states that all traffic on the internet should be treated equally. Thus, the principle states that network service providers (i.e. the telecom companies) should not be allowed to discriminate (i.e. limit or disallow) on network connections and speeds based on the type of traffic. Thus, for example, under net neutrality, a telecom should not be allowed to disallow BitTorrent Downloads, or limit bandwidth for Skype or Video streaming, or provide higher speeds and better quality of service guarantees for just traffic generated by iPhones or US-based companies.
Telecom companies are trying to introduce systems by which different levels of service are provided for different types of traffic, because, they argue that network neutrality is not economically viable.
The Demand for Network Services
Mobile broadband and 3G traffic is increasing exponentially
Even in India! In the last 7 months there has been 78% growth in 3G traffic, and 47% growth in 2G. India loves mobile broadband
Users are getting hooked to 3G. An average 3G user consumes 4 times more data than a 2G user. 3G is an acceptable alternative to wired broadband
Mobile data is growing fastest in smaller towns and villages (category B & C circles)
Video, voice, and streaming data are taking up huge chunks of bandwidth
NetHeads vs BellHeads
There are two major approaches to the network: the traditional telephone providers who come from a circuit switched Telephone background (the BellHeads), and the people who come from the packet-switched internet protocol background (the NetHeads). The BellHeads believe that the network is smart, endpoints are dumb; they believe in closed, proprietary networks; they expect payment for each service; often with per-minute charges; they want to control the evolution of the network and to control everything about the network. They want strong regulations. The NetHeads philosophy is that network is dumb, and endpoints are smart. So users should take all the decisions; they believe in an open community; and they expect cheap or free services, with no per-minute charges; they want the network to evolve organically without regulations.
To a large extent, the NetHeads are for net neutrality and the BellHeads are in favor of abolishing net neutrality in favor of carefully controlled tiered traffic.
The Supply Side
Land-line penetration is decreasing. On the other hand, mobile penetration continues to increase and is showing no signs of saturation. Fixed-line is losing its relevance, especially in case of emerging countries in India. Which means that increasing chunk of the internet bandwidth is going to be consumed by mobile devices.
LTE (the Long Term Evolution) mobile network is the fastest growing network ever. 300+ different operators all over the world are investing in LTE. This will come to India soon.
Mobile technologies are improving, and individual devices will soon be capable of handling 1Gbps data connections. This means that the capacity of the core network will have to go up to provide the speeds that the device is capable of consuming. And the NetHeads are making good progress and being able to provide high capacities for the core networks.
The problem is that the mobile spectrum is a scarce resource, and will soon become the bottleneck. The other problem is that chunks of the spectrum have to be exclusively allocated to individual operators. And then that operator has to operate just within that chunk.
The Problem of the Commons
When people have shared, unlimited access to a common resource, then each will consume the resource without recognizing that this results in costs for everyone else. When the total amount that everybody would like to consume goes above what is totally available, everybody suffers. This is a problem which will affect the mobile spectrum. The spectrum gets congested, and bandwidth suffers.
How to solve the congestion problem?
Congestion pricing. For example, cheaper access after 9pm is an instance of congestion pricing – an attempt to convince some of the users to consume resources when they’re less congested.
During periods of congestion, bandwidth is scarce and hence should have high prices. On the other hand, when the network is not congested, then the additional cost of supporting an additional user’s downloads is minimal, hence the user should be given free or very cheap access.
The Net Neutrality Debate
Net neutrality believes that the maximum good of maximum people will happen if networks service providers do not discriminate amongst their customers.
No discrimination means:
No blocking of content based on its source, ownership or destination
No slowing down or speeding up of content based on source, ownership or destination
Examples of discrimination:
In 2005, Madison River Communications (an ISP) blocked all Vonage VoIP phone traffic
In 2007, Comcast in the US, restricted some P2P applications (like BitTorrent)
In 2009, AT&T put restrictions on what iPhone apps can run on its network
Disallowed SlingPlayer (IP based video broadcast) over it’s 3G network
Skype was not allowed to run over AT&T’s 3G network
The case for net neutrality:
Innovation: Operators/ISPs can kill innovative and disruptive apps if they’re allowed to discriminate
Competition: Operators/ISPs can kill competition by selectively disallowing certain applications. For example, if AT&T slows down Google Search, but speeds up Bing Search, this can cause Google Search to die.
Consumers: Operators/ISPs will have a strong grip on the consumers and other players will not get easy access to them. This will hurt the consumers in the long run.
The case against net neutrality:
Capacity is finite. Especially in the case of mobile broadband (because the spectrum is limited)
If there is no prioritization, a few apps will consume too much bandwidth and hurt everybody; and also it reduces the service provider’s motivation to increase bandwidth
Prioritization, and higher pricing for specific apps can be used to pay for new innovations in future network capacity increases
Broadband is a two-sided market:
Apps and Broadband is a two-sided market.
Both, applications and bandwidth are needed by consumers
Without applications, users will not consume the bandwidth, because they have nothing interesting to do
Without bandwidth, users will not use applications, because they’ll be too slow
Hence both have to be promoted simultaneously
How should a two-sided market be handled?
Usually, one side should to be subsidized so it can grow and help the other grow
e.g. Somebody needs to break this cycle and grow one side of this market, so that the other can then grow
For example, Google (an app/content provider) is buying fiber and providing 1Gbps connection in Kansas for $70 per month. Thus Google is subsidizing the bandwidth increase, and hopes that the users and apps will increase in proportion.
Regulatory and Policy implications
Two ways to handle this:
Ex Ante: come up with regulations and policies before problems occur
Because lawsuits are expensive
US is trying to do this – they have exempted mobile providers from net neutrality principles
Netherlands has passed net neutrality regulations – first country in the world. Mobile operators are not allowed to disallow or discriminate against services like Skype
Rest of Europe: public consultations going on
Ex Post: Let the problems occur and then figure out how to deal with them
Net Neutrality and India
No mention of net neutrality in the NTP (National Telecom Policy 2012)
Fair Usage Policy (FUP)
Is against net neutrality (maybe)
It discriminates against users, but does not discriminate against applications
But it is indirect discrimination against applications – because users who use BitTorrent and other bandwidth heavy applications will be more affected by FUP
Affects innovation – because users are discouraged from using innovative, bandwidth heavy applications
(This is a liveblog of the Turing100@Persistent Lecture on Bob Kahn and Vint Cerf by R. Venkateswaran, CTO of Persistent Systems. Since it is being typed as the event is happening, it is not really well structured, but should rather be viewed as a collection of bullet points of interesting things said during the talk.)
Vint Cerf and Bob Kahn
Vint Cerf: Widely known as the father of the internet. He is President of the ACM, Chief Internet Evangelist at Google, Chairman of the ICANN and many other influential positions. In addition to the Turing Award, he has also received the Presidential Medal of Freedom in 2005 and was elected to the Internet Hall of Fame in 2012.
Bob Kahn: Worked at AT&T Bell Labs, MIT, then while working with BBN, he got involved with the DARPA and Vint Cerf and they together worked on packet switching networks, and invented the IP and TCP.
The birth of the internet: TCP and IP. 70s and 80s.
The Internet:
The first 20 years:
Trusted network
Defense, Research and Academic network
Non-commercial
Popular apps: email, ftp, telnet
Next 20 years:
Commercial use
Multiple levels of ownership – increased distrust and security concerns
Wide range of apps: email, WWW, etc
What did Vint Cerf and Bob Kahn do?
The problem:
There were many packet switched networks at that time
But very small, limited and self contained
The different networks did not talk to each other
Vint Cerf and Bob Kahn worked on interconnecting these networks
Each network talked its own protocol, so they wanted a protocol neutral mechanism of connecting the networks.
Each network had its own addressing scheme, so they had to invent a universal addressing scheme.
Packets (information slices) forwarded from one host to another via the “internetwork”
Packets sent along different routes, no guarantees of in-order delivery. Actually no guarantee of delivery
Packets have sequence numbers, so end point needs to reassemble them in order
The protocol
A “process header” identifies which process on the end host should be delivered the packets. This is today called the “port”
Retransmissions to ensure reliable delivery. And duplicate detection.
Flow control – to limit number of un-acknowledged packets, prevent bandwidth hogging
A conceptual “connection” created between the end processes (TCP), but the actual network (IP) does not know or understand this
Mechanism to set up and tear down the “connection” – the three-way handshake
This are the main contributions of their seminal paper
The Layered Network Architecture
Paper in 1974 defining a 4 layered network model based on TCP/IP.
This later became the basis of the 7 layer network architecture
The Internet Protocol
Packet-switched datagram network
Is the glue between the physical network and the logical higher layers
Key ideas:
Network is very simple
Just route the packets
Robust and scalable
Network does not guarantee any thing other than best effort
No SLA, no guarantee of delivery, not guarantee of packet ordering
Dumb network, smart end-host
Very different from the existing, major networks of that time (the “circuit-switched” telephone networks of that time)
No state maintained at any node of the network
Advantages
Can accommodate many different types of protocols and technologies
Very scalable
The Transport Layer
UDP
Most simplistic higher level protocol
Unreliable, datagram-based protocol
Detect errors, but no error corrections
No reliability guarantees
Great for applications like audio/video (which are not too affected by packet losses) or DNS (short transactions)
TCP
Reliable service on top of the unreliable underlying network
Connection oriented, ordered-stream based, with congestion and flow control, bi-directional
State only maintained at the end hosts, not at the intermediate hosts
Internet 2.0 – Commercialization
The birth of the world wide web: late 80s early 90s
Tim Berners-Lee came up with the idea of the the world-wide-web
1993: Mosaic, the first graphical web browser
First Commercial ISP (Internet Service Provider) – Dial up internet
Bandwidth doubling every 6 months
Push for multi-media apps
Push for higher bandwidth and rich apps
Net apps (like VoIP, streaming video) demand higher bandwidth
Higher bandwidth enables other new applications
Apps: email, email with attachments, streaming video, intranets, e-commerce, ERP, Voice over Internet, Interactive Video Conferencing
Dumb Network no longer works
Single, dumb network cannot handle all these different applications
Next Generation Networks evolved
Single, packet-switched network for data, voice and video
But with different levels of QoS guarantees for different services
Clash of Network Philosophies: BellHeads vs NetHeads (mid-90s)
Two major approaches: the BellHeads (circuit switched Telephone background), and the NetHeads (from the IP background)
BellHeads philosophy: network is smart, endpoints are dumb; closed, proprietary communities; expect payment for service; per-minute charges; Control the evolution of the network; want strong regulations
NetHeads philosophy: network is dumb, endpoints are smart; open community; expect cheap or free services; no per-minute charges; want network to evolve organically without regulations.
These two worlds were merging, and there was lots of clashes
BellHead network example: Asynchronous Transfer Mode (ATM) network
Fixed sized packets over a connection oriented network
Circuit setup from source to destination; all packets use same route
Low per-packet processing at each intermediate node
Much higher speeds than TCP/IP (10Gbps)
A major challenge for the NetHeads
Problems for NetHeads
To support 10Gbps and above, each packet needs to be processed in less than 30ns, which is very difficult to do because of all the processing needed (reduce TTL, lookup destination address, manipulate headers, etc)
As sizes of networks increased, sizes of lookup tables increased
Almost read to concede defeat
IP Switching: Breakthrough for NetHeads
Use IP routing on top of ATM hardware
Switch to ATM circuit switching (and bypass the routing layer) if a long-running connection detected.
Late 90s, all IP networking companies started implementing variations on this concept
MPLS: Multi-Protocol Lable Switching
Standard developed by IP networking companies
Insert a layer between TCP and IP (considered layer 2.5)
Separates packet forwarding from packet routing
Edges of the network do the full IP routing
Internal nodes only forward packets, and don’t do full routes
Separate forwarding information from routing information, and put forwarding info in an extra header (MPLS label – layer 2.5)
Internal nodes only look at MPLS label, and forwards appropriately, without doing any routing and without looking at IP packet
Last node (edge; egress LSR) removes the MPLS label
Label switching at intermediate nodes can be implemented in hardware; significant reduction in total latency
MPLS is now basis of most internet networking
Internet 3.0: The Future
End of the network centric viewpoint. (Note: These are futuristic predictions, not facts. But, for students, there should be lots of good project topics here.)
Internet was designed for co-operative use; not ideal for today’s climate
Multi-homing not well supported by TCP/IP
Change in IP address results in service disruption
What if you change your ISP, your machine, etc?
Cannot be done seamlessly
Network is very machine/ip centric (“Where”)
What is needed are People-centric networks (“Who”) and content centric (“What”)
IP address ties together identity and location; this is neither necessary, nor desirable
Three areas of future research:
Delay Tolerant Network (DTN) Architecture
Whenever end-to-end delay is more than a few 100 milliseconds, various things start breaking in today’s networks
DTN’s characterized by:
Things that are not always connected to the network. For example, sensor networks, gadgets, remote locations. Another Example: remote villages in Africa have a bus visiting them periodically, and that gives them internet access for a limited time every day.
Extremely Long Delays
Asymmetric Data Rates
High Error Rates
Needs a store-and-forward network
Content-centric Networks
Instead of everything being based on IP-address, how about giving unique identifiers to chunks of content, and define a networking protocol based on this
Strategy: let the network figure out where the content is and how to deliver it
Security: the content carries the authorization info, and unauthorized access is prevented
Software Defined Networks
Virtualizing the Network
Search the net for: “OpenFlow”
Hardware Router only does packet forwarding, but end applications can update the routing tables of the router using the OpenFlow protocol. App has a OpenFlow controller that sends updates to the OpenFlow agent on the Hardware Router.
In the hardware/OS world, virtualization (VMWare, Xen, VirtualBox) are slowly taking over; OpenFlow is a similar idea for network hardware
Oracle, VMWare have had major acquisitions in this space recently
Vinton Cerf and Robert Kahn invented TCP and IP, the two protocols at the heart of the internet, and are hence considered the “Fathers of the Internet”. For this and other fundamental contributions, they were awarded the Turing award in 2004.
On 8th September, R. Venkateswaran, CTO of Persistent Systems, will give a talk on the life and work of Vint Cerf and Bob Kahn as a part of the Turing 100 Lecture Series organized by Persistent in Pune on the first Saturday of every month (although this month it was shifted to the second Saturday).
In addition, this Saturday’s event will also feature a talk on “Net Neutrality: The Supply and Demand Side Perspective” by Dr. V Sridhar, a research fellow with Sasken.
About the Turing Awards
The Turing awards, named after Alan Turing, given every year, are the highest achievement that a computer scientist can earn. And the contributions of each Turing award winner are then, arguably, the most important topics in computer science.
About Turing 100 @ Persistent Lecture Series
This year, the Turing 100 @ Persistent Lecture Series will celebrate the 100th anniversary of Alan Turing’s birth by having a monthly lecture series. Each lecture will be presented by an eminent personality from the computer science / technology community in India, and will cover the work done by one Turing award winner.
The lecture series will feature talks on Ted Codd (Relational Databases), Vint Cerf and Robert Kahn (Internet), Ken Thompson and Dennis Ritchie (Unix), Jim Gray, Barbara Liskov, and others. Full schedule is here
This is a lecture series that any one in the field of computer science must attend. These lectures will cover the fundamentals of computer science, and all of them are very relevant today.
Fees and Registration
This is a free event. Anyone can attend.
The event will be at Dewang Mehta Auditorium, Persistent Systems, SB Road, from 2pm to 5pm on Saturday 8th September. This event is free and open for anybody to attend. Register here
