933 karma · joined April 2, 2013
What matters is how you deal with incidents as an organisation, not that you should never release a bug.
git log - see a commitish I want to fixup cmd-f type first few letters hit tab to get to the end of the commitish cmd-c esc cmd-v to paste it
The other great thing is when you have cmd-f going and there are multiple hits in your terminal, hitting enter cycles you through them backwards.
I also enjoyed https://jvns.ca/blog/2017/04/23/the-fish-shell-is-awesome/ which is a nice read though not a tutorial.
Overwhelmingly the developers in my organisation are happy to work remote forever. Deliver people, product people, design people all seem to want to be back in the office. Upper management as well.
In an ideal world, workplaces would strike a balance and allow each person the environment to deliver their best work.
Does anyone have good resources for someone who would like to brush up on these subjects?
If you already understand MVC (for example if you’ve worked with .NET’s MVC offering) reading rails guides will serve you very well.
Surely the author means easier?
I push my code up to my origin as soon as I can and as I go I’ll fix up my commits and force push.
There are some advantages for me anyway. Pushing to origin kicks off some smoke tests and end to end tests that are fairy slow and cumbersome to run on my dev machine. That helps me catch bugs earlier, especially since I’m working on a Microservices architecture. Also it acts as a backup for if my dev machine dies on me. I prefer to fix up and force push to create a clean logical story from my code rather than leave in spurious commits which exist only to fix linting for example.
> But it’s more your own lack if you’re not able to imagine these thing inside your mind by yourself
Maybe that in itself is a taught skill?
Disraeli said “the fool wonders, the wise man asks”