For this demo, we will be using node/javascript and NPM, only because it is sort of a lingua franca.
Let's create a merge conflict. It's pretty easy to do.
| #_preseed_V1 | |
| # <CHECK_THIS> | |
| d-i debian-installer/locale string en_US | |
| d-i keyboard-configuration/xkb-keymap select us | |
Instructions for getting an ELK stack set up quick on Mac. Paths are opinionated. You'll have to infer and change. Sorry mate. 🍰
Install Homebrew if not already. You probably have. If not, you should.
brew install elasticsearch nginx
and it's this very interesting little post where he talks about at the end of your day; you want to close the book on it. I think this is especially pointed now that many of us are working from home. For me, this is a new thing. And so, I've been very intentional with trying to put walks at the beginning and end of my day.
But in this particular blog post, he describes a routine that he does where he tidies things up and makes his list for the next day. And then he has a particular phrase that he says, which is "schedule shut down, complete."
update this
"There are hundreds of different computer languages. Most experienced programmers know a dozen or so." source
WTF!? A dozen? Know? What does know mean? I don't KNOW English. Do you know what "erinaceous" means? (of, preterning to or resembling a hedgehog) I don't KNOW twelve machine languages.
KSP is delaying the 64-bit windows port for a while, at least past 1.0. The 32-bit Windows KSP version is a bit cramped. You install too many mods and the game will crash. It's hard to work out the balance point. On the KSP forums and on reddit, sometime people suggest switching to Linux. Someone is having problems playing a game and someone basically suggests learning Unix. Then the thread dies.
Linux (even if you've used it for a decade) is hard. Especially getting all the things to work properly. I used three different distros until I got AMD video drivers to work correctly and even now I'm not sure. You can have an easy time installing Linux. Maybe you got lucky on your hardware. Having a bad time in Linux is crazy-pants-party-time. You have to know a lot of commands just to collect information on what is going on.
Try a sprinkle of empathy.
So I wrote down what I did since I'm wiping my Linux partition over and over again. I hope this helps someone. Maybe
| require 'drb/drb' | |
| DRb.start_service | |
| remote = DRbObject.new_with_uri("druby://localhost:8787") | |
| remote.pid | |
| # => <some pid> | |
| # you can verify the PIDs with top and you can filter by process name like ruby or irb or something |
The absolute requirement is that these must be binaries that could go into /usr/bin one day. No python, ruby or js stuff. Not that dynamic languages are bad/evil, but I think system utilities should be binaries. I also think it's interesting that people are writing replacements in Go/Rust/Other that rethink some unix legacy. Replacement doesn't mean better in all cases. I just think it's an interesting time but also a good measure of what these compiled languages can handle/tackle/address. Will we see larger and more impressive CLIs? Or will the feature sets be about the same but the quality/stability/safety be better?
It's going to be reductive to explain some of these tools in one line.
| # Things have changed in postgres 15.x+ | |
| $ createdb -O <your shell uid> foo_dev | |
| $ createuser foo | |
| $ psql | |
| psql> grant all privileges on database foo_dev to foo; | |
| psql> alter user foo with encrypted password 'random-password'; | |
| # enter the database that you just created |
| // User password resets could benefit from railroad error handling | |
| // because there are so many things to go wrong along the way | |
| // | |
| // 1. I forgot my password, send me a link | |
| // 2. I got the link, let me enter a new password | |
| // 3. Password and confirmation must match | |
| // 4. Password must be at least 8, etc | |
| // 5. Password was saved successfully | |
| // | |
| // There are many things that can go wrong and having a transaction |