Weekend vs Weekends

Posted by in Engineering Management, Startup

Since the start of my career I had got weekends for leisure time, but being in a startup I used to end up working on most of the Saturdays. So when I got an opportunity to work at TinyOwl which was 6 days a week, I was completely fine with it, because I thought that I anyway do work on Saturdays, what’s the harm if it’s officially open. 3 Months post joining TinyOwl, I was ...continue reading.

0

7 level security classification model

Posted by in Devops, Technology

When you start building your infrastructure, your servers cross communicate with each other which brings in lot of security risk. To reduce this risk you should have some way to organize/classify your servers. The idea behind this model is to define how critical is the server from the security point of view. Hence, this level model works very well.

Server Class Level Description Example
Public + Subnets behind Level 0 Any server in our infrastructure
...continue reading.
1

Building peaceful and scalable infrastructure

Posted by in Devops, Server Side, Startup, Technology

This is the first of the series of blog post on building peaceful and scalable infrastructure.

Every DevOps dream is to have a stable infrastructure so that he/she can sleep peacefully without having to worry about systems going offline. From my experience if you cover up following areas in your infrastructure. You can sleep peacefully.

1. Design/Architecture

The better you know your components in your infrastructure, the better you can design it. There are multiple ...continue reading.

1

Separation of concern, just not in code

Posted by in Engineering Management, Other, Startup, Technology, Thought

`Concerns` is a term used in computer science for scoping out the different behavior of the code and `Separation of concern` is a design principle for separating a computer program into distinct sections. I like this philosophy as this tells you how important it is to keep your code organized by separating concerns. The same applies to how you organize your engineering teams as well. There is a need for understanding, ...continue reading.

1