text:
Perl 5 Unleashed
Perl 5
by Kamran Husain and Robert F. Breedlove
Chapter 1 What is Perl?
- Why Perl?
- A Brief History of Perl
- The Benefits of Using Perl
- What Are the Negatives of Using Perl?
- What Can Perl Do?
- Is Perl for You?
- Summary
Chapter 2 A Brief Introduction to Perl
- Running Perl
- Variables in Perl
- Arrays and Associative Arrays
- Array Operations
- File Handles and Operators
- Working with Patterns
- Subroutines
- A Final Note
- Summary
Chapter 3 References
- Introduction to References
- Using References
- The Backslash Operator
- References and Arrays
- Using Multidimensional Arrays
- References to Subroutines
- Implementing State Machines
- Passing More Than One Array into a Subroutine
- References to File Handles
- Using Symbolic References
- Strict References
- For More Information
- Summary
Chapter 4 Introduction to Perl Modules
- What Is a Perl Module?
- Using Perl Modules: use vs. require
- The Sample Letter.pm Module
- Subroutines and Passing Parameters
- Another Sample Module: Finance
- Multiple Inheritance
- The Perl Module Libraries
- Summary
Chapter 5 Object-Oriented Programming in Perl
- Introduction to Modules
- Classes in Perl
- Creating a Class
- Blessing a Constructor
- Methods
- Exporting Methods with Exporter.pm
- Invoking Methods
- Overrides
- Destructors
- Inheritance
- Overriding Methods
- A Few Comments About Classes and Objects in Perl
- Summary
Chapter 6 Binding Variables to Objects
- The tie() Function
- Tying Scalars
- Tying to an Array
- Tying to an Associative Array
- For More Information
- Summary
Chapter 7 String and Patterns
- Basic String Operations
- Finding Substrings
- Reusing Portions of Patterns
- Pattern-Matching Options
- Substituting Text Through Pattern Matching
- The Translation Operator
- Extended Pattern Matching
- Summary
Chapter 8 Documenting Perl Scripts
Chapter 9 Portability Issues with Windows and Perl
- Perl for Windows
- Getting the Distribution
- Differences in Perl on NT and UNIX
- Unsupported Functions
- Extensions to Perl 5 for Windows NT
- Problems with Windows 95
- Summary
Chapter 10 Win32 Modules on Windows NT
- The Win32 Module
- The Process Module Extensions
- The Kill Method
- The Win32::Semaphore Utilities
- Using Mutex with Win32::Mutex
- Using Win32::ChangeNotification
- The Win32::Eventlog Module
- The Win32::Registry Module
- The Win32::NetAdmin Module
- Using the Win32::Service Module
- Using the Win32::NetResource Module
- Handling Input from Multiple Sources
- Summary
Chapter 11 Security Issues in Perl
- A Few Words Before We Begin
- Setuid Scripts
- Why Is Perl More Secure Than Shell Scripts?
- Some Tips on Making Scripts Secure
- The Perl Safe.pm Module
- Setuid CGI Scripts and CGIwrap
- Reference Books
- Summary
Chapter 12 Using Sockets
- A Very Brief Introduction to Sockets
- Perl Functions for Working with Protocols
- Socket Primitives
- Connection-Oriented Servers in Perl
- The h2ph Script
- Using Socket.pm
- Summary
Chapter 13 Messaging Facilities: The System V Ipc Functions
- An Introduction to the System V Ipc
- Using the UNIX System V Ipc Functions
- The ipcs Command
- The msgsnd() and msgrcv() Functions
- Shared Memory
- Semaphores
- The SysV::Ipc Module
- Applications of Ipc
- Summary
Chapter 14 Signals, Pipes, FIFOs, and Perl
- Signals
- The kill() Function
- The warn() Function
- Timeouts
- Pipes and FIFOs
- Using open() for Ipc
- Summary
Chapter 15 Direct Access to System Facilities
- Introduction
- Working with UNIX Users and Groups
- Getting Information in Network Files
- Getting and Changing the Priority of a Process
- System-Level Functions
- Summary
Chapter 16 Command-line Interface with Perl
- The Command-line Options to Perl
- Sending Options via the Command Line
- Specifying an Option within the Program
- The -c and -w Syntax Checking and Warning Options
- The -e Option: Executing a Single-line Program
- The -s Option to Supply Custom Command-line Options
- The -I Option to Include Other Files
- The -P Option for Using the C Preprocessor
- Using the -n and -p Options for Handling Multiple Files
- The -i Option to Edit Files
- Using the -a Option
- Using the -F Option
- Using the -0 Option
- Using the -l Option
- Using the -x Option to Get a Perl Program from Another File
- Using the -S Option
- The -v Option: Printing the Perl Version Number
- Using Conditional Code with the C Preprocessor
- Reading Input from STDIN
- The Getopts Package
- Summary
Chapter 17 GUI Interfaces with Perl/Tk
- Introduction to the Perl/Tk Package
- Where Do I Get and Build Perl/Tk?
- Documentation for Perl/Tk
- Writing Scripts in Perl/Tk
- Widgets as Building Blocks
- Configuring Widgets
- Handling the Keyboard with Key Bindings
- Displaying a Bitmap
- Displaying Images with Photo
- Menus
- The Canvas Widget
- Miscellaneous Topics
- Summary
Chapter 18 Databases for Perl
- The DBM Packages
- Viewing Your Data
- Adding and Removing Items
- Operations on a DBM File
- Using DBM in Modules
- Multiple DBM Files
- The Catch with DBM Utilities
- What Is the DBI Package?
- Summary
Chapter 19 Generating Reports
- Formatted Output
- Defining a Format
- Using the format Statement
- Using More Than One Format
- Controlling the Format
- Creating Multiple Lines with the Caret
- Using format in Modules
- Another Example of Report Generation
- Summary
Chapter 20 Introduction to Web Pages and CGI
- HTML, CGI, and MIME
- A Simple HTML Document
- Formatting Lists
- Using HTML Tags
- Preformatted Text
- Special Characters in HTML Documents
- What Is a URL?
- CGI Scripts
- Input and Output to CGI Scripts
- A Test CGI Script
- Using Frames
- Summary
Chapter 21 Building VRML Models with Perl
- What Is VRML?
- Basics of VRML
- Building the VRML Perl Module
- Using VRML.pm
- How to View Your World
- Inside the VRML.pm Package
- Summary
Chapter 22 Using HTML FORMs with Perl CGI Scripts
- Input and Output with CGI
- What Are GET and POST?
- Handling HTML FORMs with GET Methods
- Handling an HTML FORM with POST Methods
- Returning HTML Pages
- Using the Collected Data
- Summary
Chapter 23 HTML with Perl Modules
- Presenting Data on the Web Using CGI Scripts
- Collecting User Input Using Perl Modules
- Using Tables in HTML
- Using the HTML Module
- Constructing HTML Objects
- Specifying the Body of the Text in HTML Documents
- Controlling the Output Destination File
- Using the Tables Feature in HTML::Base
- Making Clickable Images in HTML
- Summary
Chapter 24 Building and Installing the Perl 5 Interpreter
- Getting Perl 5
- Installing Perl on Most UNIX Systems
- Running Some Tests
- The DOS Platform
- Other Platforms
- Linux: A Special Case for Perl 5
- Summary
Chapter 25 Perl Internal Files and Structures
- Introduction
- Perl Variable Types
- Scalars and Scalar Functions
- Array Functions
- Hash Functions
- Mortality of Variables
- Subroutines and Stacks
- What Is Magic?
- The Global Variable (GV) Type
- Where to Look for More Information
- Summary
Chapter 26 Writing C Extensions in Perl
- Introduction
- Compiling a C Program That Calls Perl
- Adding a Perl Interpreter to Your C Program
- Calling Perl Subroutines from Within a C Program
- Working with the Perl Stack
- The Flags to Use
- Using SCALAR Context
- Returning Lists from Subroutines
- Using G_EVAL
- Getting Special Variable Values
- Using the ST Macros
- Evaluating Perl Expressions
- Pattern Matches and Substitutions from Your C Program
- Summary
Chapter 27 Writing Extensions in C
- Introduction to XS
- Steps for Creating an Extension
- The xsubpp Compiler
- Input and Output Parameters to Functions
- The bootstrap Function
- Passing Arguments
- The RETVAL Variable and the OUTPUT Section
- Keywords
- The Listings of Modules
- Summary
Chapter 28 Client/Server Using Java Applets and Perl
- Using CGI or Sockets
- Using the Disk
- Using CGI and Sockets
- For More Information on How to Program in Java
- Summary
Chapter 29 Practical Scripts While Using Perl
- Statistical Applications
- Using Perl for Simple Statistical Routines
- Using Matrices
- The Filter
- An Added Touch
- A Parting Note
- Summary
Chapter 30 Using the Perl Debugger
- A Sample Session
- Stepping Through Code
- Looking at Values
- Breakpoints
- Actions
- Searching for Patterns
- Subroutines
- Caveats
- Customizing Your Debugger Environment
- For More Information
- Summary
Chapter 31 Generating Code
- Introduction
- Choosing the Input File
- Parsing Records
- Writing the C Header Files
- Writing the Encoder Source File
- Writing the Decoder
- Putting It Together
- Summary
Chapter 32 Dynamic Image Creation
- Introduction
- Two-Dimensional Plots
- Three-Dimensional Plots
- Using the Output in CGI Applications
- Creating GIF Images Directly from Perl
- Working with GD.pm
- Using GD with HTML Pages
- Summary
Chapter 33 Debugging CGI Applications
- Wrong Permissions on CGI Scripts
- Use the Perl Interpreter Line on UNIX Systems
- Libraries for Dynamically Loaded Modules
- Check for Support for System Calls
- Don't Return Malformed Headers
- Flush Output Buffers Immediately
- Don't Set Environment Variables
- Clean Up After Yourself
- Configure Your Server Correctly
- Always Create an index.html File
- Summary
appendix A Perl 5 Function and Variable Reference
appendix B Perl Module Archives 737
- CPAN Sites
- Perl 5 Module List
- Newsgroups
- Web Pages
- Frequently Asked Questions (FAQ) Lists
- Mailing Lists
- Other Resources
- Summary
To my family, my wife Madeline for giving me the time and encouragement, and my children Delenn, Duncan, and Diego for setting my life in perspective. -BB
Copyright © 1996 by Sams Publishing
All rights reserved. No part of this book shall be reproduced, stored in a retrieval system, or transmitted by any means, electronic, mechanical, photocopying, recording, or otherwise, without written permission from the publisher. No patent liability is assumed with respect to the use of the information contained herein. Although every precaution has been taken in the preparation of this book, the publisher and author assume no responsibility for errors or omissions. Neither is any liability assumed for damages resulting from the use of the information contained herein. For information, address Sams Publishing, 201 W. 103rd St., Indianapolis, IN 46290.
International Standard Book Number: 0-672-30891-6
HTML conversion by :
M/s. LeafWriters (India) Pvt. Ltd.
Website : http://leaf.stpn.soft.net
e-mail : email@example.com
All terms mentioned in this book that are known to be trademarks or service marks have been appropriately capitalized. Sams Publishing cannot attest to the accuracy of this information. Use of a term in this book should not be regarded as affecting the validity of any trademark or service mark.
|Richard K. Swadley
|Publishing Team Leader
|Greg Wiegand
|Managing Editor
|Cindy Morrow
|Director of Marketing
|John Pierce
|Assistant Marketing Managers
|Kristina Perry, Rachel Wolfe
|Acquisitions Editor
|Christopher Denny
|Development Editor
|Anthony Amico
|Software Development Specialist
|Brad Myers
|Production Editors
|Kristi Hart, Katherine Ewing
|Copy Editor
|Bart Reed
|Chris Barrick
|Technical Reviewers
|Zachary Bir, John Fleming, Elliotte Harold, Scott Hutton, Matt Liggett, John Neinart
|Editorial Coordinator
|Bill Whitmer
|Technical Edit Coordinator
|Lynette Quinn
|Editorial Assistants
|Carol Ackerman, Andi Richter, Rhonda Tinch-Mize
|Cover Designer
|Tim Amrhein
|Book Designer
|Gary Adair
|Copy Writer
|Peter Fuller
|Production Team Supervisor
|Brad Chinn
|Debra Bolhuis, Mona Brown, Michael Dietsch, Jason Hand, Daniel Harris, Bill Hartman, Susan Knose, Clint Lahnen, Paula Lowell, Laura Robbins, Bobbi Satterfield, Susan Van Ness, Suzanne Whitmer
First of all, I would like to thank Chris Denny at Sams for giving me the opportunity to write a book on Perl 5. I would also to thank Kristi Hart, Tony Amico, and Bart Reed for their patience, help, advice, and forcing me to keep up with deadlines.
I'd like to thank Uzma, my wife, and Haya and Hana, my twin daughters, for putting up with my weird schedules and odd hours.
Last, but definitely not the least, thanks to all the Perl programmers on Perl mailing lists for all the critique and comments via e-mail.
About the Authors
Kamran Husain is a software consultant specializing in developing real-time applications, data acquisition, and turn-key systems in all sorts of software environments including C++, Java, Windows NT and 95, JavaScript, and Motif. He can be reached via e-mail at email@example.com.
Robert F. Breedlove is a senior systems engineer with EDS. He has over 20 years of experience in data processing including extensive client/server, UNIX, intranet and Internet experience. He can be reached at email@example.com, or at his homepage: http://www.channel1.com/users/rbreed01/.
Tell Us What You Think!
As a reader, you are the most important critic and commentator of our books. We value your opinion and want to know what we're doing right, what we could do better, what areas you'd like to see us publish in, and any other words of wisdom you're willing to pass our way. You can help us make strong books that meet your needs and give you the computer guidance you require.
Do you have access to CompuServe or the World Wide Web? Then check out our CompuServe forum by typing GO SAMS at any prompt. If you prefer the World Wide Web, check out our site at http://www.mcp.com.
If you have a technical question about this book, call the technical support line at (800) 571-5840, ext. 3668.
As the team leader of the group that created this book, I welcome
your comments. You can fax, e-mail, or write me directly to let
me know what you did or didn't like about this book-as well as
what we can do to make our books stronger. Here's the information:
|Greg Wiegand
Comments Department
Sams Publishing
201 W. 103rd Street
Indianapolis, IN 46290
This book documents a very powerful language called Perl 5, which is version 5 of Larry Wall's creation, Perl. Perl is fast becoming the de facto language for UNIX system administrators, Webmasters on the World Wide Web, and programmers who want a fast, powerful, and easy-to-use program language. This book will provide you with the basics of the language and introduce you to the tools available for Perl.
While writing this book, I assumed that you, the reader, have had some prior programming experience. If you do not have any prior programming experience, I strongly suggest not skipping the first three chapters. If you are already a programmer and are familiar with Perl 4, this book should provide you with enough knowledge to use the great new features.
How This Book Is Organized
This book is divided into six parts.
Part I: The Basics
The first part provides a brief introduction to Perl as a programming language. It covers the use of references to variables, regular expressions, and the fundamentals of programming in Perl by using modules. It introduces the use of Perl for programming with an object-oriented paradigm. It also covers the not-so-basic but very important topic of tying variables in Perl programs.
Part II: Communications
The second part covers applying Perl to different platforms and types of applications. It begins with a chapter on processing patterns and strings in Perl. For a long time, I debated reversing the order of Chapters 6 and 7 because the concepts are both fundamental, but the chapter on tying variables seemed to fit in the first part. Most of the portability issues in programming in Perl on a Windows platform are also discussed in this part.
Part III: Presenting and Sharing Data
The third part gets into networking and system-level programming issues for Perl. The basic communications features in Perl include sockets, System V Ipc messaging facilities, signals, pipes, and FIFOs, and are covered in this part. The basics of handling the command-line interface as well as a graphical user interface using Tcl/Tk and Perl are also covered in this part. The last two chapters of this part introduce the use of database front-ends and the report-generating facilities of Perl. The information in this part serves as the basis for writing Perl applications that can provide reports on data stored in databases.
Part IV: Working with the Web
Section four introduces the World Wide Web and the Common Gateway Interface (CGI). Thick books have been written on these topics, and this part attempts to present the most practical information required to get you started writing CGI scripts and your own Web pages. This part covers how to access databases from within Perl and how to write your own module to generate VRML objects. The information in this chapter can serve as a basis for writing your own CGI scripts using the modules available on the World Wide Web for Perl.
Part V: Under the Hood
The chapters in this part are geared towards the advanced user or the system administrator who has to install Perl on various platforms. The topics in this part tend to be centered on UNIX systems, but that's just where most of the heavy Perl development seems to be. I cover the internal data types used in Perl, and then based on this knowledge I go on to show the techniques of writing extensions and embedding Perl in C programs.
This part covers the use of the Perl debugger. This was the part where I wanted to present some case studies on how to use Perl as a prototyping language to solve problems. I use Perl to solve some real-world problems involving parsing weird data formats and creating images on demand, and then I discuss issues on how to debug CGI applications. This part also covers how to use Java applets on a client to communicate with Perl servers, which is a hot Internet topic.
Conventions Used in This Book
The following typographic conventions are used in this book:
- Code lines, commands, statements, variables, and any text you type or see on the screen appears in a computer typeface. When lines of input and output are shown together, bold computer typeface is used to show the user's input.
- Placeholders in syntax descriptions and
code snippets appear in italic
computer typeface.
Replace the placeholder with the actual filename, parameter, or whatever element it represents.
- Italics are used to emphasize important points.
- Sometimes a line of code is too long to fit as a single printed line in the book. If you see the special icon  at the beginning of a line of code, you should interpret that "line" as a continuation of the line preceding it.
There's Always a Better Way
Now for a personal disclaimer of sorts. Even though I attempt to cover all the major points of the latest release of Perl, version 5.002 at the time we go to print, I probably will never be able to list all the features of this wonderful language. If there is one thing that I've learned while working with Perl, it is that there are so many ways of doing any one task. Every time I write a Perl script, I think that I "could've done it this way and maybe it'll run faster." The number of combinations of things to do with Perl never really ends. So, if you find a better way of writing Perl scripts than the ones shown in this book, don't be surprised-it's bound to happen. Do drop me a line, though, because I will incorporate them into the next edition of this book. I look forward to receiving all your comments and, yes, even criticisms and the usual flames.
Kamran Husain

subset: commoncrawl


text:
Daddy Li waited no further and tried it out!
The results are more precise than other shavers that Daddy Li has tried before. He also found it very easy to shave with the anti-slip grip and slim handle. The ReflexAction System allowed him to shave easily as the blades followed the contour of his lips and chin and he didn't have to worry about getting any cuts or razor bumps.
Do follow Philips Twitter page at Do follow Philips Twitter page at https://twitter.com/PhilipsSG and participate in the Twitter games to win up to $100 shopping vouchers!
You can find out more here - Philips GSS Promotion
*Disclaimer: The Philips Electric Shaver was sponsored by Philips. All content, comments and reviews are based on our own opinion/view of the product and brand and was not influenced by any external factors.


text:
World Cup qualifying action is back as England do battle with Wales in their Group 6 tie in Cardiff. England are the favourites and are quoted at 2/5 to do the double over Wales, having beaten them 2-0 at Old Trafford in October last year. Wales are quoted at 6/1, however England will be looking to solidify their position in Group 6 and a win against the Welsh team is vital if England want to remain in control of the group. Other World Cup qualifying action features Northern Ireland vs. Azerbaijan, and Scotland v Italy. For full match odds and specials on all the World Cup qualifiers plus live betting on all these games visit www.coral.co.uk
Defending US Open champion Roger Federer has missed the majority of the summer hard court season nursing a minor injury; however, he won the only event in which he competed and is quoted at 1/2 to add the US Open title to his 2005 Wimbledon title. The player who most believe has the best chance to challenge Federer's supremacy is French Open champion and number 2 seed Rafael Nadal. Spaniard Nadal's youthful exuberance makes him as strong a challenger as any during the US Open and he is quoted at 5/2. Other players to watch out for are veteran Andre Agassi at 18/1 and world number 14 Thomas Johansson at100/1.
On the women's side Kim Clijsters has dominated the hard-court season and has looked strong during the past few weeks. Odds of 2/1 may look very generous by this time next week. Another strong contender is Venus Williams, the elder Williams sister who, has never failed to follow up a Wimbledon victory with an US open title and is currently quoted at 9/1. Other players to watch out for are Frenchwoman A. Mauresmo at 14/1 and veteran Mary Pierce at 40/1.
This weekend also features Formula One action from Imola in Italy and the highlight of the cricket domestic season, with Hampshire facing Warwickshire in the C & G Trophy Final. It will be a great weekend of sports betting and coral.co.uk has you covered.
**Please note that prices are subject to change**
Coral Eurobet (www.coraleurobet.com), based in the UK and in Gibraltar, is one of the world's leading gaming and fixed-odds bookmaking businesses, providing up-to-the minute sports betting and gaming products throughout the world including its online Poker, online Arcade games and online Casinos. In addition to its online business, it operates over 1200 licensed betting offices in the UK, a significant telephone betting business and two leading UK greyhound stadia.
Weekend betting action from Coral.co.uk
Company: Coral Eurobet
Contact Name: Emma Jordan
Contact Email: email@example.com
Contact Phone: 01483766766
Contact Name: Emma Jordan
Contact Email: firstname.lastname@example.com
Contact Phone: 01483766766


text:
It's pretty much a given that, for any individual player, spring training stats are meaningless as a projection of what might happen when the season starts. Not that this stops us from poring over them, worrying as a starter's ERA tilts towards double figures, or cheering as a backup infielder hits .400. But as a projection of regular season performance, they are basically useless. The one exception John Dewan discovered is that
When we chose only those players doing exceptionally well in spring training, we found that about three-fourths of them performed better than their career average during the upcoming season. Our definition of "exceptionally well" was slugging 100 points higher in spring training than their previous career slugging percentage.
But is this because the sample size - many players will get less than 60 at-bats in spring - is just so small as to be useless? What if we combined the numbers and looked at spring training performance on the team level, giving us a sample size maybe 30 times as big? Do they offer any potential insight into how a team might perform during the regular season?
Firstly, here's a quote from a front-office source, regarding the general relevance of spring-training stats, and how they are seen by the teams.
"We go into the spring with a baseline evaluation of each individual player and his role within the club and organization. During the spring, we try to measure each player against this baseline. The lower that initial valuation or our certainty in regards to that evaluation, the more sensitive we are going to be to that individual's performance in the spring. The statistics only matter in that they are a reflection of the performance that those performing on field evaluations are seeing."
What I did was collate various numbers for the sixteen National League teams over the course of spring training, and then compared them to the same numbers during regular-season play in April. It seemed likely that, if there was a connection to spring numbers, the first month would show this the clearest, as team performance will inevitably vary over the course of an entire season - a lot can happen between April and September. Here's the Google Doc with Spring and April team stats
I then worked out the correlation between the spring and April numbers. Statistically, correlation measures the relationship between two sets of data, and ranges from +1 to -1. +1 means an almost perfect match (for instance, if one set of data was 1, 2, 3, 4 and the other 2, 4, 6, 8, that'd have a correlation of +1); -1 means the data are inversely related i.e. the higher X is, the less Y is, while 0 means no apparent relationship. Now, there are limitations - these four graphs all have the same correlation, despite widely varying data, and correlation does not prove causation. But a lack of correlation would strongly suggest no connection between spring numbers and regular season ones.
Pitching statistics
- BA against: correlation 0.131
- OBP against: 0.119
- SLG against: 0.229
There seems to be some evidence, albeit pretty weak, in most of these categories, to suggest a slight link between performance in spring training and once Opening Day starts. Though only the GO/AO ratio reaches the level where the relationship appears to be particularly significant - if your team gets a lot of ground-balls in spring, it seems this is a trend that may continue into the regular season. Slugging percentage allowed shows a medium correlation, but the other categories barely crept over the 0.1 level, which marks the bottom of the "small correlation" range.
Hitting statistics
- BA: correlation -0.035
This was a surprise. While there was almost no correlation between spring and regular-season batting average, there was a negative one for on-base percentage. This means that the better teams were at getting on-base in Florida and Arizona, the worse they were in April. The poster-child for this was the Houston Astros: in spring, their OBP trailed only one team, but in the games that counted, they were abysmal, at .281, over thirty points worse than the 15th-ranked franchise. The same reverse correlation existed for GO/AO, the opposite of what we found for pitchers.
The sole area that did show a positive, albeit small, relationship was stolen-base percentage. To some extent, this may make sense, because of teams like the Padres, who explicitly expressed, early in spring-training, that they were going to be more aggressive on the base-paths this year. "We're going to press the limits on the bases this spring so we learn what our limits are," said Dave Roberts, hired as a special adviser to the team. The top team in spring, the Brewers, at 83%, were also the best in April, going 18-1 in stolen-base attempts.
Defense and W-L record
- Fielding %: -0.131 correlation
- Defensive Efficiency: -0.214
- Stolen-base % Allowed: -0.171
Again, a surprise. Any relationship between the numbers, is a negative one - the worse a team does fielding in spring, the better they do in the regular season. Any explanation for why this might be, would be welcome! However, as in most of the numbers, the correlation remains too low to draw any significant connection. There is a little more, but still marginal, connection between overall record in spring and in April - it'd have been closer, except for the Nationals turning it around, going 10-20 in Grapefruit League, then 13-10 in April. That said, I note the teams among the closest to spring training - the Marlins, Padres, Dodgers and D-backs - all had winning percentages in April less then 25 points away from their pre-season number...
More or less the same goes for team performance as for individual performance: spring training numbers offer a very limited insight into what can be expected from a team's bats, arms or defense. The only area where the 2010 numbers showed any real correlation was in the ground-out/fly-out ratio returned by pitchers - and, let's be honest, that's hardly something on which we hang with baited breath during the regular season. Please bookmark this article, and treat it as the sabermetric equivalent of a brown-paper bag, into which you can breathe when the D-backs suck at [insert aspect of game] in the 2011 Cactus League.


text:
Barks & Wags
Regular price
₹ 799.00
Your pet will look great in our printed blue tees. These lightweight t-shirts and tank tops for dogs are made with a breathable single jersey blend with Velcro on the sides for easy wearability. It's machine washable and comes in all sizes, so your pet can stylishly stand out.


text:
When we build Web infrastructures at Etsy, we aim to make them resilient. This means designing them carefully so that they can sustain their (increasingly critical) operations in the face of failure. Thankfully, there have been a couple of decades and reams of paper spent on researching how fault tolerance and graceful degradation can be brought to computer systems. That helps the cause.
To make sure that the resilience built into Etsy systems is sound and that the systems behave as expected, we have to see the failures being tolerated in production.
Why production? Why not simulate this in a QA or staging environment? First, the existence of any differences in those environments brings uncertainty to the exercise, and second, the risk of not recovering has no consequences during testing, which can bring hidden assumptions into the fault-tolerance design and into recovery. The goal is to reduce uncertainty, not increase it.
Forcing failures to happen, or even designing systems to fail on their own, generally isn't easily sold to management. Engineers are not conditioned to embrace their ability to respond to emergencies; they aim to avoid them altogether. Taking a detailed look at how to respond better to failure is essentially accepting that failure will happen, which you might think is counter to what you want in engineering, or in business.
Take, for example, what you would normally think of as a simple case: the provisioning of a server or cloud instance from zero to production:
This is probably an oversimplification, and each step or layer is likely to represent a multitude of CPU cycles; disk, network and/or memory operations; and various numbers of software mechanisms. All of these come together to bring a node into production.
Operability means that you can have confidence in this node coming into production, possibly joining a cluster, and serving live traffic seamlessly every time it happens. Furthermore, you want and expect to have confidence that if the underlying power, configuration, application, or compute resources (CPU, disk, memory, network, etc.) experience a fault, then you can survive such a fault by some means: allowing the application to degrade gracefully, rebuild itself, take itself out of production, and alert on the specifics of the fault, etc.
This confidence is typically built in a number of ways:
Traditionally, these sensible measures to gain confidence are taken before systems or applications reach production. Once in production, the traditional approach is to rely on monitoring and logging to confirm that everything is working correctly. If it is behaving as expected, then you don't have a problem. If it is not, and it requires human intervention (troubleshooting, triage, resolution, etc.), then you need to react to the incident and get things working again as fast as possible.
This implies that once a system is in production, "Don't touch it!"—except, of course, when it's broken, in which case touch it all you want, under the time pressure inherent in an outage response.
This approach isn't as fruitful as it could be, on a number of levels.
In the field, you need to prepare for undesirable circumstances. Power can get cut abruptly. Changes to the application or configuration can produce unforeseen behaviors, no matter how full the coverage of testing. Application behavior under various resource-contention conditions (think traffic spikes from news events or firehose-like distributed denial-of-service attacks) can have surprising results. This isn't a purely academic curiosity; these types of faults can (and will) affect production and, therefore, in Etsy's case, our sellers and our business. These types of events, however, are difficult to model and simulate with an accuracy that would inspire confidence in the system's behavior in the face of these problems.
The challenge is that Web systems (like many "complex" systems) are largely intractable, meaning that:
In other words, while testing outside of production is a very proper approach, it's incomplete because some behaviors can be seen only in production, no matter how identical a staging environment can be made.
Therefore, another option must be added to the confidence-gaining arsenal: fault injection exercises sometimes referred to as GameDay. The goal is to make these faults happen in production in order to anticipate similar behaviors in the future, understand the effects of failures on the underlying systems, and ultimately gain insight into the risks they pose to the business.
Causing failures in complex systems isn't a new concept. Organizations such as fire departments have been running full-scale disaster drills for decades. Web engineering has an advantage over these types of drills in that the systems engineers can gather a massive amount of detail on any fault at an extremely high resolution, wield a very large amount of control over the intricate mechanisms of failures, and learn how to recover very quickly from them.
Constructing a GameDay exercise at Etsy follows this pattern:
The greatest advantage of a GameDay exercise is figuring out how to prevent a failure from affecting the business. It's hard to overstate the importance of steps 1 and 2. The idea is to get a group of engineers together to brainstorm the various failure scenarios that a particular application, service, or infrastructure could experience. This will help remove complacency about the safety of the overall system. Complacency is an enemy of resilience. If a system has a period of little or no degradation, there is a real risk of it drifting toward failure on multiple levels, because engineers can become convinced—falsely—that the system is experiencing no problems because it is inherently safe.
Imagining failure scenarios and asking, "What if...?" can help combat this thinking and bring a constant sense of unease to the organization. This sense of unease is a hallmark of high-reliability organizations. Think of it as continuously deploying a BCP (business continuity plan).
In theory, the idea of GameDay exercises may seem sound: you make an explicit effort to anticipate failure scenarios, prepare to handle them gracefully, and then confirm this behavior by purposely injecting those failures into production. In practice, this idea may not be appealing: it brings risk to the forefront, and without context, causing failures on purpose may seem crazy. What if something goes wrong?
The traditional view of failure in production is avoidance at all costs. The assumption is that failure is entirely preventable, and if it does happen, then find the persons responsible (usually those closest to the code or systems) and fire them, in the belief that getting rid of "bad apples" is how you bring safety to an organization.
This perspective is, of course, ludicrous. Fault injection and GameDay scenarios can produce a more pragmatic and realistic view.
When I approached Etsy's executive team with the idea of GameDay exercises, I explained that it's not that we want to cause failures out of some perverse need to watch infrastructure crumble; it's that we know that parts of the system will inevitably fail, and we need to gain confidence that the system is resilient enough to handle failure gracefully.
The concept, I explained to the executives, is that building resilient systems requires experience with failure, and that we want to anticipate and confirm our expectations surrounding failure more often, not less often. Shying away from the effects of failure in a misguided attempt to reduce risk will result in poor designs, stale recovery skills, and a false sense of safety.
In other words, it's better to prepare for failures in production and cause them to happen while we are watching, instead of relying on a strategy of hoping the system will behave correctly when we aren't watching. The worst-case scenario with a GameDay exercise is that something will go wrong during the exercise. In that case, an entire team of engineers is ready to respond to the surprises, and the system will become stronger as a result.
The worst-case scenario in the absence of a GameDay exercise is that something in production will fail that wasn't anticipated or prepared for, and it will happen when the team isn't expecting or watching closely for it.
How can you assure that injecting faults into a live production system doesn't affect actual traffic, revenue, and the end-user experience? This can be done by treating the fault-toleration and graceful degradation mechanisms as features. This means bringing all the other confidence-building techniques (unit and functional testing, staging hardware environments, etc.) to these resilience measures until you're satisfied. Just like every other feature of the application, it's not finished until you've deployed it to production and have verified that it's working correctly.
Earlier this year Etsy rolled out a new payment system (http://www.etsy.com/blog/news/2012/announcing-direct-checkout/) to provide more flexibility and reliability for buyers and sellers on the site. Obviously, resilience was of paramount importance to the success of the project. As with many Etsy features, the new system was rolled out to production in a gradual ramp-up. Sellers who wanted to use this new payment method could opt in, and Etsy turned the functionality on for groups of sellers at a time.
As you might imagine, the payment system is not particularly simple. It has fraud-detection components, audit trails, security mechanisms, processing-state machines, and other components that need to interact with each other. Thus, Etsy has a complex mission-critical system with very high expectations for resiliency.
To confirm its ability to withstand failures gracefully, Etsy put together a list of reasonable scenarios to prepare for, develop against, and test in production, including the following:
The engineers then put together all of the expectations for how the system would behave if these scenarios occurred in production, and how they could confirm these expectations with logs, graphs, and alerts. Once armed with these scenarios, they worked on how to make these failures either:
After these mechanisms were written and tested in development, the time came to test them in production. The Etsy team was cognizant of how much activity the system was seeing; the support and product groups were on hand to help with any necessary communication; and team members went through each of the scenarios, gathering answers to questions such as:
The team was able to confirm most of the expected behaviors, and the Etsy community (sellers and buyers) was able to continue with its experience on the site, unimpeded by failure.
There were some surprises along the way, however, which the Etsy team took as remediation items after the exercise. First, during the payments process, a third-party fraud-detection service was contacted with information about the transaction. While Etsy uses a number of external APIs (fraud, device reputation, etc.), this particular service had no specified timeout on the external call. When testing the inability to contact the service, the Etsy team used firewall rules both to hard close the connection and to attempt to hang it open. Having no specified timeout meant that they were relying on the default, which was much too long at 60 seconds. The intended behavior was to fail open, which meant that the transaction could continue if the external service was down. This worked, but only after the 60-second timeout, which caused live payments to take longer than necessary during the exercise.
This was both a surprise and relatively easy to fix, but it was nonetheless an oversight that affected production during the test.
Recovering from database corruption also took longer than expected. The GameDay exercise was performed on one side of a master-master pair of databases, and while the recovery happened on the corrupted server, the remaining server in the pair took all reads and writes for production. While no production data was lost, exposure with reduced capacity occurred for longer than expected, so the Etsy team began to profile and then try to reduce this recovery time.
The cultural effect of the exercise was palpable. It greatly decreased anxiety about the ramp-up of the payments system; it exposed a few darker-than-desired corners of the code and infrastructure to improve; and it increased overall confidence in the system. Complacency is not an immediate threat to the system as a result.
The goal of fault injection and GameDay exercises is to increase confidence in an otherwise complicated or complex system's ability to stay resilient, but they have limitations.
First, the exercises aren't meant to discover how engineering teams handle working under time pressure with escalating and sometimes disorienting scenarios. That needs to come from the postmortems of actual incidents, not from handling faults that have been planned and designed for.
The faults and failure modes are contrived. They reflect the fault designer's imagination and therefore can't be comprehensive enough to guarantee the system's safety. While any increase in confidence in the system's resiliency is positive, it's still just that: an increase, not a completion of perfect confidence. Any complex system can (and will) fail in surprising ways, no matter how many different types of faults you inject and recover from.
Some have suggested that continually introducing failures automatically is a more efficient way to gain confidence in the adaptability of the system than manually running GameDay exercises as an engineering-team event. Both approaches have the same limitation mentioned here, that they increase confidence but can't be used to achieve sufficient safety coverage.
Automated fault injection can carry with it a paradox. If the faults that are injected (even at random) are handled in a transparent and graceful way, then they can go unnoticed. You would think this was the goal: for failures not to matter whatsoever when they occur. This masking of failures, however, can result in the very complacency that they are intended (at least should be intended) to decrease. In other words, when you've got randomly generated and/or continual fault injection and recovery happening successfully, care must be taken to raise the detailed awareness that this is happening—when, how, where, etc. Otherwise, the failures themselves become another component that increases complexity in the system while still having limitations to their functionality (because they are still contrived and therefore insufficient).
A lot of what I'm proposing should simply be an extension of the confidence-building tools that organizations already have. Automated quality assurance, fault tolerance, redundancy, and A/B testing are all in the same category of GameDay scenarios, although likely with less drama.
Should everything have an associated GameDay exercise? Maybe, or maybe not, depending on your level of confidence in the components, interactions, and levels of complexity found in your application and infrastructure. Even if your business doesn't think that GameDay exercises are warranted, however, they ought to have a place in your engineering toolkit.
Why would you introduce faults into an otherwise well-behaved production system? Why would that be useful?
First, these failure-inducing exercises can serve as "vaccines" to improve the safety of a system—a small amount of failure injected to help the system learn to recover. It also keeps a concern about failure alive in the culture of engineering teams, and it keeps complacency at bay.
It gathers groups of people who might not normally get together to share in experiencing failures and to build fault tolerance. It can also help bring the concept of operability in production closer to developers who might not be used to it.
At a high level, production fault injection should be considered one of many approaches used to gain confidence in the safety and resiliency of a system. Like unit testing, functional testing, and code review, this approach is limited as to which surprising events it can prevent, but it also has benefits, many of which are cultural. We certainly can't imagine working without it.
John Allspaw is senior vice president of tech operations at Etsy. He has worked in systems operations for more than 14 years in biotech, government, and online media. He started out tuning parallel clusters running vehicle crash simulations for the U.S. government and then moved on to the Internet in 1997. He built the backing infrastructures at Salon, InfoWorld, Friendster, and Flickr. He is the author of The Art of Capacity Planning (O'Reilly Media, 2008) and Web Operations (O'Reilly, 2010).
Originally published in Queue vol. 10, no. 8—
Comment on this article in the ACM Digital Library
Sanjay Sha - The Reliability of Enterprise Applications
Enterprise reliability is a discipline that ensures applications will deliver the required business functionality in a consistent, predictable, and cost-effective manner without compromising core aspects such as availability, performance, and maintainability. This article describes a core set of principles and engineering methodologies that enterprises can apply to help them navigate the complex environment of enterprise reliability and deliver highly reliable and cost-efficient applications.
Robert Guo - MongoDB's JavaScript Fuzzer
As MongoDB becomes more feature-rich and complex with time, the need to develop more sophisticated methods for finding bugs grows as well. Three years ago, MongDB added a home-grown JavaScript fuzzer to its toolkit, and it is now our most prolific bug-finding tool, responsible for detecting almost 200 bugs over the course of two release cycles. These bugs span a range of MongoDB components from sharding to the storage engine, with symptoms ranging from deadlocks to data inconsistency. The fuzzer runs as part of the CI (continuous integration) system, where it frequently catches bugs in newly committed code.
Robert V. Binder, Bruno Legeard, Anne Kramer - Model-based Testing: Where Does It Stand?
You have probably heard about MBT (model-based testing), but like many software-engineering professionals who have not used MBT, you might be curious about others' experience with this test-design method. From mid-June 2014 to early August 2014, we conducted a survey to learn how MBT users view its efficiency and effectiveness. The 2014 MBT User Survey, a follow-up to a similar 2012 survey, was open to all those who have evaluated or used any MBT approach. Its 32 questions included some from a survey distributed at the 2013 User Conference on Advanced Automated Testing. Some questions focused on the efficiency and effectiveness of MBT, providing the figures that managers are most interested in.
Terry Coatta, Michael Donat, Jafar Husain - Automated QA Testing at EA: Driven by Events
To millions of game geeks, the position of QA (quality assurance) tester at Electronic Arts must seem like a dream job. But from the company's perspective, the overhead associated with QA can look downright frightening, particularly in an era of massively multiplayer games.


text:
From the longer years, we are manufacturing and supplying, trading the whole sum types of Clean Room Equipments to our reliable consumers. Our made equipments are more valuable for the various labs, packaging industries, research centers, pharma industries and many places… our clean room equipments are created with the admirable quality of stainless steel material so the products are enduring for years and much durable.
Most of the parts, our offered clean room equipments are used for remove particles and harmful contaminants from the floors. Importantly, you can buy these equipments without thinking as it is simple to operate and maintain and get from our company at nominal cost price.
Excellent features
- Admirable quality
- Simple to operate
- Easy to maintain


text:
The following consists of replies to some difficulties raised by students of philosophy and religion.
What is Philosophy?
It has been argued that the system of philosophy which is known as Advaita, propounded by Acharya Sankara, is not a philosophical system, since it accepts the authority of the scripture, and philosophy does not accept scriptural testimony as a test of truth. To this point of view, several answers may perhaps be appropriate. Firstly, the term 'Advaita' need not necessarily be associated with Sankara, because it stands for a way of thinking or a doctrine which can be promulgated by a methodology of reason. Even if Sankara had not been born, this system of human thought would remain as a way of possible logical analysis and synthesis. Perhaps it would not be difficult to see that the conclusions which are associated with Advaita can be drawn even without reference to any scripture or theological background. That historical circumstances required Acharya Sankara to consider Scripture as the final authority would not preclude the great logical acumen which is demonstrated in his writings, which can stand independently as a supreme philosophical system, even without any reference to Scripture. Hence, a true student of philosophy need not have to mix up the theological atmosphere of Sankara's times with the philosophical conclusions that he drew by pure reason alone.
Further, it is strange that philosophy should be interpreted as a position totally opposed to Scripture or irreconcilable with Scripture, if we are to consider Scripture as an accepted hypothesis which itself cannot be questioned, and not necessarily a book written by someone or even revealed to anyone. Which scientific method or philosophic situation can be said to be free from the necessity to be finally grounded on some hypothesis on which it bases itself and on whose pedestal it raises the edifice of its system? How would science or philosophy or any thinking process at all assume a sense or meaning if it is not to found itself on some irrefutable fact which is already accepted not as something deduced from a premise, since a premise itself cannot be deduced? Indian philosophers, whether they accept the authority of Scripture or not, had also amply revealed in their expositions the great power of reason which, while it was not necessary for it to refute Scripture, could also stand on its own legs.
The Nature of Reality
It is also argued that the Advaita position that Brahman is consciousness is a sort of self-contradiction, for consciousness is a quality. To this, it has to be said that consciousness is certainly not a quality, nor can it be a product of the conjunction of the subject and the object as some thinkers have tried to establish. If consciousness were a quality, it would have to be a quality of something other than consciousness, but what on earth can that be which is other than consciousness? That so-called something which is other than consciousness has necessarily to be also that which is not known to consciousness, in which case it cannot be related to consciousness, and consciousness cannot be related to it. Where then comes the question of consciousness being a quality of anything at all? Secondly, it is contended that the Advaita conclusion that Brahman (the Absolute) is consciousness is not tenable, for, it is argued, the statement "Brahman is consciousness" is tautological. The point is that if Brahman is consciousness, it would be like saying that Brahman is Brahman, and to say that Brahman is consciousness would be like an analytic judgement, not a synthetic one, adding no new information to the subject Brahman, since Brahman is already said to be consciousness. This objection arises on account of introducing the defects of linguistic grammar into a philosophic proposition, for we cannot see any tautology in the statement that Brahman is consciousness, inasmuch as the statement is intended to describe the characteristic of Brahman, or, we may say, the constituent essence of Brahman, or, rather, more precisely, what Brahman is. Hence, the statement "Brahman is consciousness" does not introduce the conjunction 'and', so that there should be Brahman 'and' consciousness in order that Brahman may be consciousness. The grammatical copula 'is' in the statement "Brahman is consciousness" does not distinguish between Brahman and consciousness, but is only a verbal contrivance necessitated by the exigency of grammar. The spirit of the statement is the real philosophic position, and not the form of the linguistic structure of the sentence. It is well known that every sentence involves a subject and a predicate linked together by a verb. Only, in the present context, neither Brahman nor consciousness can be taken as a predicate, because one and the same thing is asserted even when two terms are used. Thus, it appears the objection is not philosophical. The statement "Brahman is consciousness" cannot be considered as a truism, as if it is a well known fact, for it requires an elucidatory effort to come to the conclusion that the nature of Brahman is consciousness. If a father makes a statement, "Rama is my son", it does not follow that the statement is tautological or a truism, for, while Rama and son mean one and the same person, the one term explains the intrinsic nature of that which is indicated by the other.
Is the World Unreal?
It has often been glibly and sarcastically opined by many a thinker that the Advaita doctrine propounds the unreality of the world, the illusoriness of all things, that nothing exists at all. While the process of an investigation into the validity of the question of the unreality of the world is a little intricate and need not be discussed here, it is not true that the Advaita crudely brushes aside the content of world-experience as a literal unreality. No content of an experience can be regarded as totally unreal as long as there is such a thing as experience, and no one with the least sense would dub an experience as unreal as long as it remains an experience. But, while it is certainly true that the very meaning of experience is that it 'is there', and no one will speak of it if it is not there, no experience can be considered as unreal as long as it 'is' an experience, whether it is of the world or anything else. Yet, there is certainly something more to be said about this phenomenon. Would we call it an experience when it is contradicted by another experience subsequently following it? The famous analogy of the experience of a snake in the rope is before us. Is the snake real? No one would say that it is unreal, for it is a content of experience which is real. But, at the same time, there is a point which requires a more judicious consideration of the issue, since, in a different experience which is of the rope, the snake is realised to be unreal. Who would ever regard the snake as a reality on the perception of the rope as a real experience? It appears to us that the analogy of the snake and the rope, which is so well known, is not a puerile connivance of some psychological whim, but a most apt illustration of the position of the world as a whole and of man's location in the world. It would thus be obvious how one and the same proposition can be unreal as well as real in two different contexts, while not being self-contradictory as a blending of totally opposite positions.
It may also be added here that it would not be wisdom to stretch even the weapon of logic to its breaking point, for logic is a function of reason operating on the dichotomy of the subject and the object, while at the same time feeling the necessity to bring together the two as an integral statement.
The Basis of Proof
If there are no proofs which can demonstrate Brahman's reality, this need not be considered as a serious defect in the situation. Rather, it should be happily accepted as the glory of truth itself, which is also associated with eternity. How is one to prove the eternal through non-eternal means, and what eternal means are available to man in a world of temporal processes? What proof does one expect to establish the existence of Brahman, as Brahman is the basis of all proof, the indubitable existence as the very self of the one who argues and thinks in terms of proof? How would it be proved by some other proof, and where is the point in expecting a proof at all?
Evidence from Sleep
The illustration of experience in the state of deep sleep sometimes advanced in the Advaita system as an evidence of the existence of an absolute being, is not without substance. Reversing the Cartesian proposition, "I think, therefore I am," the analogy cited is an adventure in the direction of the conclusion, "I am, therefore I think." Would there be a need to bring a proof that one's own self exists? Obviously, it is not hard for one to realise that proofs proceed from the fundamental experience of there being such a thing as self, and if the self itself were to be an object of doubt, there would be no worth-the-while conclusion in life, which would be free from the defect of the same doubt. If there is anything at all which cannot be doubted, it has to have a base which itself cannot be doubted. All this would be commonplace to any sensible point of view.
Now comes the question, What happened in deep sleep? This is one of the great analyses made in the system of Advaita philosophy. While in the waking state the body seems to be the whole of the reality of oneself, in dream one's existence is proved to be possible without association with the physical body. The point that comes to relief in deep sleep is that one can and one does exist there in a condition wherein even the mind does not operate, and one's existence in the state of sleep is free from association of every kind, physical as well as psychological. It is no great feat of discovery to make much of the psychological difficulty involved in understanding the nature of the memory that remains subsequent to sleep, of one's having existed in the state of sleep. That the physical and the psychological embodiments are not the reality of a person is the essence of the discovery which is made from one's existence in sleep. Whether sleep is a biological condition, or is brought about by this factor or that, is irrelevant for the purpose. We need not go into the details here as to how and why one enters the state of deep sleep. The Upanishad has something to say about it, while the medical man or the psychologist and the scientist may have something else to say from their own points of view. These considerations, however, do not touch the essential point made out in the study of the self in sleep, that it is impossible to set aside the conclusion that the self is basically of the stuff of consciousness. While the experience of joy in sleep is attributed to different factors and can be explained in several ways, it is impossible to believe that there can be satisfaction in a state of unconsciousness. No doubt, sleep is a state of unconsciousness and it should be a contradiction for anyone to believe that such sleep should have any value. Is it not strange that the value of sleep seems to outweigh any other value, even if it is to be considered only as a reminder, though occasional, that man is evidently something other than what he appears to be in his much-adumbrated waking activity?
It is said that the condition of sleep cannot be regarded as an experience because this condition is an 'event' and all events are not experiences. To this it is to be pointed out that it is difficult to understand what an 'event' can be if it is not existent, and what can existence mean if it is not something that is known to exist? Precisely, an experience is the knowledge of existence; it may be the existence of an event, a condition, a situation, a thing, or whatever it be. Then, why should not sleep be an experience, if it is an event? Further, the argument that in order to call an event an experience, it must be an event of which someone is the subject, does not in any way affect the issue on hand; for, how could sleep be an experience or an event if it is not an experience to someone or an event occurring in respect of someone or something? In fact, what exists, or, precisely, is, in the state of sleep is the pure subject alone. In sleep there is an indication of subjectivity, free from traces of all objectivity, if only we are not to consider the state of unconsciousness as an object counterposed before a subject. The definition of consciousness has also to be made a little clear. Consciousness cannot be considered as something happening to someone, whether it is noticed or not. Philosophically, the term 'consciousness', when it is applied to describe the pure metaphysical subject, is to be understood as denoting something more than even what is usually called self-consciousness. It is the basic presupposition of any meaning whatsoever. Hence, such a subliminal base of the very meaning of anything, the primary being or existence of whatever can be regarded as meaningful, has to be something not only not associated to any other primary being which may be its subject, but should be not even a state of self-consciousness in the sense of one being one's own object of awareness. It is pure universality, consciousness as such, which cannot be distinguished from being as such. Thus, consciousness need not mean noticing, seeing or any kind of happening to anyone. This latter empirical characterisation of consciousness may have the utilitarian value of a grammatical subject, or sensorily conditioned individuality localised in space and time. But consciousness has to supersede space and time, since the former knows the latter as its content. The suggested pure subject indicated by the experience of sleep is not an ego, which latter is a self-conscious, localised, embodied something, but a general state of reality which encompasses all that can be anywhere or at any time. The subject indicated in sleep is not the enjoying or suffering subject, for it is prior to every psychological condition, since, here again, psychological experiences are its contents.
Experience is not 'doing something', for the fact of doing anything would be the object of a consciousness prior to it. Thus, we find that consciousness cannot be associated with anything other than itself, neither an event nor a thing. The Advaita argument of the presence of bliss in the state of deep sleep, as evidenced by a subsequent memory thereof, cannot be just brushed as totally irrelevant. There is certainly a great point which the Advaita makes out here. It is logically impossible to conceive of memory or remembrance except as a conscious recollection of a previous experience. Since experience cannot be dissociated from a consciousness of it, the conclusion that consciousness is not absent in the state of sleep cannot also be ruled out. As regards the experience of happiness in sleep, it is up to anyone to prove it or disprove it. An intense subjectivity to which consciousness is driven in sleep should be considered as the explanation for the happiness mentioned. The nearer one moves to oneself, the truer one is, and, hence, freer; and, is not freedom a state of happiness? It is entanglement in objectivity that distracts the attention of consciousness by making it appear as something other than its own self, which may safely be called a sort of metaphysical schizophrenia. The utter subjectivity which everyone craves for as an emblem of total freedom is demonstrated by man in the process of history. No one would like to be other than oneself, or involved in what one is not. Such empirical involvements are not present in sleep, and though this not-being-present is a kind of negative freedom and an entry into pure subjectivity through the backdoor (this, incidentally, differentiates sleep from Samadhi, or universal consciousness), there is no doubt that this apparent negativity becomes at least a suggestion of the possibility of positive subjectivity, even as the reflection of an object, which may be said to be the negative presentation of the object, indicates the nature of that object itself. In studies of this type, one may have to be dispassionate and honest, as far as one's own feelings and experiences are concerned, and not allow an empirical logic to interfere with its validity, for, as we have noted, logic is not a permanent friend of the very source of logicality. We need not identify this source entirely with the Transcendental Unity of apperception of Immanuel Kant, but here is certainly its elder brother, as it were, and the presence of it none can deny without denying the denier's existence itself. In a way, the true self is reflected in spatio-temporal involvement in the state of waking and, evidently, philosophers are right when they opine that the world is a dream, if it is true that all spatial and temporal experience is a shadow cast through the screen of objectivity by that which is the archetype transcending the space-time network. Plato's analogy of the cave is profound and pertinent, and it is a happy augury that in a more explicit manner this truth is coming to light through the discoveries of modern physics, into whose findings we need not enter here.
On the Question of Creation of the Universe
All descriptions concerning the origin or creation of the universe are intended to clarify philosophical and psychological situations which arise due to an inborn belief that the world must have an origin, and must have a creator. This is a hypothesis which cannot itself be explained by any rational process of investigation. Why should it be necessary for the world to have a creator outside itself? Why should anyone create a problem and then try to find a solution for it? Has anyone seen God creating the world? But how is it that people everywhere speak of the creation of the world as if they have witnessed God working at the beginning of things. The circumstance actually involves two facets, namely, (a) belief in the word of the Scripture, which narrates the story of creation by God; (b) a necessity felt by inductive logic and the natural manner of human thinking that everything that is visible must have come from somewhere and that all things must have been made by someone as a cause preceding an effect.
Taking the first issue, namely, the descriptions and explanations in the Scriptures, it is no doubt true that the Scripture of every religion, except those that do not bring in a God into the picture, speaks of God creating the world out of His own Will, not because He has a desire but it is His Nature automatically operating, as the sun shedding light without any desire to do the work of shining. Firstly, therefore, it has to be accepted that God creating the universe does not imply an action like some human being working, because God is timeless Being, and no action is conceivable where time is absent. Hence it is fallacious to take the creation theory literally, as if God is some large man thinking and working like man only. Creation is like the four-dimensional realm of modern physics appearing as a three-dimensional world of empirical experience. And no scientist will say that four-dimensional existence has 'created' the three-dimensional world. The electrons or the atoms do not "create" the stone of which they are the internal constituents. This would land us on the question: Is the world really there? For, if a stone is really there, it should be visible to the microscope which sees only a pressure of electromagnetic force commensurate with the entire structure of the universe. In this light, the world and God would be two names for one and the same thing, and any question regarding creation by God would fundamentally lack scientific basis.
The renowned philosopher, Acharya Sankara, says that theories of creation are not intended to describe an actual historical process of the world coming from God, as if God started manufacturing things in some ancient time, but that these stories of the procession of effects from God at the top are indicative of a higher truth that God alone is, inasmuch as the logical relationship between effect and cause negatives any difference between the two, thus merging the effect in the cause, that is to say, leaving God alone to Himself with no world whatsoever as a product externally created.
The infinity and the omnipresence of God, which is accepted by everyone, precludes the possibility of a world being there outside God. An appearance of a reality cannot be regarded as something created by reality. Hence all problems arising in respect of desire, playfulness, constraint and the like on the part of God, get ruled out and the question contradicts itself, since the necessity for the world to have a cause outside it is a hypothesis characteristic of the three-dimensional way of human thinking in which it is shackled.
On the Question of Pain and Suffering to Created Beings
The idea of pleasure and pain is a product of what may be called parochial thinking, without the consciousness of any reference which one may have with other factors that range beyond human perception. Pleasure and pain do not exist as if they are things hanging somewhere in space. These are names given to conditions of experience undergone by a particular degree of consciousness when the atmosphere which it regards as existing external to itself in space and time is either reconcilable or irreconcilable with its present condition. It is a pain for a human being to be dipped within the bowels of the cold waters of the Ganga, but a delight to the fish swimming within it pleasantly. Man never thinks the same thought throughout his life. Today's pleasure is tomorrow's sorrow. These facts are not unknown in human history. Apart from the psychological considerations, there is a scientific and a metaphysical error in thinking that pleasure and pain are existent in objects, as it were. A cool breeze in summer is pleasant, and the same thing is unpleasant in winter. A fourth or fifth cup of pleasant milk causes nausea. The rich people of the world know the sorrow caused by their wealth. People who crave for having children know the troubles of family life and social tension. Why go so far? Since pleasure and pain are conditions of particular circumstances of individualities in relation to reality outside, any excessive harping on the tune of life's sufferings may require a more impartial adjudication.
The horror of the big fish swallowing the smaller ones and the apparent unjustifiability behind the survival of the strongest, or, we may say, the fittest, is inseparable from the basic psychological defect which Alfred North Whitehead calls "the fallacy of misplaced concreteness," which means to say that human judgements of what look like local events and occurrences do not take into consideration their vaster relationship to the universe as a whole, such that every event is a universal event, and it is not the big fish that swallows the smaller one but the evolutionary impulse of the cosmos adjusting itself in terms of its internal components for a purpose that transcends an existing situation. Evolution is not a pain, even as no one regards as pain the growth of a child into a mature genius. The whole difficulty arises because of the thought that God is outside the universe and handles things as a carpenter operates on his tools. This unfortunate weakness of human thought raises the frightful bogey of questions which have as much reality and meaning as its own intrinsic worth. Evolution is not for anybody's pain or pleasure, because, there is no "anybody" outside the process of evolution. The Infinite seems to proceed from the Infinite, and return to the Infinite, all which can suggest nothing more than that the Infinite is just what it is.
The Process of Action and Reaction
If we insist on finding a reason behind the sufferings of life, whatever be their nature and detail, it has to be accepted that the justice of the universe which is a single organism cannot permit illogical and, therefore, unjust occurrences within its internal constitution. Life in the world is seen to be a little complicated by the operation of the law of action and reaction, called Karma. This is a principle according to which every action produces an effect with an equal force. Bondage is considered to be the reaction produced by actions which defy the fact of the unitary structure of the cosmos of which all individuals are inseparable parts. This principle of reaction to action arises only when this intrinsic inseparable connection of the individual with the cosmos is forgotten and the former indulges in attitudes or actions with the false notion that it is an independent actor or doer, consequently inviting the nemesis of reaction. The universe is the shadow cast by the wishes of its contents, and it is what these wishes are and what they sweep away from infinite existence with the winds of the forces moving towards their fulfilment. Since the acceptance of the fact of creation implies the fact of pleasure and pain in life and suggests a cause behind the effect, it would follow that there are endless causes behind endless effects moving in a cyclic fashion, which system operating in the time-bound world is called by different names by the religions of the world; and the Indian tradition calculates this cycle of an endless revolution by its concept of the Yugas or temporal ages known as Krita, Treta, Dvapara and Kali, in the descending order of knowledge and virtue. All this would explain why no man tied down to the present cycle alone can know why anyone has any particular experience, pleasurable or miserable, since the causes behind effects visible in the present cycle can originate from earlier cycles, and therefore it cannot be said that there is an undeserved pleasure or an undeserved suffering. Nothing can come from nothing, is indeed sound logic.
The Evolution of Life
There is no precise saying as to when a lower species evolves into the higher one. Since personal agency in action cannot be attributed to sub-human species, all evolution below the human level is supposed to be a spontaneous fulfilment of the vast purpose of Nature. The progress of the sub-human organism, or the rise from the lower condition of the soul to the higher, is considered automatic as a spontaneous action of the universal Nature in the case of all beings who are free from the egoism of personal agency in action. Personal effort comes into relief only at the human level wherein consciousness becomes self-consciousness, an individual affirmative urge, whereby this centre of affirmation is severed from the supporting hand of the universal Nature and self-effort on the part of one's own individual self becomes the well-known drudgery of life. The animal nature when it rises to the human level will, in the natural course of things, take higher births, gradually, provided right thinking harmonious with the total universe motivates its thought and action. The sufferings of animals, as with sufferings of human beings, in whatever way they be called, are already touched upon in their essential causational circumstances, in what we have considered already above in a different context. There can be no devil engaged in inflicting sorrows on anyone, even as there cannot be a world external to the omnipresent reality. Human thought has to learn a little of the art of the vision of things by superhuman insight before whose glowing radiance the world will shed its cloak of all darkness and misfortune.
The Vedas, Epics and Puranas
The Epics and Puranas are there only to dilate upon the secret hints and hidden truths embedded in the body of the Vedas. The gospel of the Vedas does not contradict the Epics and the Puranas. People who speak of a difference herein are mostly those who have not made a thorough and entire study of either the Vedas or the Epics and Puranas in their true spirit. The hells and heavens of the Puranas are gradations or degrees of expression of reality, all which is corroborated in the Vedas in a more concise and pithy form. The meaning of the Vedas is too hard for the ordinary mind to grasp, and a mere grammatical or linguistic translation of them cannot be said to convey their real message. The Vedas are supposed to be interpreted from the subjective, the objective as well as the universal points of view and not merely as bodies of words which have just a dictionary meaning. The Epics and Puranas are elaborations of truths which are already embodied in the Vedas in a loftier form.
The Question of God and Satan
What is known as Satan may be regarded as the centrifugal urge of the cosmos, an impulse to move away from the centre to the periphery or the outer circumference as space, time and objects. God is the Centre of the Universe, and everything that is divine, the opposite of the so-called Satan, is the centripetal urge, an impulse that directs itself towards the Centre of the Universe. Neither God nor Satan can be viewed anthropomorphically. But man has an inveterate habit of converting God into a widespread man and visualise Satan as the quintessence of wickedness, again viewed as some person existing somewhere. Nothing of the kind is called for in the broad daylight of clearer thinking. Our earlier analyses above would be sufficient clarification of whatever one may think God is, Satan is, or their supposed relationship is. We are not puppets at the mercy of anyone, as we are integral parts of the universe; call this, if you would like, man's relationship to God. With this awakening, the idea of the devil, or Satan, vanishes into thin air.
Man's Duty
The duty of man, then, is an inward collaboration with the structure of all things, the law of the Universe; we may say the Universe is more a large area of a law operating than a thing, an object or substance. The terms Sattva, Rajas and Tamas imply the threefold condition of the constituents of the Universe, and the injunction to cultivate a tendency to Sattva is the highlighting of a requirement on the part of everyone to move towards larger dimensions of universality, that is to say, cosmical being. This naturally implies a rise from Tamas, or unconscious motivation and existence, and Rajas which is the impulse of consciousness to diversification and distraction of attention in a multitude of ways. Sattva is the integrated perspicacity of the total reality, or the wholeness of being, which is the final aim of all things and towards which it is that everyone, and everything, anywhere, seems to be eagerly moving inwardly as well as outwardly.


text:
Solo Exhibition by Camelia Pham
13 – 28 May 2017, 9 am – 6 pm
Creative Artillery
27/52 Tô Ngọc Vân str, Hanoi (Hanoi Rock City courtyard)
From the organizer:
"This is Camelia Pham speaking. She is an awesome illustrator who situated in Italy for her obsession with gelato.
Currently, she's a graphic design student in the Academy of Fine Art in Frosinone, a town near Rome.
Personally, drawing for her is a way to escape the absurdity of the outside world, by creating another senseless world but more twisted and bended to underline and reflect all of her emotions and thoughts about the events in her life, yeah she's egocentric as hell.
But when you are the protagonist of your own story, the only thing you know best, what can you do?"
Camelia's first solo exhibition in Hanoi will be open from 13 – 28 May.
* Artworks, postcard and customized prints will be available for sale.
Follow updates on event page


text:
Por favor intenta utilizar Google Translator para traducir el contenido a tu idioma preferido.
Effective Date: May 25, 2018
Welcome to Rouvy.com and related applications Rouvy Desktop, Mobile and Tablet application, PowerTap Mobile, Magura Mobile, O-Synce Mobile, Bulls Mobile – (collectively "Rouvy," "We," "Us," or "Our").
We respect your right to privacy. Your ability to make informed choices about the use of your information is important to us. We want to make sure that you understand the type of information we collect about you, how it is used and the safeguards we use to protect it. This Privacy Policy explains our policy regarding the collection, use, disclosure and protection of personal information you share with us.
Before you get to the details, here are a few of our fundamental privacy principles:* Information you upload or post to Rouvy may be seen by others depending on your privacy settings.
Please also read the Terms of Use which sets out the terms governing Rouvy and the Rouvy Legal Cookie Statement.
VirtualTraining s.r.o.
Namesti Svobody 13
385 01 Vimperk
Czech Republic
The type of information that we collect and retain depends upon your interaction with Rouvy. Here is a short overview of the two main types of interactions.
Information You Give Us. We collect the personally identifiable information you provide to us:
Create a user account, place an order, register a product (information we collect is necessary to complete the account registration and transaction and so that we can ensure you Rouvy products and services):* Username (unique identification)
You have the final decision on whether to proceed with any activity that requests personal information. However, if you do not wish to provide information needed for a transaction, you may not be able to complete it.
Information Rouvy Collects. When you interact with Rouvy we may maintain a record of the following types of information:
Cookies are small pieces of unique information, sent by a website, that are stored on your computer's hard drive by your web browser. Cookies enable a website to tailor information presented to you based on your browsing preferences. Rouvy uses cookies to personalize your Rouvy, when you seek service & support or to remember you when you register for products or services.
Rouvy may also use cookies to track your visit to Rouvy site. While our web servers may automatically log your IP address, the type of information we collect pertains to how you navigate, browse and purchase. This information is not personally identifiable, and we do not correlate this information with your personal information.
However, rejecting cookies may affect your ability to use some of the products and/or services of Rouvy.
The personal information we collect is generally used to process your requests and transactions, to provide you with high quality service, to tell you about opportunities we think will be of interest to you, to customize your Rouvy experience and to understand your needs so that we may provide you with the most suitable products and services. For example, we may use your personal information to help us:
Rouvy does not sell or rent your personally identifiable information to third parties. Under certain circumstances and from time to time, Rouvy may share your personally identifiable information with third parties as set forth below. In such circumstances, we provide only the information necessary to perform the function or to provide the service for which it has been shared. These third parties are required to keep the information confidential and are not permitted to use the personal information provided by us for any purpose, except as authorized by Rouvy.
Rouvy may share your information with third parties such as:
By providing us with your personal information when registering to Rouvy or when you obtain or use any of our products or services, you consent to the collection, use and disclosure by Rouvy of your personal information as provided in this Privacy Policy.
Your consent includes the retention of personal information that is collected through Rouvy, including your personal information that you submit through a registration process, for as long as you are a user of Rouvy' products and services, and for a reasonable time thereafter, unless and until you withdraw your consent. Information associated with your account will generally be kept until it is no longer necessary to provide Rouvy or until you ask us to delete it or your account is deleted whichever comes first.
Information about you that is no longer necessary and relevant to provide our Services may be de-identified and aggregated with other non-personal data to provide insights which are commercially valuable to Rouvy, such as statistics of the use of Rouvy. This information will be de-associated with your name and other identifiers.
Rouvy is committed to maintaining the security of information under our control. We have taken security measures, consistent with industry practices, to protect your personal information. To try to prevent unauthorized access, maintain data accuracy and ensure correct use of information, we have put in place industry-accepted physical, technical and administrative practices to safeguard and secure the information we collect.
Where we have given you (or where you have chosen) a password which enables you to access certain parts of Rouvy, you are responsible for keeping this password confidential. To protect the confidentiality of this category of personal information, you must keep your password confidential and not disclose it to any other person.
Unfortunately, no transmission of information over the internet can be guaranteed to be completely secure. Although we will do our best to protect your personal information, we cannot guarantee the security of any information you transmit to Rouvy from your PC or the Internet Service Provider, and any transmission is at your own risk. Once we have received your information, we will use strict procedures and security features to ensure its security on our system and to try to prevent unauthorized access.
All information you provide to us is stored on our secure servers. All information is transmitted using secure socket layer (SSL) encryption. Rouvy engages a company that is an industry leader in online security and Services verification to strengthen the security of Rouvy's Services. Rouvy are registered with site identification authorities so that your browser can confirm Rouvy's identity before any personally identifiable information is sent. In addition, Rouvy's secure servers protect this information using advanced firewall technology. We restrict access to personal information about you to those Rouvy employees who need to know the information for the purposes described in this Privacy Policy.
To help ensure that these measures are effective in preventing unauthorized access to your private information, you should be aware of the security features available to you through your browser. You should use a security-enabled browser to submit your credit card information and other personal information at Rouvy. Please note that if you do not use a SSL-capable browser, you are at risk for having data intercepted.
Rouvy offers several features and settings to help you manage your privacy and how you share your activities. The most important is the level of privacy in your privacy settings page. There you can set up the level of publicity of your data. Subject to your privacy settings, your information and content may be publicly accessible.
Rouvy offers various ways to manage the notifications you receive. You can choose to stop receiving certain emails and notifications by indicating your preference at Rouvy Portal Settings. You may also unsubscribe by following the instructions contained at the bottom of each type of email. Any administrative or service-related emails (to confirm a purchase, or an update to this Privacy Policy or the Terms of Use, etc.) generally do not offer an option to unsubscribe as they are necessary to provide Rouvy you requested.
You may correct, amend or update profile or account information that is inaccurate at any time by adjusting that information in your account settings.
You may request that your account is deleted by visiting the user profile settings on Rouvy.
Access and Porting
You can access much of your information by logging into your account. To download a copy of your data contact us via e-mail email@example.com.
Rectify, Restrict, Limit, Delete
You can delete much of your information by logging into your account. If you are unable to do this, please contact us at https://support.rouvy.com. Rouvy will generally respond to your request within 15-20 business days.
If you have provided personal information to Rouvy you may ask us to advise you of the scope of information Rouvy processes about you. You should wish to raise a concern about our use of your information. Please contact as via e-mail email@example.com.
Furthermore, we believe that the individual is invaluable in ensuring that data is complete and accurate. We will provide you with access to personally identifiable information you provide through Rouvy for as long as we maintain that information in a readily accessible format. Similarly, we permit and encourage you to correct inaccuracies in the information you submit to us through Rouvy. If you believe that Rouvy does not have your current personal information, you can update it by visiting the user profile settings on Rouvy.
Periodically, Rouvy may contain links to and from websites of our business partners, distributors, resellers, advertisers or other third parties. If you follow a link to any of these websites, please note that these websites have their own privacy policies which you should read before you submit any personal data to these websites. We disclaim any liability for the data processing activities of our business partners, distributors and resellers, all of which act as independent data processing controllers.
We also link to co-branded websites that are maintained by Rouvy and one or more of our business partners. An example of a co-branded website is the Rouvy e-shop. When you submit information to one of our co-branded websites, you may be submitting it to both Rouvy and our business partners. Please note that the privacy policies of these co-branded websites may differ from this Privacy Policy. We encourage you to read the privacy policies on any co-branded website to which you link, and we disclaim any liability for the data processing activities of our business partners which act as independent data processing controllers.
Please remember that information you submit in a discussion group or forum at Rouvy will be deemed public information and is not confidential. There is a risk in such communication venues that various information and data can be collected and used by others. Please be careful and responsible when you are on-line.
Rouvy reserves the right to modify this Privacy Policy at any time. Please review it occasionally. If Rouvy makes changes to this Privacy Policy, the updated Privacy Policy will be posted on the Services in a timely manner and, if we make material changes, we will provide a prominent notice. If you object to any of the changes to this Privacy Policy, you should stop using the Services and delete your Rouvy account.
This Privacy Policy was originally prepared in the Czech language. Although Rouvy may provide one or more translations for your convenience, the Czech version will control in the case of any conflict or discrepancy.
If you have any questions or suggestions regarding our Privacy Policy, please contacts us at firstname.lastname@example.com


text:
Our Partners
Learn more about our partners in education.
Our Partners
The Brett and Kelly Coleman Foundation
The Brett and Kelly Coleman Foundation, a non-profit organization based in Northern Nevada, is focused on assisting children in need. The Brett and Kelly Coleman Foundation has been a huge support system and an amazing collaborating organization to help support local youth through education.
Fit Learning
In 1998, several graduate students in the behavior analysis program at the University of Nevada, Reno founded Fit Learning in a broom closet. Originally, Center for Advanced Learning, its founders were committed to applying the science of learning for the transformation of mainstream, academic difficulties. Two decades later, Fit Learning's impact now reaches students across the globe. We are all joined together inside our noble cause of transforming every child who walks through our doors – regardless of age, disability, challenge, or label – such that they acquire the kinds of cognitive and academic skills that will enable them to go forward and make a difference in their own lives. And now, through Empower Youth, the same opportunities can now be provided to youth who would otherwise be unable to receive the life-changing education provided by the Fit Learning method.
Big Brothers Big Sisters
For more than 100 years, Big Brothers Big Sisters has operated under the belief that inherent in every child is the ability to succeed and thrive in life. As the nation's largest donor- and volunteer-supported mentoring network, Big Brothers Big Sisters makes meaningful, monitored matches between adult volunteers (Bigs) and children (Littles), ages 6 through 18, in communities across the country. They develop positive relationships that have a direct and lasting effect on the lives of young people.
Women and Children's Center of the Sierra
The Women and Children's Center of the Sierra (WACCS) provides services to support women as they work to move out of poverty and improve their lives. Their comprehensive approach includes ESL and GED (HiSet) education, job search and preparation, a free diaper bank, crisis intervention, and information and referrals for any other community service a woman may need to move forward in her life.
Become a Partner
Connect with us to learn how your organization can partner with us to provide a life-changing educational opportunity to at-risk youth.


text:
Amazon Redshift (8)
- In-Warehouse Machine Learning and the Modern Data Science Stack - Jun 24, 2021.
As your organization matures its data science portfolio and capabilities, establishing a modern data stack is vital to enabling such growth. Here, we overview various in-data warehouse machine learning services, and discuss each of their benefits and requirements.
- BigQuery vs Redshift: Pricing Strategy - Jul 17, 2018.
In this blog post, we're going to break down BigQuery vs Redshift pricing structures and see how they work in detail.
- Choosing Between Modern Data Warehouses - Jun 28, 2018.
Most of the modern data warehouse solutions are designed to work with raw data. It allows to re-transform data on the fly without a need to re-ingest your data stored in a warehouse.
- Modernize your data infrastructure with Looker + AWS - Apr 25, 2018.
Learn how you can improve performance and optimize resources using Looker + AWS and Amazon Redshift with Looker extensive pre-built analytics models for AWS data. As a bonus, we will give 1K credit towards AWS data warehouse.
- 3 Levers for Getting the Most Out of Amazon Redshift and AWS, Aug 29 - Aug 22, 2017.
Learn how to optimize your Amazon Redshift instance, critical metrics for smart investments in cloud infrastructure, and best practices to scale your AWS investment.
- Webinar: Driving Data Democracy: Hadoop and Redshift, Mar 16 - Mar 4, 2016.
The Hadoop ecosystem has improved markedly over the past few years. MPP databases allow analytics teams to easily query massive structured data sets. Learn how these pipelines work on March 16.
- Which Database is best for an Analyst? - Dec 10, 2015.
Database comparisons usually look at architecture, cost, scalability, and speed, but rarely address the other key factor: how hard is writing queries for these databases? We examine which of the top 8 databases are easiest to use.
- Getting Started with Amazon Redshift - Sep 27, 2013.
Amazon Redshift is a fast, fully managed, petabyte-scale data warehouse service. This step-by-step, practical guide to the world of Redshift teaches you how to load, manage, and query data on Redshift.