explaingit

shekhargulati/52-technologies-in-2016

7,302JavaScriptAudience · developerComplexity · 1/5Setup · easy

TLDR

A developer's 2016 challenge to learn and document one new technology per week, resulting in 42 written tutorials with working code samples spanning web frameworks, build tools, NLP, databases, and cloud services.

Mindmap

mindmap
  root((repo))
    What it is
      42 weekly tutorials
      Code plus write-up
      Series ended 2016
    Topics Covered
      Web frameworks
      Build tools
      NLP and data
      Cloud services
    Languages
      Scala and JVM
      Python
      Go
    How to Use
      Browse numbered folders
      Read README per entry
      Run sample code
Click or tap to explore — scroll the page freely

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

Things people build with this

USE CASE 1

Browse working code samples and write-ups to quickly get a feel for an unfamiliar framework like Finatra or Slick.

USE CASE 2

Use the tutorials as a reference when evaluating JVM ecosystem tools for a new project.

USE CASE 3

Follow the numbered series as a structured self-study curriculum covering tools across the software development landscape.

Tech stack

JavaScriptScalaPythonGoJVMsbtHugo

Getting it running

Difficulty · easy Time to first run · 5min

No build step needed, browse tutorial folders and read the included READMEs directly.

No license information was mentioned in the explanation.

In plain English

This repository is a collection of 42 written tutorials published by a developer who set out to learn one new technology every week throughout 2016. The goal was to pick a tool or technology, build a small working application with it, and write up the experience as a blog post. The series ran weekly from January through most of the year before the author decided to stop at 42 entries rather than the originally planned 52. Each tutorial lives in its own numbered folder inside the repository and includes its own README with the full write-up and accompanying code. The topics covered are broad and tend toward the Scala and JVM ecosystem, though the series branches into Python, Go, and cloud services as well. Entries cover REST API frameworks, build tools, natural language processing, database libraries, load testing, static site generators, data streaming platforms, image recognition APIs, and automation tools, among others. Specific tools covered in the first batch include Twitter's Finatra web framework, the sbt build tool, Stanford CoreNLP for sentiment analysis, the Slick database library, Hugo for static websites, CoreOS for server infrastructure, Google's Cloud Vision API, and the Gatling load testing tool. The series is organized as a numbered list in the main README, with each item linking to the relevant folder and tutorial. The author explicitly notes the series has ended and no new posts will be added. The code samples and write-ups remain available as a learning reference. External contributions were welcome during the active period. The repository accepted corrections, additions, and guest posts through pull requests. The topics were chosen to give the author broad exposure to tools across the software development landscape rather than deep expertise in any single area.

Copy-paste prompts

Prompt 1
I want to learn Finatra, the Scala web framework. Show me a minimal REST API example based on the shekhargulati/52-technologies-in-2016 tutorial style.
Prompt 2
Walk me through what Stanford CoreNLP does for sentiment analysis and give me a runnable example in Scala or Python, similar to the week-4 entry in shekhargulati/52-technologies-in-2016.
Prompt 3
I cloned shekhargulati/52-technologies-in-2016 and want to run the Gatling load-testing tutorial. List the steps and prerequisites I need to get it working.
Prompt 4
Compare the Hugo static-site-generator setup in shekhargulati/52-technologies-in-2016 with a modern equivalent, what would I do differently today?
Open on GitHub → Explain another repo

← shekhargulati on gitmyhub — every repo by this author, as a profile.

Verify against the repo before relying on details.