svemir

{
  "$schema": "https://raw.githubusercontent.com/jsonresume/resume-schema/v1.0.0/schema.json",
  "basics": {
    "name": "Svemir Brkic",
    "label": "Middle-aged Developer",
    "image": "",
    "email": "[email protected]",
    "phone": "",
    "url": "",
    "summary": "",

svemir

Code is clean if it can be understood easily – by everyone on the team. Clean code can be read and enhanced by a developer other than its original author. With understandability comes readability, changeability, extensibility and maintainability.

NOTE: Edited the original to remove a few points that are mostly Java-specific.

---

General rules

1. Follow standard conventions.
2. Keep it simple stupid. Simpler is always better. Reduce complexity as much as possible.
3. Boy scout rule. Leave the campground cleaner than you found it.
4. Always find root cause. Always look for the root cause of a problem.

svemir

A Common Crawl Experiment

Introduction

At my company, we are building infrastructure that enables us to perform computations involving large bodies of text data.

To get familiar with the tech involved, I started with a simple experiment: using [Common Crawl metadata corpus][1], count crawled URLs grouped by top level domain (TLD).