![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
We are currently at the point where if the forecast is inches of snow, we think "maybe we will see a flake or two." As i headed to bed last night, there were fat flakes falling occasionally. I think if a cluster of snow crystals found each other to fall together, they could stay cold enough to hit the ground as snow.
Tonight's prediction is 2" of snow. Yeah, right.
So are the grocery shortages supply chain or snow panic, i wonder.
I read the announcement of a late February pub crawl in my town with a sense of wonder. The Omicron case rates shot up so fast: could they come down fast enough in the next four weeks for a pub crawl to seem not insane?
In other wonders, i wonder if the tech folks among us have a guide to using git they like. I am really fuzzy on the different ways my colleagues use it, and i am wondering if i should be using it in my personal data repository more cleverly. I use Visual Studio as my editor these days (since the mac changed permissioning, and i would have to recompile emacs to run it). Is it easy to bob back and forth between branches? Right now i use it like i used code repositories in the 90s. At least my coding is slightly more sophisticated than my Fortran coding was, but not by much.
(Feeling like a brontosaurus.)
Tonight's prediction is 2" of snow. Yeah, right.
So are the grocery shortages supply chain or snow panic, i wonder.
I read the announcement of a late February pub crawl in my town with a sense of wonder. The Omicron case rates shot up so fast: could they come down fast enough in the next four weeks for a pub crawl to seem not insane?
In other wonders, i wonder if the tech folks among us have a guide to using git they like. I am really fuzzy on the different ways my colleagues use it, and i am wondering if i should be using it in my personal data repository more cleverly. I use Visual Studio as my editor these days (since the mac changed permissioning, and i would have to recompile emacs to run it). Is it easy to bob back and forth between branches? Right now i use it like i used code repositories in the 90s. At least my coding is slightly more sophisticated than my Fortran coding was, but not by much.
(Feeling like a brontosaurus.)
no subject
no subject
It can get to -15C here, it's more common to have a cold snap like we have right now around -10C. We're at the same latitude as North Africa: i know so many other folks get MUCH colder!
no subject
Yesterday I went up to put out the garbage and very full recycling bin. Ha ha! said I to myself, As I go up the still-slippery driveway the bin will be my mobility device! I can use the bin to get to the mailbox and then across the driveway on the road, drop off the bin in its accustomed place and go down the lawn. Alas, on that last steep portion of driveway the bin and I were sliding back downwards. Patience was not conquering it. So I angled the bin to drift to the grass and then went up the grass to the mailbox successfully. The voyage across the top of the driveway on the road was Fraught Indeed, requiring not only patience but a repetitive conversation refusing help from an athletic young woman who was walking her large dog. And then I went down the grass and took the second bin up the grass, awkward though it was.
But our street was the only one I was on yesterday that was hazardous.
I am so glad of the precipitation. No sign of snowdrops yet.
no subject
Yes, it is easy to bob back and forth between branches.
Branches in git can be way more ephemeral than they were in code repositories in the 1990s.
That means in a typical work day, I am going to go to the develop branch, and do a
to make sure that I am up-to-date with all the changes my colleagues made yesterday.
Now that I am up-to-date, I am going to do
That means, I am checking out a new branch called "feature/my_new_branch"
Then, I will muck about on my branch.
When I am done with the mucking about part, I will do
which will stage all the files I created and prepare them for upload. The "." means "add all the files." I can choose to add some of the files instead, but usually I add them all.
Then I will
This will attach a short message to the staged things.
Then I will
which will send the things to github.
That will only send them if my branch exists on github and all that. If it fails because the branch does not exist on github, it gives you a helpful message to make your branch exist on github. I created a shortcut for the command so I don't remember what it is.
Once on github, I will go to the "Pull requests" tab, and it will say, "Hey, it looks like you uploaded a branch, do you want to do a pull request with that" or something to that effect. I will tell it yes, and then there is a template where my coworkers say, "Explain yourself. What did you do, why did you do it? Do you have a pretty picture?"
Then continuous integration stuff runs. Theses are style checks and code tests. If this fails, I will know how to fix it, or I will say "Help me, this failed in a weird way."
Once it passes all that and the coworkers approve of my nonsense, I do a squash and merge. That means all the things I did get squashed down into one commit and merged into the develop branch.
Some parts of this will be completely irrelevant to you, but that is typically how I use git in my work day.
no subject
At least we have some groceries and I feel your pain on the shortages - I did get milk earlier this week though and we have the Fairlife shelf stable stuff to cook with if needed
Stay warm and hopefully this turns out to be nothing...
no subject
snowing steadily now...Dowser is in HEAVEN
Git recommendation
I am also happy to answer questions and chat about it, although it's been a while since I've used it actively.
no subject
When I was trying to re-enter the work force, I was blogging my learnings. Here is the search in that blog for the term Git. It starts with some very easy resources in the oldest posts, and there are more complex things in the more recent posts.
There was a thing by Women Who Code DC that I remember being better than it appears to be.
Git SCM has a few videos that are short, in order, and less chaotic than poking through my old blog posts.
There are tools that make dealing with git easier like Oh-My-Zsh for command line on Linux variants which I mention in my blog. Git SCM has a list of GUI tools, and that makes some of this stuff easier to visualize.
no subject