Don’t panic.

祝日 / Permanent Vacation
he wasn't even looking at me and he found me
noise dept.
almost home
Three Goblin Art
trying on a metaphor
todays bird
dirt enthusiast
🪼
cherry valley forever
Claire Keane
ojovivo
Peter Solarz
Keni

Kiana Khansmith

izzy's playlists!

blake kathryn
No title available
Jules of Nature
tumblr dot com

seen from United States
seen from United States
seen from United States

seen from United States
seen from Canada
seen from United States
seen from United States

seen from India

seen from Türkiye

seen from United Kingdom
seen from United States
seen from United States

seen from Lithuania
seen from Netherlands
seen from United States
seen from Canada
seen from United States
seen from United Kingdom

seen from Canada
seen from United States
@bi6545
Don’t panic.
The release of data on the news-reading habits of 20 million Yahoo users could help advance recommendation algorithms.
Vista esquemática del método de Kimball
Jerarquía de los sistemas de información según el modelo de pirámide.
In order to build a great data science practice, you need great data engineers. Here's how to hire them.
Un artículo que algunas ideas en torno a los llamados científicos de datos, la cultura que los rodea y el como escoger entre ellos en función del perfil con que vienen.
No está de más leer un poco de estos temas.
Naturalmente que todos en todas las materias que se dictan, desean y requieren del pensamiento critico. Sin embargo, enseñar como pensar correctamente no es parte de ninguna materia en concreto... aunque no por eso debemos limitarnos a la hora de plantear un posible curso sobre el tema.
En el artículo, se explora el engranaje de cuatro puntos para enseñar a pensar críticamente. Estos son:
Argumentación
Lógica
Psicología
Filosofía de la Ciencia
Vale la pena dedicar un tiempo a la investigación de estos puntos, pues el ser crítico, analítico y capaz de razonar correctamente, debiera ser como los deportes: algo que requiere talento, pero que se puede afinar con entrenamiento apropiado.
Are you good at math? Like, really good at math? Do you also know Python and, oh yeah, have deep knowledge of a particular industry?
On the off chance that you possess this agglomeration of skills, you might have what it takes to be a data scientist. If so, these are good times. LinkedIn just voted "statistical analysis and data mining" the top skill that got people hired in 2014.
Glassdoor reports that the average salary for a data scientist is $118,709 versus $64,537 for a programmer. A McKinsey study predicts that by 2018, the U.S. could face a shortage of 140,000 to 190,000 "people with deep analytic skills" as well as 1.5 million "managers and analysts with the know-how to use the analysis of big data to make effective decisions."
In this white paper, we describe the rapidly evolving landscape for designing an enterprise data warehouse (EDW) to support business analytics in the era of "big data.” We describe the scope and challenges of building and evolving a very stable and successful EDW architecture to meet new business requirements. These include extreme integration, semi- and un-structured data sources, petabytes of behavioral and image data accessed through MapReduce/Hadoop as well as massively parallel relational databases, and then structuring the EDW to support advanced analytics. This paper provides detailed guidance for designing and administering the necessary processes for deployment. This white paper has been written in response to a lack of specific guidance in the industry as to how the EDW needs to respond to the big data analytics challenge, and what necessary design elements are needed to support these new requirements.
Excelente documento que analiza el llamado big data en el contexto tradicional de Kimball: Enterprise Data Warehouse. El documento toca puntos como Hadoop y MapReduce por lo que su lectura es recomendable.
The Kimball Group is a focused team of senior consultants specializing in the design of effective data warehouses to deliver enhanced business intelligence. Through consulting, education, and writing, we help organizations leverage the information that’s collected by their operational systems to make better business decisions. We pioneered this industry. Although what we do is no longer unique, how we go about doing it most definitely is.
Averaging over 25 years of experience in the field, our vendor-independent team has the know-how to relate to a broad range of client situations, and the insight to react to the elements that make each distinct. Plus the aptitude and attitude to look out for our clients’ best interests at all times. We wrote the best-selling books on dimensional modeling and DW/BI methodology. And every day, we surround our clients with more ways to make smarter decisions.
That’s why we’re the industry leader in DW/BI methodology, design and education, especially when it comes to dimensional modeling. Although many of our competitors are larger, none are more experienced or relentlessly practical.
Ralf Kimball es el papá de los helados del mundo de los datawarehouse, incluso alega haber sido el inventor del concepto de modelado multidimensional... y por esto es justo que tenga un boyante negocio montado alrededor de esto. ¡Bien por él!
Ejemplo de diagrama de Entidad/Relación, aquí, ilustrando el llamado modelo físico de la base de datos por cuanto se observan las estructuras que van a tener las tablas en todo detalle, incluyendo claves primarias.
Entity Relationship Diagrams (ERDs) illustrate the logical structure of databases.
El tutorial de SmartDraw sobre diagramas E/R es un buen punto de arranque para familiarizarse con los mismos o volver a agarrar el ritmo si lo que nos ha pasado es un tema de olvido...
La chica creadora de este diagrama, cuenta que lo hizo exclusivamente con un touchpad (una de esas plaquitas que hacen las veces de mouse en las laptops) A la luz de mis propios intentos de dibujar con uno, puedo asegurar que lo que ella ha hecho no es nada fácil.
Esto es un flowchart bien hecho. Divertido, se deja entender, y por qué no, quizás ayude a alguien a llegar al espacio.
Sin embargo, reflexionando aquí entre nos, veo que ese diagrama no es conforme a ninguna regla formal.
Learn about the differences between modern and traditional flowcharts and more in this article from the SmartDraw Flowchart site. The Flowchart site contains useful information about this type of diagram.
Esta es una excelente guía para crear diagramas de flujo (flowchart en inglés). Define apropiadamente cada simbolo y lo que es más importante, discute en una forma entendible el uso de un diagrama de flujo en diversas situaciones reales.
Quizás debí buscar una guía así antes de hacer el desastre de mi post anterior :-/
Jugando un poco con LucidChart, he creado el diagrama aquí visto. Pretende ilustrar un poco como es el proceso de obtener calificación en una materia.
Quedo pendiente de chequear si la sintaxis del diagrama es correcta, pues LucidChart es una herramienta de dibujo y por lo tanto, cualquier cosa es aceptada, sin importar que haga sentido o no.
If you sometimes need to create quick diagrams for work, Gliffy is a great tool to bookmark.
Relational databases have been in use for a long time. They became popular thanks to management systems that implement the relational model extremely well, which has proven to be a great way to work with data [especially for mission-critical applications].
In this DigitalOcean article, we are going to try to understand the core differences of some of the most commonly used and popular relational database management systems (RDBMS). We will explore their fundamental differences in terms of features and functionality, how they work, and when one excels over the other in order to help developers with choosing a RDBMS.
Sin quejas con esta comparativa. Orientada hacia el mundo relacional, presenta a los tres productos que revisa de una maneja objetiva. Sin embargo, no ofrece conclusiones propias, dejando al lector en el deber de decidir por si mismo.