Git - what to do when it goes wrong
This has a great summary of what to do when things go wrong when using Git. Added here so I know where to look in moments of panic.
Links
This has a great summary of what to do when things go wrong when using Git. Added here so I know where to look in moments of panic.
Links
There are two camps of people where I work; those who want to return to the office and those who want to remain working remotely. The former group tend to be those whose work involves spending most of the day talking to people (the “business” side of the company). The latter group tend to be those whose work is mostly focussed around thinking - or have family and enjoy the balance this approach affords. I fall into the latter camp on both counts.
It is very easy for your work week to become a random collection of meetings - all with different attendees and different agendas. For developers in particular this can cause a huge hit on productivity as their day becomes disjointed and they are unable to stay focussed for the longer periods they need for their work.
In a recent article by Ryan Singer, Options, Not Roadmaps, he explains why he doesn’t use roadmaps - he uses options instead.