Wow this looks delicious...now to switch from chrome.

I've tried many times before but always ended up back with chrome.

Finally I can capture it from an angle that impresses!

I'd love to hear more!

@timlyrics mileage will vary but my story is one I am proud of. I'm self taught through and through. My late grandparents introduced me into this wonderful world in 1999 with a Compaq presario! I was hooked day one and have been breaking and making things ever since.

Well, in highschool I was all about music. I was a c student elsewhere. I would do the bare minimum, rarely study...not proud of that part. I was looking to go to a decent University for CSE... Procrastinated, took the ACT(30) but not the SAT and just didn't set myself up for success. I was in the Marine corps a few months later doing logistics.

When I left in 2013, I went straight to CSE at a decent state uni... Couldn't hack it.

In 2014 I fought for a job in our R&D department... I was writing cli and gui apps to simplify my (then) job. I got it!

That was the best day ever, receiving the offer letter...

I'd like to think I'm smart enough to skip the degree, as I'm at market pay approaching Senior Engineer. 27y/o

Just dealt with this recently...fork it is!

@-psr so true :)

@beriba I think you misunderstood what I said.

I thought I was verbose enough. Apparently not.

I literally said that I use git pull --rebase.

Is there even a point in typing out a thoughtful reply here? Apparently not.

I don't have bad git habits, I'm literally on the same page as you.

Everyone recommending VS Code are onto something. It's an incredible editor.

@beriba well, for the most part I agree. We merge our branches into integration and then we merge integration into master. I'm talking about local branch, updating from origin while branched. As for why I even care about micro merge commits, it started with a peer who had a number of commits and often back to back "merge origin into branch" commits well over 50% of the substance of the pull request. So we tried coaching then squashing his prs... He kept trying to stay branched after squashing... I digress.

@beriba we all branch off of a protected integration branch. We rarely do shared branching. We are a team of four. I'm talking rebasing locally on top of the integration branch to be conflict free for the pull request. If it were a shared branch, all you have to do is make sure you are up to date before force pushing and also make sure someone isn't pushing at the same time. If you can avoid that, it's pretty painless. Just git pull --rebase. I'm all about minimizing micro merge commits, and keeping a clean history that's all. I will admit though, minimize not eliminate...because be realistic, it's risky and a hassle in shared branching with poor communication.

lol I love force pushing a rebase. I hate merge commits.

Everyone else in the shop won't get near force push.

Just gotta communicate and be careful.