What is this about? This post is one of many in a series of posts on Entity Framework Core. I have attempted to summarise what I learned while working with Entity Framework Core, from stackoverflow answers, to entity framework official docs to courses on pluralsight. In this journey, I found, the pluralsight course, Entity Framework Core: Getting Started by @julielerman most useful. As someone who spent the past few years primarily on managing people, I missed out a lot on the tech side of things. So these days, I have been playing catchup. And guess what? There is a lot to catchup! But as with any learning, it isn’t a sprint, it is a marathon and a pretty long one. ...

Background In the last 3 years or so, a lot of blog posts, youtube videos and tutorials came out about containerising applications. I had completely ignored this topic as there was no immediate use of containers that I could apply to my work. Those new to the software industry might not even have heard of containers. When I ask about it to those who brag about it, comparisons are made to Virtual machines but I never really got the details out from anyone, or you can say, I was not satisfied with explanations. ...

In my previous post we went through branching in git and commands that can be used to get changes from one branch to another. Oops! Let us explore some commands that will prove useful when we end up in tricky situations with Git. Reset Reset helps you undo a commit. You know those times when you commit too soon. Git offers you the following levels of control to when you attempt a reset. ...

Featured Image: “Forest” by fear-sAs is licensed under CC BY-NC-ND 3.0 In my previous post we looked at some basic git commands. Let us delve a little deeper into branches. Git Branch A branch in git is really just a pointer to a commit HEAD Head points to the current branch which in turn points to the latest commit in a branch. ...

Featured Image: please let me hold your hand by pippimuckel is licensed under CC BY-NC-ND 3.0 In the previous post we went through some concepts and terminology in git. Some basic git commands Create a repository Let us take a look at how we can create a local repository. git init What does it do? Initialises a repository for a project Creates a .git folder for your repository Used by Git to track changes that happen in that repository folder Git stores repository specific settings to that folder It tracks the latest change in a branch in that folder Also stores configuration for the repository in there A new repository, needs some configuration. Let us go ahead and configure it. ...

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. ...

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. ...

“01119 (304) 08-09-2009 Curley Cattle Transport - Mack Prime Mover 02-CCT + 3 trailers for cartage of cattle in a yard in Burke Development Road, Normanton, Queensland, Australia.” by express000 is licensed under CC BY-NC-SA 2.0 When starting this blog, I really hadn’t done enough research onto which platform to start blogging. I previously used to post some of my daily work problems on blogger. It was alright. But I hadn’t really written many interesting posts apart from posting some problems and solutions. Hopefully importing all those posts into this domain, will not only give them some visibility but also give my blog some content. ...

“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. ...

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? ...