Recursos de programación de spectrum
Los beneficios del podcasting son muchos, también en el desarrollo de software. Primero quiero contarte la historia de Mario. Trabajaba en una empresa de creación de software, su pasión desde que le regalaron un Spectrum. Mario escuchaba las noticias en la radio. Siempre. Cuando iba y venía, cuando subía y bajaba. Quería estar bien informado. Cambiaba el dial, conocía la hora exacta de los programas que mejor le informaban. Durante años repitió este procedimiento. Ocurrió algo singular...
Software Developer & Architect at The Practical Developer Moisés is a Software Developer and Architect, and the author of the blog ThePracticalDeveloper.com and the book Learn Microservices with Spring Boot. He has been developing software since he was a kid, when his parents bought him a Sinclair Spectrum ZX and he started playing around with code. Since then, he has been involved in development, design, and architecture, and has worked in waterfall and agile organizations. His career started in Málaga, where he worked for big corporations and also small startups. He moved to Amsterdam in 2015 and is now working as Solutions Architect for a project based on Java and Spring Boot Microservices. Moisés has learned to be a pragmatic developer and architect and likes sharing his observations with others.
¿Conoces la Abadía del Crimen? La abadía es un juego de 8-bit (para spectrum y CPC) que se convirtió en el primer juego RPG en 3D (2.5D) en 1987. Este juego es una maravilla desde un punto de vista tecnológico: en solo menos de 120k es capaz de almacenar el sonido, las imágenes, toda la lógica del programa y los datos . ¿Conseguiste terminar el juego sin ayuda? No conozco a nadie que se lo haya pasado sin ayuda. Es uno de los juegos mas complicados que se han desarrollado, como unas 10x o 100x comparado con la venganza de montezuma de Atari. En la charla contaremos como diseñamos y construimos una AI capaz de jugar solo y aprender a completar el juego. https://www.koliseo.com/events/commit-2018/r4p/5630471824211968/agenda #/5734118109216768/5664208255451136
The Reactive Manifesto motivates the reactive tenets with large-scale systems that serve millions of users worldwide, needing exorbitant data size and bandwidth coupled with sub-second latencies. This presentation puts the spotlight on the other end of the spectrum: the systems that operate manufacturing processes and logistics are vital to a factory’s success. Data sizes and rates are easily manageable with today’s hardware, the top priority is absolute reliability. In these systems resilience is the prime motivator for loose coupling, elasticity is just a consequence. This presentation explains the architecture approach taken at Actyx and discusses the suitability of different patterns in this context, including some war stories.
In my career I've created several component libraries, and always found it challenging and rewarding at the same time. The engine we developed at WorkWave is the result of such attempts: it offers a great tradeoff between flexibility and ease of use. Styling with inline styles greatly simplifies the developer's work while the use of Aphrodite to output real classes enables the full spectrum of css features. I'll show you the choices we made, what problems have arisen while developing the components and how we solved them, hopefully helping you make better choices for your own libraries.
The CAP theorem points to unavoidable tradeoffs between consistency and availability when the network can partition. This decision heavily impacts system performance and cost. Current database design forces application developers to decide early in the design cycle, and once and for all, where they sit in this spectrum. At one extreme, strong consistency, as in Spanner or CockroachDB, requires frequent global coordination; restricting concurrency in this way greatly simplifies application development, but it reduces availability and increases latency. At the opposite extreme, systems such as Riak or Cassandra provide eventual consistency only: they never sacrifice availability, but application developers must write code to deal with all sorts of concurrency anomalies in order to prevent violation of application invariants. However, a system only needs to be consistent enough for the application to remain correct. We propose a unique middle ground, Just-Right Consistency (JRC), composed of various techniques that do not sacrifice availability, unless provably required for the application to execute correctly. We overview JRC, and present an open-source cloud-scale database built for it, Antidote. Antidote stores Conflict-Free Replicated Data Types (CRDTs) under Transactional Causal Consistency (TCC), the strongest model that does not compromise availability. Optionally, a transaction can be ACID, but Antidote keeps availability high by moving the required coordination outside the common path. Finally, we leverage research tools that help developers use ACID properties selectively, only when necessary for correctness.
This post appeared originally on Codesai’s Blog. Lately at Codesai we’ve been studying and applying the concept of connascence in our code and even have done an introductory talk about it. We’d like this post to be the first of a series of posts about connascence. 1. Origin.The concept of connascence is not new at all. Meilir Page-Jones introduced it in 1992 in his paper Comparing Techniques by Means of Encapsulation and Connascence. Later, he elaborated more on the idea of connascence in h...
Es curioso lo que está pasando con la afición a las retro-máquinas (léase AMSTRAD, COMMODORE, SPECTRUM, MSX, AMIGA, ATARI, etc., si me dejo alguna, perdón a los damnificados). Pese a lo que se podría pensar, es un mercado que sigue funcionando, con tiendas propias dedicadas a los coleccionistas, montañas de software clásico que se ha […] - por Diego Freniche