Web engineeringFunctional programmingHigh-end audio

Srdjan Strbanovic

djidja8

A quiet systems thinker who built an archive where modern web craft, functional ideas and high-fidelity sound met.

8.1Kposts
5topics
1languages
The selector

A quiet archivist of practical systems

Srdjan Strbanovic, visible online as djidja8, built a substantial English-language Scoop.it archive from 2011 onward. The analysed body of work is now dormant, but it preserves a clear intellectual profile: a developer-minded selector drawn to modern web architecture, functional programming, backend systems and carefully chosen audio gear.

The web as an engineering system

Srdjan’s software archive followed the web’s shift from documents to applications. React, service workers, isomorphic JavaScript, Node APIs and microservices appeared as parts of one broader concern: how modern systems are assembled and maintained.

Abstraction with practical teeth

The Functional programming and Software Development Hub topics showed a taste for abstraction with consequences. F#, Scala, Clojure, parser combinators, DSLs, Kafka, Docker and unikernels were gathered as tools for clearer models and stronger architectures.

An audiophile counterpoint

TopAudio widened the portrait. Alongside code and infrastructure, Srdjan followed cost-effective high-end audio: DACs, amps, speakers, music servers and headphones, often with an ear for compact or all-in-one systems that promised serious sound without pure extravagance.

What defines this archive

A large technical memory

Across the analysed topics, Srdjan built an archive of 8,130 posts. The scale suggests sustained scanning rather than occasional bookmarking, with dense coverage of web apps, functional programming, backend infrastructure, Node APIs and audio gear.

Selection over commentary

The voice was mostly quiet, but the choices were specific. Tutorials, conference talks, engineering blogs, project pages and documentation dominated, giving the archive a practical rhythm and leaving the selected material to speak for itself.

A builder’s bias

The strongest software topics repeatedly returned to implementation: tests, frameworks, distributed systems, API security, service workers, Docker, unikernels, streams and design patterns. The archive favored tools and methods that working developers could put to use.

Reach across communities

The profile drew meaningful attention, with more than 215,000 views and over 108,000 unique visitors across all topics. The nodeJS and Web APIs and TopAudio topics were especially visible historically, showing reach beyond a narrow programming niche.

Topics

Deep dives

A front-end archive from the moment the web became an app platform

The Web Apps topic captured a particular moment in the web platform’s evolution, when the browser was becoming an application runtime rather than a page viewer. The selections followed installable web apps, service workers, fast-loading HTML, modular interfaces and the early promise of open web distribution.

The strongest editorial pattern was architectural: pages gave way to modules, JavaScript moved across client and server, and UI engineering became a systems problem. React testing, isomorphic JavaScript and functional reactive patterns appeared not as hype, but as practical tools for building sturdier applications.

Because the topic stopped in 2015, it now reads like a snapshot of the transition into modern front-end practice. Its value is historical as much as technical: a map of the ideas that hardened into the web-development mainstream.

Functional programming as a practical, polyglot toolkit

The Functional programming topic treated FP as a working programmer’s discipline, not an ivory-tower exercise. It gathered introductions, tutorials and talks across F#, Scala, Clojure, Elm, Elixir, JavaScript and TypeScript, with a clear bias toward code that could be used in real projects.

The archive often crossed language borders to compare habits of thought: an F# developer moving into Scala, Elm applied by practitioners, Clojure explained for newcomers, JavaScript made more functional through memoization and currying. The through-line was transfer: patterns mattered more than brand loyalty.

This topic also showed Srdjan’s taste for technique. Parser combinators, pure functions, state pipelines and functional architecture appeared beside beginner lessons, giving the collection a layered feel: approachable at the surface, demanding underneath.

Node and APIs as craft, not just code

The nodeJS and Web APIs topic was a hands-on notebook for building networked software. Its emphasis fell on REST APIs, Node frameworks, MongoDB integration, package practices, streams, debugging, testing and deployment details.

Security and operations were never far away. Rate limiting, API lifecycle management, common developer mistakes and API security attacks made the topic more than a tutorial shelf; it followed the work needed to keep services usable and defensible.

The inclusion of REST fundamentals alongside Node-specific practice gave the archive breadth. It linked day-to-day implementation to larger questions of API design, versioning and hypermedia, which is why the topic drew strong historical attention.

Selected posts