Git Part 2

Git: Part 2 - Some essential concepts

Featured Image “Essentials” by all black long johns is licensed under CC BY-NC-SA 2.0 In my last post, I introduced you to Git. We talked about its history briefly and how useful it is. In this one, let us explore some key terminology and concepts in Git. That way we have a common language to talk about Git. Remote This is what we generally call the copy of the repository that is maintained somewhere on the server. ...

October 3, 2020 · 5 min · 983 words · eakangk
Git

Git: Part 1 - An introduction

Background When I joined the small company that I currently work for, I was suprised at how little some of my coworkers knew about Git. The fact is, there was no reason to be suprised. I had taken my exposure with Git for granted due to the fact that I had been using it for a couple of years before I joined the firm. So as a good citizen, I prepared a little workshop to help others learn. ...

October 3, 2020 · 4 min · 698 words · eakangk
Invisible Lego

Software and invisibility

“The Invisible Man.” by Chaotic Good01 is licensed with CC BY-NC-SA 2.0. To view a copy of this license, visit https://creativecommons.org/licenses/by-nc-sa/2.0/ Keeping people informed Early in my career, I thought writing software is all about the outcome. Delivering something that works. I thought it didn’t matter how it was done. At the end of the sprint if you didn’t have a deliverable, it was a problem. This was true in companies which adopt a waterfall model of development. ...

September 16, 2020 · 3 min · 568 words · eakangk

Software design - Why?

The problem A lot of software engineers get into the industry and often end up starting to write code soon after they read the requirements’ specification. Sounds familiar? You might have done it too. Hard to admit? Can be. We are humans, after all. Jumping right into the coding process might be a great idea for a simple coding challenge, where the objective is to solve a problem in as little time as possible, with potentially very few lines of code. You just have that very specific goal. You don’t have worry about future enhancements for that solution, nor do you have to think about maintainability of that solution. Once solved, the code might have to run through a set of tests and pass the criteria of the question. Fantastic! And you might even get selected for the next round of interviews! Great! So why think about design when you start working on a real solution? ...

June 27, 2020 · 6 min · 1126 words · eakangk