Harrison Harnisch
A collection of posts by Harrison Harnisch
A collection of 3 posts
Over the last year, my role at Buffer has changed from an individual contributor to a technical leadership role. While the amount of time I spend coding and doing architecture hasn’t changed much, the way I go about the tasks has changed significantly. Instead of being focused on a project from start to finish, I move around projects as needed. Sometimes a team will get blocked on a tricky problem or need to make a decision that could impact oth
Over the last year my role at Buffer has changed from an individual contributor to a technical leadership role. While the amount of time I spend coding and doing architecture hasn’t changed much, the way I go about the tasks has changed significantly. Instead of being focused on a project from start to finish, I move around projects as needed. Sometimes a team will get blocked on a tricky problem or need to make a decision that could impact other teams or request technical mentor-ship to level u
On the surface the Buffer link counting service is pretty simple. Its job is to keep track of the number of times someone has created a Buffer post with a given url embedded into it. An Example Link { "url": "https://buffer.com", "created_at": "1480431305", "update_id": "123456", "profile_id": "654321" } Behind the scenes this is what powers the Buffer Button counts. As we’ve recently shared, Buffer is moving towards a Service Oriented Architecture and moving the links counting logic into it