Code Code Code Blog

Ry's Git Tutorial BOOK Review There are many good books about git but  Ry's Git Tutorial stands out as an amazing git tutorial book  I will describe below why: http://amzn.to/2pwEuFJ I want to stress out although I'm going to list below what this books talks about that is not the reason you should read this book.   The reason you should read this book is that it's crystal clear about git! it's just an amazing book, it's fun to read, and I truly get to understand git. It very clear, Ry's manages to bring us closer to git by making things really clear. Ry's makes an outstanding effort to bring us from knowing nothing about git to being an expert. The book starts with the real basics like Initializing the repository on an example website, staging files, exploring the repository. Then he moves on to  undoing changes  and he scans various ways you can undo your changes: viewing old revisions, tagging release, undo commit stages etc. Branches

Nick (a friend of mine :) loves developing software. But he doesn't really like meetings. His manager just asked him, hey, Nick, about this new feature you are going to develop, can you set up a meeting with a product, project, team leads, UI, backend teams just so we are all aligned? Now Nick needs to handle a meeting. It was all wired up in his head, but communication, as to say, is not his strongest skill, and he is afraid of a failure. Luckily, Nick got the dev.to summary mail with a blog post named "Scared of high-tech meetings? Follow this plan!", he has read it and this is how it went and what the plan he read was: Our plan: You are talented, you already know how you want the meeting to end. The plan is simple and involves one step. We are going to set up the meeting, however, we already know how we want it to end, our design should be approved. In order to achieve this plan end goal this is what Nick does: He creates a one-page document with the design and s

This is a great book for software engineers.  You don't have to be a consultant to benefit greatly from this book.   All you need to be is a software engineer.  By taking all the practices that the author mentions you will gain so much and you will increase vastly your chances of becoming a very successful software engineer.  The bits of advice is pure gold . The bits of pieces of advice I found to be so helpful: Get in the mood for being a consultant even if you are not one! Be a problem solver! How to be a successful meeting manager. How to organize yourself. How to estimate software programming time. How to handle complexity. How to handle office politics. How to communicate your work. How to be professional. What it takes to get you to make so much money. I highly recommend it if you are a software developers this might be the best soft skills book I have ever got myself into it's already helping me and I just finished it.

What is a PowerSet? Why is it called a PowerSet? Is it good or bad for us? Will I need it on my next Angular/Machine learning project? If we look at  Wikipedia for the definition of powerset  we see the below: In mathematics, the power set (or powerset) of any set S is the set of all subsets of S,... Cool, so that means if we have a set of a few item's {1, 2} then the power set would be the set of all sets, in the {1, 2} case it would be: { {1}, {2}, {1, 2}} Continuing to read the Wikipedia definition we see the guys there say: including the empty set and S itself You know what, those guys say we need to  add the empty set  let's just add it and move on: { {}, {1}, {2}, {1, 2}} So we added the empty set,  the definition is now happy.  :) All right I think now we are aligned with the definition, nice. Computer makes a power set Now the question is, how do we program the computer, to give us the PowerSet? The computer did not read the Wikipedia def